• 84 Posts
  • 300 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.










  • You question forced me to revisit this and take a closer look. I have in my notes “If someone’s fingerprint is untrusted, they will get an encrypted msg that they cannot read.” So I entered a 1:1 window with the one person who only ever gets errors from me, entered /omemo fingerprint, and it simply showed the person’s fingerprint. Then I did the same for someone who has fewer issues with me, and printed next to their fingerprint is “(trusted)”. Ah ha! The other acct has an untrusted fingerprint and Profanity does a shitty job of informing the user. The absense of a “(trusted)” when asking for the fingerprint is the crucial indicator.

    To answer your question, I think keys are managed automatically. I never had to add a key. But I have had to trust fingerprints. In the new version of profanity it’s possible to enter /omemo trustmode blind. That would also solve my problem but I don’t want to be sloppy. So I have to guide the other user to their own fingerprint and confirm it.

    (edit)
    Well this is bizarre. There are a couple people who I can talk to in Profanity just fine with OMEMO enabled, and their fingerprint also lacks the “(trusted)” next to it. Yet my trustmode is “manual”.




  • The server is snikket.chat.

    I am not sure what causes the OMEMO error though as I am not a iOS user.

    I believe Profanity is mostly to blame for those errors. Profanity loses track of keys and fingerprints of other users, and I think what it does is encrypts the msg to myself, then transmits it without encrypting to the recipient. Then the recipient gets a msg that’s encrypted to others but they cannot decrypt it. Then to worsen matters it seems XMPP uses the same incorrect error message for many different situations. Profanity really needs to change so if any of the recipients keys are not found, it should refuse to send the msg. I see a bogus error on my end as well, and the fix is to disable OMEMO the re-enable it (/OMEMO end; /OMEMO start).

    In any case, thanks for the suggestion. I’ll see if I can get someone to try that app. I cannot be fussy about features. I really just need text msgs to work.



  • I am aware that that happened in Oregon once, and even though the parts per million after one person’s bladder is empted into a tank of thousands of gallons is negligible, they emptied the whole water tank which covered a whole city and refilled it, and sent the guy a water bill for that.

    I suggest watching the “how beer saved the world” documentary. It shows how they used filthy stagnant pond water with duck shit in it to brew beer, which was safe after the brewing process. But note the beer container is not part of the brewing process.

    The water is not much of a risk. But filled bottles sit in warehouses with rats. Rats urinate on the bottles. This is why Europeans don’t drink directly from the bottle. I’m not sure why Americans are content drinking direct from the bottles… maybe US warehouses are rat-free.


  • In Europe they charge 10¢/bottle for simple bottles and 40¢/bottle for the fancy clamp-down style. Then that gets refunded when they are returned. It’s a bit of a hassle because some brewers do not participate, in which case the reverse vending machine rejects the bottle which means you then have to carry it to a glass recycle bin. The brewers that do not participate use a thinner more fragile glass that would be unfit for reuse. So consumers have to stay on their toes and keep track of which brewers participate. Can get quite tricky with the obscure artisinal brews.

    Ireland is introducing the same concept for plastic bottles of charging a fee for them then returning the fee in a reverse vending machine. I can’t imagine reusing those. They must be recycling them.