Recent searches
Search options
Administered by:
@smallcircles @peertube I've long complained that one of the biggest problems with the Fediverse is that it's needlessly fragmented into separate services, apparently just because commercial social media is similarly fragmented. Just because Twitter, Instagram, and YouTube are separate services doesn't mean we need separate Federated Twitter, Federated Instagram, and Federated YouTube that can technically talk to each other but don't make it easy.
I've thought about this. All fediverse backends should implement all kinds of objects. I think mbin is a lot better than others because of this.
@Floppy@mastodon.me.uk@TheFederatedPipe @smallcircles Agreed, for full fediverse compliance, *something* should be shown for all types of object, and all actor types too!
Ignoring them completely is not helpful, it would be much better even to just display canonical link if nothing else is available.
I say this as dev of @manyfold; I'd like to be able to provide custom types that have meaningful semantics, but instead I need to use the restricted set of types that Mastodon will react to.
@TheFederatedPipe @smallcircles years ago we had https://en.wikipedia.org/wiki/OEmbed. Feels like we ought to be able to leverage something like that.
Not so long ago I read about it, thought it was cool that YouTube, TikTok and the others follow this, because it benefits a of us.
Exactly, the server shouldn't ignore it, the user via the client should do it if they wanted to.
I don't like the fact that @Mastodon has basically stalled the development of the fediverse, people here are way to afraid of breaking stuff. Don't get me wrong, backward compatibility is cool, but sometimes you gotta do it for the benefit of the whole net.
I've read about some cool FEPs that are basically ignored out of the fear of compatibility with Mastodon or older versions despite de fact they solve a huge problem.