• 45 Posts
  • 120 Comments
Joined 11 months ago
cake
Cake day: July 30th, 2023

help-circle

  • One other Lemmy instance is on 0.19.4, and that also has the same problem:

    Ungoogled Chromium: the create post form erases the fields after tabbing out of them. Tor Browser (firefox based): no issues with the create post form.

    Now slrpnk is on 0.19.5, along with two other Lemmy nodes I tested this on. The create post form is working in this version with Ungoogled Chromium.

    timeline selector broken

    There is another problem that was introduced with version 0.19.4 and still persists in 0.19.5: There are four possible timeline views: subscribed, local, all, moderator view. That selector is broken in Ungoogled Chromium 112 but not in Firefox-based browsers. In UC, I click “moderator view” and the button highlights as I click it, the page refreshes, but the selector does not stick. It is trapped in the “local” view and only shows the local timeline.

    This problem is replicated in other 0.19.4 and 0.19.5 instances.

    update

    Actually there is still a problem with 0.19.4 w.r.t. post creation. And this affects Firefox too: if I use the cross-post feature to copy the post elsewhere, the form is populated just fine but then I have to search for the target community at the bottom of the form. As soon as I select the target community, the whole rest of the form clears. I have not yet tested this specific scenario in 0.19.5.




  • not sure what you mean by “doesn’t prevent using the function entirely.” Do you mean the function is available for those who install another browser? My current theory is that the create post function is 100% broken for Ungoogled Chromium users, but probably operational for people running 3rd party clients or Firefox. Considering Ungoogled Chromium is based on the single most popular browser (Chromium), vanilla Chromium users are probably also impacted, which seems serious.

    The form should probably display a loud warning about this. Someone might opt to write the body of their post as a very first step, before the title. They could put a substantial effort into writing a long text and then see it all vanish the instant they click the title field. Nothing is worse than seeing one’s work thrown away like that.

    I would roll back to the previous version if there is no fix for this.

    (edit) Are there any stats kept on user agent strings? It might give a clue on the number of users affected.

    (edit2) history

    I guess it’s worth noting a bit of history. For quite some time (maybe a year or more) Ungoogled Chromium did not work on any Lemmy site for me. Tor Browser did. After upgrading a couple months ago, UC worked on all Lemmy sites. But now Lemmy is dysfunctional again on 19.4. Works fine on Lemmy 19.3.


  • Antiwork means the revolutionary abolition of the world of work and all that entails: a waged-labor

    BBC World News recently covered a trend of employees quitting the conventional style of work. These workers reject the culture of breaking one’s back bending over backwards to satisfy their boss’s every wish. The concept is for workers to put their own well-being above the corporate bottom line, which generally means forgoing¹ promotions, raises and advancement in the company because it’s just not worth it. To own the work, and work at a comfortable pace and comfortable fashion.

    I don’t recall what term they used for this trendy new view, but “antiwork” could be taken to be a more general concept that covers the extremes of complete abolition of work as well as the less extreme concept of simply rejecting unwanted excessive overwork. Before reading your post I would have assumed “antiwork” would include “antiworkmyassoff”.

    ¹ by “forgoing” I don’t mean rejecting offers, but just accepting that promotions and significant raises won’t typically be offered.


  • For the past few days, the “create post” form is usually broken. After entering a title I hit tab to the next field and the title is instantly erased upon shifting the focus to another field. The form is unfillable.

    I was able to post once after this behavior started for no apparent reason. No idea how to reproduce that.

    It’s worth noting that submitting comments in existing posts is not a problem.

    Browser: Ungoogled Chromium 112

    (edit) after more thought, I think that one time I was able to post was probably done using Tor Browser, not UC.


  • What’s interesting about this is #LemmyWorld uses Cloudflare, and CF was involved in a CP scandal. You might be tempted to report the CP to Cloudflare, but it’s important to be aware of how CF handles that. CF protected a website that distributed child pornography. When a whistle blower reported the illegal content to CF, CF actually doxxed the people who reported it. Cloudflare revealed the whistle blowers’ identities directly to the dubious website owner, who then published their names and email addresses to provoke retaliatory attacks on the whistle blowers! Instead of apologizing, the CEO (Matthew Prince) said the whistle blowers should have used fake names.






  • Hence the purpose of the thread. The OpenVPN devs serve the permacomputing community better than the devs of the ProtonVPN client. The fact that profit motives are the culprit for the forced obsolescence is guesswork. It’s a very good guess but in the end it’s merely irrelevant trivia. They don’t get a sympathetic pass or some different treatment for needing to profit.

    You can’t expect to use older hardware in combination with bleeding-edge online services (like VPN)

    Yes I can. Hence the purpose of open standards which make that possible. OpenVPN is proven to work on old hardware with current bleeding edge services. I have it working with riseup and getting it working for ProtonVPN is likely a matter seeing if I fat-fingered my password wrong. I have openvpn connecting to protonvpn from other clients already.

    I’m guessing the 23mb to 44mb jump was due to targeting a newer API version. That doesn’t mean ProtonMail’s code is more bloated–it could actually be less, while the OS/API side increased.

    It doesn’t matter. Introducing code that statically links in more object code is also accountable bloat that brings bugs. Saying that the code is on someone else’s side of the wall does not discount the bug potential amid other downsides to bloat. It’s also notable that AOS 6 was a minor change. It was Google following a one-major-release-per-year pattern, and just making an insignificant release just for optics so people don’t think they’re slacking on progress. Thus speculation that the same source code compiled in the bloat is unlikely. Not long after that release Protonmail makes another giant leap of bloat to 70mb+ with no change in the SDK API target.


  • AOS 5 (Lollipop) was 7 years old when Proton dropped it, not 10. 10 years is also a reckless place to draw that line. That’s Apple’s line.

    Permacomputing folks have much higher standards than that of Apple’s corporate bottom line. I am writing this response using 16 year old machine that works just fine, and which will continue to function and serve my needs for at least another 5 years more.

    As developers chase the shiny, bloat increases. Protonmail version 1.13.40 (the last AOS 5) was 23mb. The very next version just 3 months later (3.0.1), the first to demand AOS 6+, was 44mb. Yikes. They are welcoming bloat with reckless disregard. The more you bloat the code, the more error-prone it becomes. Bugs are directly proportional to complexity.


  • What you seem to be implying is that the OS removed an interface that the app is using. That’s unlikely because ProtonVPN needs generally the same facilities and mechanisms as openVPN, which was not forced to bump their SDK. You can also see that the ProtonMail app (which is inherently very different than VPN service) also bumped their version to abandon AOS 5 users a year later. Yet other email clients (which generally need the same interfaces) were not forced to abandon people.


  • IPsec didn’t occur to me. Apparently they don’t show the ipsec configs when desktop users login (I only recall openvpn and wireguard & i’m not keen to check because just about every login results in a CAPTCHA for me).

    The older droids (2.3 for sure) had broken built-in ipsec but they probably got it straightened out eventually.

    they may have been forced to raise their SDK version?

    What do you mean forced? Forced by who? I would not make excuses for pushers of forced obsolescence. It’s on them to explain and make excuses – which is almost always a quite vague “for security reasons”, like every bank that chases the shiny and forces consumers to buy a new phone every 3 years.

    Note Protonmail demonstrates this same forced obsolescence pattern with their Mail app, which requires AOS 6.




  • dedicating an entire community to the stance seems a bit much

    That’s crazy talk. There are so many dynamics to non-voting that I’m not even convinced that 1 community is enough. This one community has to accommodate:

    • advocacy of not voting (Anarchy promotion)
    • problems voting & countless forms of voter suppression (my situation)
    • voter turnout discussions and consequences of not voting in nations where voting is obligatory (Belgium and Australia)
    • hopelessness of voting in regions where voting merely legitimizes dictatorships (China, Russia)
    • alternatives to voting (e.g. consumer actions)
    • Non-voting as a means to compel positive change (e.g. 97,000 Michigan dems and pro-Palestinians threatening to not vote unless Biden changes his policy in Israel)

    I’m not an anarchist but found it interesting to read their rationale for opposing voting and elections.

    I’m personally very pro-voting

    Then you should be very interested in the 2nd bullet. There are LOT of non-voters in the US and it leads to scumbags taking power (e.g. 2016 POTUS). You should want to see people discussing the low voter turnout problem that helps the republicans.