Timeline
Post
Remote status
Context
1
@sun out of every single healthy conversations out here, that one is real ass. doesn't make any logical sense.
Replies
16
@yonle the post the first was replying to was completely reasonable and “you get blocked for a reason” is a bad argument imo and the reply shows why. People aren’t fair.
@sun it won't make any sense, and i look at it more like it's "meh, idc"
@yonle alright, well I tried to explain it. Have a nice day.
@sun well, what i mean by the response in the end is similar to "well you've been blocked probably for reasons so idc"
@yonle sure people are free to curate their own experience for any or no reason
@sun and it's no wonder the specs never going anywhere, useless bunch of philistines
@Ree @i @sun I suspect it is already planned in some way. Look at Aussies trying to declare Github a social media network and ban 16 year old and younger from accessing it (they failed), or how EU is getting more and more involved in Mastodon.
The latter is especially worrying since EU's DSA is already a threat to Fediverse and something like required moderation additions could be a big issue, ie. a requirement for some kind of 3rd party automod to prevent "misinformation" and alike.
The latter is especially worrying since EU's DSA is already a threat to Fediverse and something like required moderation additions could be a big issue, ie. a requirement for some kind of 3rd party automod to prevent "misinformation" and alike.
@i @phnt the same crticisms of ostatus apply to activitypub. that a bunch of standards all standing on each others shoulders in a trenchcoat to make this one use-case work (microblogging) won't magically create interoperability with other services that leverage one or more of those open-web standards.
you use rss--but you can't consume some other rss feeds, and rss readers can't read your rss feed.
you use webmention--but you can't interoperate with blogs
you use websub--but you can't interop with aggregators
instead of a tight and targeted spec for use cases you drag in a shitload of baggage to be "spec-compliant" with a spec you were only using out of design convenience, but then you have extra work and mismatch with functionality so you end up cutting corners and you're not compatible anyway (see: json-ld)
AP sometimes can do these things partially because it has enough traction that people just...implement AP instead of just the minimal standard. At which point it could have been anything else, even ostatus to some extent (ostatus had no private messages admittedly)
you use rss--but you can't consume some other rss feeds, and rss readers can't read your rss feed.
you use webmention--but you can't interoperate with blogs
you use websub--but you can't interop with aggregators
instead of a tight and targeted spec for use cases you drag in a shitload of baggage to be "spec-compliant" with a spec you were only using out of design convenience, but then you have extra work and mismatch with functionality so you end up cutting corners and you're not compatible anyway (see: json-ld)
AP sometimes can do these things partially because it has enough traction that people just...implement AP instead of just the minimal standard. At which point it could have been anything else, even ostatus to some extent (ostatus had no private messages admittedly)
