It is a pity that #Peertube has never been well integrated with #Microblogging.

[glatorius@troet.cafe]

@smallcircles @peertube Since this answer was boosted, here is an explanation of the current state and why this doesn't really work with every link for now:
https://hachyderm.io/@thisismissem/113486614405418531

[smallcircles@social.coop]

@jonny @thisismissem

OT: I might take this opportunity to point to something tangential in case you find that interesting, namely that @helge has prepared a forum topic for thinking about next-gen social web protocol visions, etc.

Wiki: Vision for a Fedi Specification

This topic is for people who believe, that we need a better specification underlying the Fediverse. In order to develop such a thing, one needs a group of people that work towards a common goal. The goal of this wiki is…

Discuss Social Coding (discuss.coding.social)

[julian@fietkau.social]

@Glatorius @smallcircles @peertube It's possible, yes. I have definitely read a discussion about this somewhere on the Mastodon GitHub. From memory, you'd either have to do that check when someone first clicks on a link, which works-ish but would add potentially multiple seconds of delay in corner cases, or you check for every link in any incoming post, which would hugely increase the Mastodon DDoS effect.

[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.

[floppy@mastodon.me.uk]

@TheFederatedPipe @smallcircles years ago we had https://en.wikipedia.org/wiki/OEmbed. Feels like we ought to be able to leverage something like that.

[thefederatedpipe@fedia.io]

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 incompatibility with Mastodon or older versions despite de fact they solve a huge problem.

[silverpill@mitra.social]

@smallcircles @peertube Other micro-blogging services can receive videos, photos and events, and display them as posts. Only Mastodon can't do that.

[jenniferplusplus@hachyderm.io]

@thisismissem @smallcircles @peertube
We don't need to custom build a bunch of modal windows in every fedi app. There are platform provided solutions to this problem.

At the same time, mastodon lacks quote posts, or any other way to attach AP objects to a post. Which would solve this problem and more.

[thisismissem@hachyderm.io]

@jenniferplusplus @smallcircles @peertube platform provided solutions? So maybe at a stretch FedCM?

[jenniferplusplus@hachyderm.io]

@thisismissem @smallcircles @peertube
https://developer.mozilla.org/en-US/docs/Web/API/Navigator/registerProtocolHandler
And similar/compatible capabilities in every operating system

[thisismissem@hachyderm.io]

@jenniferplusplus @smallcircles @peertube protocol handlers aren't great because it limits you to one account, this has been discussed at length

[jenniferplusplus@hachyderm.io]

@thisismissem @smallcircles @peertube
No more so than the redirect modal does. If you land on your mastodon instance and can't easily switch to your other account on that instance, that seems like a mastodon problem, not a protocol handler problem. And the protocol handler doesn't require developers to adopt mastodons route schemes in order to be intelligible to the redirect modal.

[thisismissem@hachyderm.io]

@jenniferplusplus @smallcircles @peertube right but at least I can have accounts on different servers.

[jenniferplusplus@hachyderm.io]

@thisismissem @smallcircles @peertube
You can do that with protocol handlers, too. If you register multiple handlers, you get a dialog to choose between them. Which is not different than the redirect modals, except it requires no typing.

And native apps can also be handlers, making the whole ecosystem less awkward.

[smallcircles@social.coop]

@jonny @thisismissem @helge

FYI My own first feedback: https://discuss.coding.social/t/wiki-vision-for-a-fedi-specification/563/6

[jonny@neuromatch.social]

@smallcircles @thisismissem @helge i don't have more standards energy in me right now but i've signed up for notifs for that thread and plz don't hesitate to ping me again on it

[helge@mymath.rocks]

@johnny: But you would be such a good contributor. "As Johnny, I want to see all replies".

However, I understand not wanting to write this. I would probably end up with a long rant about what I actually want, and then delete it, because the density of information is thin. No prior experience exists.

[jonny@neuromatch.social]

@helge @smallcircles @thisismissem i just meant right now as in literally this moment but i will come play soon

[smallcircles@social.coop]

@jonny @helge @thisismissem

There was a nice list of protocol design related documents at IETF that I added to the thread:

Wiki: Vision for a Fedi Specification

This topic is for people who believe, that we need a better specification underlying the Fediverse. In order to develop such a thing, one needs a group of people that work towards a common goal. The goal of this wiki is…

Discuss Social Coding (discuss.coding.social)