Conversation
Notices
-
Embed this notice
The more I think about it the more @alex was technically correct about moving mentions from header to body
:marseydisagree: Putting mentions in a specific field
:marseyagreefast: Putting mentions in the text body for some fucking reason
Imagine email but everyone just did this
-
Embed this notice
I think the issue really was that pleroma is controlled by the council of fags and trannies and they are very resistant to everything Alex does for political reasons. Trannies literally fediblock instances just for using soapbox, I just saw one yesterday.
The reason it “broke fedi” was that the largest instance uses soapbox, and the people that make clients and stuff were relying on conventions rather than the standard. Alex can’t force everyone to fix those conventions but he made a good faith effort to make things work in pleroma.
-
Embed this notice
Lol the feature was broken and everyone put up with it. @alex fixed it. Turds got mad. Story done.
-
Embed this notice
“Hurr durr these things that are meant to work together by following a standard aren’t working together because we aren’t following the standard. How could this happen to me??” :soyjak:
-
Embed this notice
@bot @roboneko @ne @newt
okay i'm fed up of seeing this thread lol
Issue is, this was not the standard for the majority of the fedis existence. it was then added in the backend as something that worked but no FE's worked with it. The issue was that gleason (think it was the other guy but icr the name) pushed an update which not just added the new way of doing it, but removed the old way, with no workaround so every other instance was unable to display it properly, effectively 'breaking' the fedi.
there was no phase out, no patches or workarounds for the prior versions or anything.
the issue is communication and implementation. since fedi relies on many different hosts with many different softwares, you have to be very careful when making changes to software, regardless of whether its even the right thing to do, how it was done was very poor and why people got mad about it.
There are two types of standard, 1 in a process in which things are done, 2 being how things are done currently. you may think that it is a good standard in the first sense. it was not in the second.
and thats not even talking about the ways in which FE's and BE's interact and how imo they couldve avoided the issue entirely if it was handled differently, not even talking about the older instances and software that doesnt work properly now because of it.
I hope that made sense and gives some perspective lol
-
Embed this notice
@bot @ne @newt
> stop making me punch you
:brainlet:
-
Embed this notice
@bot @ne @newt
> sweeping up the oldfags and their broken stuff that sucks
who broke it though? :think_nyan:
-
Embed this notice
The people that didn’t follow the standard.
-
Embed this notice
Sorry boomer, gleasonchads are sweeping up the oldfags and their broken stuff that sucks and actually making things better instead of just stagnating.
-
Embed this notice
There’s a standard so people should follow it, you’re just coping and sneeding. Have you ever seen a hellthread in misskey? It uses full tags so every post is inevitably 99.999% mentions, which is pants on head retarded and not user friendly at all. It also doesn’t follow the standard so it literally can’t reply to soapbox posts properly.
-
Embed this notice
@bot @ne @newt it's not coping. breaking the network is not ok. what some document happens to say doesn't change that. there are ways to go about these things
damaging the ecosystem is not helpful
-
Embed this notice
Aren’t mentions in the metadata part of activitypub? So that’s the “correct” way to do it isn’t it?
-
Embed this notice
@bot @ne @newt it doesn't matter what's "correct" according to some spec if in reality your change breaks people's stuff. being forced to have all mentions in all posts all of the time is dumb and backwards. but alex was irresponsible with the rollout of a breaking change
half the code around here (and FOSS in general really) is barely maintained at any given time but it works specifically because people don't constantly make breaking changes to the core infra
-
Embed this notice
@newt @ne @bot this is ironic because half the features on fedi appear to have been blindly copied from twitter instead of being carefully thought out
but I agree with the sentiment. blindly mimicking is bad
-
Embed this notice
It’s actually easier to remove mentions on soapbox, esp on mobile. You can still do the second, and maybe clients shouldn’t do things incorrectly so not really an argument.
-
Embed this notice
@bot @ne who says what's correct here? Most clients work with mastodon and it uses mentions.
This stuff breaks compatibility just for the sake of being like twitter. Which is something I'd rather avoid, because twitter is a shit platform and there is no reason in trying to mimic it.
-
Embed this notice
What are the top 3 reasons?
-
Embed this notice
@bot @ne Easier to remove mentions. Also, I can reply to more than one person with more than one statement. Also also, a metric shitload of clients aren't broken this way.
-
Embed this notice
Isn’t it just duplicated information? Also it’s very dumb when a post is 90% tags which happens often, and sometimes people break @s by accident when replying.
-
Embed this notice
@bot @ne most of your language is just duplicated information. If you want to deduplicate your posts, run lzma over them.
Mentions in posts are convenient for a whole plethora of reasons.
-
Embed this notice
@ne is it bad because you don't like it? Or are there any other reasons?
-
Embed this notice
@newt its bad and i dont like it
-
Embed this notice
@ne what's wrong with using email like that again?
nekobit
Fediverse Contractor
Josh Adams
Lumeinshin
Neko McCatface v2023 :verified::makemeneko:
:suya:
All GNU social JP content and data are available under the