On my phone only worked via Chrome browser (not via sync or samsung internet), give it a try

lovely. More pls 😁

Ty for sharing ❤ edit: Whoops just realised it wasn’t OC. Still great tho!

Your first sentence I agree with. Your second sentence I don’t agree with. It’s still early with the reddit exodus - things have been escalating incredibly fast and most people don’t even know much about it yet, or are still processing what’s happening.

Reddit was a big part of our lives for many people and it’s not easy to let go. I was so deeply offended by what happened that I let go quickly even though it hurt me. But people who already used the official app? For them, it’s a difficult conversation at best. But I’d say it is still early days.

So much this. Defederation is a catastrophic issue for an average user in its current form, as the interactions fail totally silently.

Give us simple but informative warnings on reading threads, warnings when trying to post, warnings when trying to subscribe, and warnings when our subscriptions become defunct. Then the user can make informed decisions about either looking for new communities, or maybe moving to a different instance.

You say that as if the blocks are a known factor. They are not easily visible to users, and instances can block others on a whim like beehaw did to some others very recently.

Worst of all, when users had subscriptions and connections active from a time when there wasn’t yet a block in place, they don’t even get warnings or notifications when trying to post or comment? Subscriptions don’t give warnings either?

But that’s not really a full solution, because instances seem to block instances on whims (recently beehaw blocked two other ones suddenly). And users don’t even get warnings or notifications about it when posting or reading cached content…

But the “true version” of this thread exists on Lemmy [email protected] does it not? I thought my comment into this thread would not be seen by anyone outside lemmynsfw when lemmy.ml blocks lemmynsfw?

It’s pretty awful for an average Lemmy user, because you can get cut off from communities you already subscribed to, without any notification! So you might post and comment without realizing that your content is not getting published, even though you and your local instance still see it.

The user experience would be improved by getting a warning if you try to contribute to a community in this case. And also your subscriptions should show warnings about not working anymore, and those should come up as notifications on the account.

Looks like that is the case! But how were you able to see my comment and reply then?

I think it’s a technical issue rather than community limitation but also would like to hear any insights…

I have this problem quite often. Any insights from anyone?

The default webui needs many updates to become more usable for a wider range of users. I also don’t like how the page updates wildly when I’m trying to read through. Either the updating should work more smoothly to not make the user disoriented, or maybe have a preference for paged scrolling or something along those lines…

Funnily enough - my instance already does this in the UI and I actually dislike it! So I would want to opt out of it, but can’t (at least until the UI in my instance is further modified).

Having this as a controllable user preference in the “default” webui would solve both my problem and yours, and probably many others too :)

Great work! User preferences diverge - I wanted “no blur”, but also “no auto expand” for myself.

While having this in my instance of choice is great, Lemmy as a whole would benefit from improving the default webui with things like these settings. Where could users pitch ideas like this?

Workarounds are great, but this would be worthy of being an option in the native webui.

It is public information. Go to the /instances/ address of any instance to see which are blocked by them.

I guess users will need to review that when deciding where they create their lemmy accounts.

Unless it’s blocked…

Getting the blur disabled should be a user setting though in the web UI without installing anything.

femboys!