So I've run this poll until yesterday. The question was whether the Fediverse has quote-posts.
20 users voted for yes, 8 users voted for no.
Of course, this poll wasn't representative. I dare say my "bubble" is more Fediverse-savvy than the average, and I know I had quite a number of voters from Hubzilla and (streams). So the result is greatly skewed towards "yes". And still, 40% of all voters thought the Fediverse had no quote-posts.
This shows how well especially Mastodon users know the Fediverse.
Oh, and by the way: The Fediverse does have quote-posts. Just about everything that isn't Mastodon can quote-post, and it all can even quote-post Mastodon toots with next to zero resistance. And in fact, quote-posts in the Fediverse are about six years older than Mastodon.
I'mma just copypasta your hashtag line below ;) Let's not forget, in #Misskey parlance: #ReNotes - which arguably, might be the most etymologically correct of all of them, since most (at least masto) posts are 'notes', rather than 'articles'.
And in fact, quote-posts in the Fediverse are about six years older than Mastodon
That might be a good tidbit for Yuki to expand upon in his Fediverse history doc at Codeberg ?
Tbh I'm not enthusiastic about a #Mastodon#hardfork. Not necessarily because of the #techdebt or even because it's technically inferior to other #ActivityPub implementations (which are both true), but because I cannot be sure if that new fork is going to adopt the same attitude as Mastodon in choking the rest of the #fediverse with its proprietary extensions and #EmbraceExtendExtinguish / #EEE.
I'd rather not have the uncertainty. Either start from scratch like #GoToSocial is doing or help the other two mainstream AP families which are #Misskey and #Pleroma. That's the only way we can ensure no implementation overwhelmingly dominates the fedi. :seija_coffee:
PSA: Since Threads apparently will be federating replies soon, I thought I should post this again, because there's still a lot of people that don't know.
When a normal user uses "block this domain" it's LITERALLY just a MUTE. The blocked server can still see, interact, and reply to your posts, you just won't be able to see them.
It's kinda like sitting in a room with hungry bears while wearing a blindfold. If you're scared of hungry bears, your best bet is to get out of the room, not put a blindfold on. And by this, I simply mean to migrate to an instance where the blocks are up to your standard on the "instance" level.
Stay informed and make informed decisions, no matter what you choose to do with your Fediverse presence.
The main reason other AP implementations have added it (or in the case of #Misskey, made signing objects enabled by default which was a reluctant decision) as well despite Authorized Fetch / #SecureMode not being documented in the spec is that plenty of big #MastoAdmins have enabled it for their instances thinking it will prevent harassment from instances they've blocked (despite the fact that AF is purely #securitytheater), forcing the rest of the #fediverse to adopt it to remain compatible. Even at the cost of performance (no more caching).
This is plain ol' #EmbraceExtendExtinguish or #EEE for short against AP and the fedi by the Mastodon monopoly, and nobody wants to talk about it because it undermines the narrative a lot of Mastodon admins are putting out to justify their fediblocking of #Threads. Would've been fine if they focused on the (real) harms #Facebook did to Burma for example, that's a totally fine reason to block FB. But screaming EEE just makes me roll my eyes on their #hypocrisy. :seija_coffee:
The lesson of the XMPP story is that the community shouldn't get complacent just because a big corp is now backing them, support their own smaller #FOSS developers through any means they can (whether financial or code), put out a unique thing every now and then, and make sure the UX is not horrible for new users. I think #Misskey, #Sharkey, and #Catodon got those lessons right (especially the very latter, UX was really horrible in XMPP back then and I think that's what "killed" it if you can even call it that). Not sure about #Mastodon though. Maybe that's what why almost all of the worry I'm hearing about #Threads comes predominantly from Mastodon and Mastodon-compatible (in the sense they try to be as compatible with Masto as possible in terms of API) instances. :seija_coffee:
Actually I can't really bash #Lemmy for this (as much as I'd want to) because it seems like pretty much the rest of the #fediverse has this problem of images not getting immediately removed from the server when you delete the image or even your account. I've tested with #Mastodon, #Pleroma, and #Misskey (even Misskey somehow gets it wrong by not immediately making your image unavailable by the URL even if you've deleted it from your Drive, however this doesn't always happen, see below).
Now I'm not sure about instance admin stuff (and I haven't tested with my admin hat on in this Misskey), but I'm guessing you don't have a view of all uploaded photos by a user that an admin can delete from in Mastodon and Pleroma either (please prove me wrong though!). :sagume_think: Misskey does let you view all files uploaded by a user and delete from there, though I'm not sure if the file gets immediately removed from the server once you hit delete, but it's probably gonna be like what I'm going to write below
What I do know about Misskey is that, if you've never accessed the URL generated for the file in your Drive, and hit delete, the next time you access it, it definitely will no longer be available; a pure 404 as expected. However if you've accessed the URL at least once, then the file will get cached. I'm not sure if it's Misskey doing this or the reverse proxy (like #nginx), because clearing cache or switching to a whole 'nother browser still shows the file is available.
Oh, and have I mentioned that all three software will automatically put your image into the server the moment you hit the upload button, even if you haven't submitted the post yet? Yeah it's equally as easy as Lemmy to accidentally upload something to those three as well.
This only applies in #Mastodon. #Misskey and its forks like #Sharkey have #fulltextsearch too and they will ignore your "#privacy setting" for every post it has ever seen from you. And IIRC Misskey did implement full-text search way earlier than Mastodon has started debating about it. :sagume_think:
Why did this debate of full-text search arose again? :seija_coffee:
What are people's feelings on using the FediBlock tag for calling out individual accounts? Personally, I find it mildly annoying at best, in that most of these accounts are already acted upon by staff, but potentially harmful at worse if people are going there instead of immediately clicking the report button, or even worse, using it to call out a user by finding one of their worst out of context posts and putting it on blast.
Honestly, I'm using it as a tool to scope out instances that we need to block because they are literal Nazis, literal pedos, literally attempting to harass people off of the network, or otherwise bad faith. I would rather it not come into play for individual accounts, but be advance warning for when the actual staff of a server is the problem.
What do people think though? Is there a perspective I'm missing?
Would Fediverse admins like a presentation by Babka folks on antisemitism on the Fediverse, specifically what mainstream Jews/Jewish organizations consider hate speech and why?
If you're an instance admin or a moderator and you'd be interested, I'd like to hear from you. If there's enough interest, I'll put together a signup, but this is just a feeler for now.
If you're interested, please reply or DM me, thanks!
If you're not an admin, please boost or let your admin know about this! Thanks!