And relying on a single volunteer to ship crucial security updates? Disabling the shitty FF features may be hidden in about:config but as long as this is possible, using upstream FF is still the most secure way to use a Gecko browser.
I think the post in itself is informational, many of the comments are not.
Post stays, comments get locked.
This thread transformed from being about a serious issue on the fediverse into a pile of accusations on a personal level. I don’t see this thread becoming any more civilized the way the comments are spiraling downwards. I’m keeping the post up because, as I said, this is a serious issue, but I don’t think keeping the thread unlocked is doing any good.
Calckey/Firefish (forked from the Japanese software Misskey, so I assume that one is similar) is basically Mastodon but cool. It fixes many of your problems. While it’s not yet perfect (same issue with followers from other servers), there seems to be more going on.
As annoying as Jack Dorsey is, I have high hopes for BlueSky.
As long as he doesn’t submit that protocol as ActivityPub 2.0 or whatever, it’s not compatible with the wider fediverse, so not interesting.
I don’t think the ideas of Lambalicious work with Lemmy. What would sending the domain name only achieve? I assume it uses the same logic as Lemmy uses to find crossposts? Obviously it needs the whole address then.
Maybe instead of crawling automatically, the users need to click a button to look up discussions? (I have yet to install your extension, so I have yet to experience the workflow myself, sorry.)
Maybe link to the privacy terms of the default instances? In general, I think your approach is good. You don’t collect any data, the feature is 100% opt-in. A central relay/proxy is even worse than your current approach. People are obviously free to set up their own Lemmy/Mastodon server if they want a relay.