this post was submitted on 03 Jul 2024
96 points (98.0% liked)

Fediverse

17786 readers
16 users here now

A community dedicated to fediverse news and discussion.

Fediverse is a portmanteau of "federation" and "universe".

Getting started on Fediverse;

founded 5 years ago
MODERATORS
 

I think this is a good incentive for Journalists to be more active on the fediverse.

you are viewing a single comment's thread
view the rest of the comments
[–] jmcs@discuss.tchncs.de 1 points 4 months ago (1 children)

A neat way would be to re-use one the 200 already existing standards like rel="author" or even rel="me" (which mastodon already supports anyway). This solution just is just NIH-driven development.

[–] ABasilPlant@lemmy.world 0 points 4 months ago (1 children)

I think the difference lies in two things:

  • You can share an article from a user of a different instance. In this case, your instance will have to look up the rel="author" tag and check whether the URL is a fediverse instance. I'm not sure whether this is scalable as compared to a tag that directly indicates that the author is on the fediverse. Imagining a scenario where there are 100, 1000, 10,000, or 100,000 instances on different versions.

  • The tag is to promote that the author is on the fediverse. If the rel="author" tag points to twitter for example, maybe Eugen Rochko + team didn't want a post on the fediverse to link to twitter.

These are my thoughts and idk if they're valid. But I think just reusing the rel="author" isn't the most elegant solution.

I know that mastodon already uses rel="me" for link verification (I use it on mu website + my mastodon account), but that's a different purpose - that's more for verification. There's still no way of guaranteeing that the rel="author" tag points to a fediverse account. You're putting the onus on the mastodon instance.

[–] jmcs@discuss.tchncs.de 1 points 4 months ago

There's also no guarantee that the rel=me points to a fediverse instance, mastodon already has logic to deal with thus without reinventing the wheel with what's effectively a proprietary solution.