Yeah, frankly I don't think an alternative would end up being significantly simpler anyway once you start accounting for the things that are already established in the current ecosystem. There are tools and services now, and libraries, but we always need more!
Absolutely. There's some in-progress work on this, but I haven't been following it too closely. github.com/mastodon/mastodon…
Sadly the state of things is that until Mastodon itself implements this, it's pretty much a stalled idea in the larger Fediverse.
I've always said the local timeline model of Mastodon was a bad idea. It's directly led to this idea of having to join a particular instance because of the community, and all the fallout from that around trusting the instance admin and such. Those concerns should be separate.
heh, well parking your name doesn't really mean anything because there are instances on domains all over the place and you're certainly not going to register on each one! Tho now that I think about it, you should be able to use your own domain for this: drupal.org/project/activityp…
hahaha sorry! Your instance did things sliiiightly different than others, so I was having to test my code in production, which resulted in sending you a lot of these!
yeah I guess that's one way to put it.
Back to the original point though, I would argue that 99.9% of of those examples in the crawl also do not rely on the extensibility model of JSON-LD.
They took all the good parts of Verifiable Credentials and turned it into the SmartHealth spec! spec.smarthealth.cards Notice you never need to bring in any JSON-LD library or deal with namespaces or canonicalization, yet it's completely decentralized!
I mean, you don't have to convince me of decentralization and openness. I'm not even tweeting this on twitter, it's coming from my own website, one of many decentralized nodes on the internet.
I'm saying the LD is irrelevant when most publishers and consumers are ignoring it. It's great the JSON-LD looks mostly like JSON, but IMO the LD part adds very little value.
fwiw I was able to implement vaccine QR code VCs without dealing with the LD part too!
yeah my point stands. The vast majority of publishers publishing JSON-LD on their websites for Google to consume care approximately 0% about the LD part of the JSON-LD, and frankly care about 1% about the JSON part. They just want Google to read the website.
That's quite a claim. Are you talking about the JSON-LD that Google recommends people publish for their rich snippets and such? Because I guarantee you about 99.9% of that is treating it as plain JSON.
Mastodon actually uses rel=me to show a "verified" badge on links on your profile!
This is also definitely in line with RelMeAuth, and what I implemented on indielogin.com, but as an authentication service, not just informational.
This morning I noticed I have a new feature in YouTube called "Go Live Together", an easy way to bring in guests to your livestream. So what better way to test it out than to try it LIVE right now?
Join me and @PhotoJoseph over here in 20 minutes!
youtube.com/watch?v=93xaRo4y…