saboteur

joined 2 years ago
[โ€“] saboteur 1 points 11 months ago

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

[โ€“] saboteur 1 points 2 years ago

lovely. More pls ๐Ÿ˜

[โ€“] saboteur 1 points 2 years ago* (last edited 2 years ago)

Ty for sharing โค edit: Whoops just realised it wasn't OC. Still great tho!

[โ€“] saboteur 4 points 2 years ago* (last edited 2 years ago)

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.

[โ€“] saboteur 2 points 2 years ago

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.

[โ€“] saboteur 3 points 2 years ago

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?

[โ€“] saboteur 5 points 2 years ago

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...

[โ€“] saboteur 1 points 2 years ago (1 children)

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?

[โ€“] saboteur 13 points 2 years ago (1 children)

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.

[โ€“] saboteur 1 points 2 years ago (3 children)

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

[โ€“] saboteur 1 points 2 years ago

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

[โ€“] saboteur 1 points 2 years ago (5 children)

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

view more: next โ€บ