Posts by a@layer02.net
(DIR) Post #B4BhD8wRSXrdrvKXWi by a@layer02.net
0 likes, 0 repeats
@icedquinn @vic nestedtext-ld
(DIR) Post #B4BhkUQiaTG24OOPBo by a@layer02.net
0 likes, 0 repeats
@icedquinn @vic the fact that everything is a string is actually really good because rdf is basically that for anything that isn't a reference (except it has datatyping to sort of "cast" values from string to something else)
(DIR) Post #B4BhtILcsTblCiD33Y by a@layer02.net
1 likes, 0 repeats
@icedquinn @coolbean @vic activitypub is impossible to implement because it's incomplete and everything you need to complete it is out of scope (authentication/authorization, trust model, etc etc)fedi is a nightmare to interop with because everyone filled in the gaps differently and even worse they use the little that *was* specced in ambiguous and nonspecific ways instead of defining their own terms or using the terms as officially defined (and then the behaviors are basically totally undefined)json-ld group is doing yaml-ld because believe it or not, some people actually asked for it and intend to implement it (as well as cbor-ld) so they have an actual mandate for doing this and didn't just decide to do it on their own
(DIR) Post #B4BmUL2YEKKy5MCrS4 by a@layer02.net
0 likes, 0 repeats
@phnt @icedquinn @coolbean @vic > fully compliant JSON-LD parsers for Python, Ruby, JavaScript and Elixir minimally,https://json-ld.org/#developers lists all of those and more...python: https://github.com/RDFLib/rdflibruby: https://github.com/ruby-rdf/json-ld/javascript: https://github.com/digitalbazaar/jsonld.jselixir: https://github.com/rdf-elixir/jsonld-expython and javascript probably have the best library support for this, with java and rust and c# not too far behind. php is lagging behind, though.> there's exactly zero need for itthere's zero need for it *if you exclusively use only properties defined in activitystreams, exactly as https://www.w3.org/ns/activitystreams.jsonld describes them*. anything not defined there is ambiguous. there are 3 ways to make it unambiguous:- use a jsonld processor to expand shorthand terms to full identifiers- use pre-expanded full identifiers- use a central registry that everyone agrees to use IANA-style, bound to some media type or profile (like how application/activity+json specifies the meaning of terms)@icedquinn has it correct. mastodon uses properties like "featured" and "discoverable" which by default have no meaning whatsoever in AS2. you can't assume these terms are always being used the same way mastodon uses them. "featured" might be a boolean indicating that the current object should be promoted, instead of a reference to a collection of pinned posts. "discoverable" might imply different things depending on if you follow mastodon's interpretation or not (say for public timelines instead of for profile directories or search results).the bigger problem is that even the official AS2 terms are being used in ways not according to their definition by mastodon, and other softwares also have different overloading of the terms. "to" being expected to always be an array or not, "attachment" being expected to be ordered when it isn't, etc etc etc etc... there's dozens of papercuts in how the same terms get used differently by different softwares, which should flat-out never happen ideally, but unfortunately linguistics is what it is.even bigger than that: the vocabulary is only a foundation for describing activities, which don't have consistently agreed-upon behaviors, constraints, or expectations. this is assuming the softwares care about activities at all and aren't just fetching notes or articles from origin. and even *that* assumes they care about the notes and articles and aren't just transforming it into some bespoke internal representation which isn't shared by any other software.honestly for fedi purposes it is mostly a mistake to try and standardize on one vocabulary and format because all it does is encourage people to bend and twist and break the standard to fit their own purposes, when what they really ought to be doing is developing their own controlled vocabularies to describe what they're *actually* doing -- and map equivalences between that and some eventual standard (that comes from surveying the landscape after it's less experimental). so for example, mastodon should be calling them Accounts and Statuses, namespaced within their own namespace, mirroring their codebase's models in app/models/status.rb and so on. this doesn't preclude them from *also* describing their entities with other vocabularies -- the same thing could be a mastodon:Status, as:Article, sioc:Post, you name it, if it fits it fits. treat it a lot more like an API than letting mastodon hollow out AS2 and use it as a rubberstamp for legitimacy.
(DIR) Post #B4BmX8176eysYzrejI by a@layer02.net
1 likes, 0 repeats
@coolbean @icedquinn @phnt @vic websub would fix Follow activities being broken, at least
(DIR) Post #B4HNomCbcTEWDIJlp2 by a@layer02.net
2 likes, 2 repeats
@shibao you rn
(DIR) Post #B4IE5sfK2PzMnXE89o by a@layer02.net
0 likes, 0 repeats
@pry inoreader
(DIR) Post #B4JxeGFbXsEKt4vRvk by a@layer02.net
0 likes, 0 repeats
@pry i haven't seen any, but i wouldn't know, i use ublock origin
(DIR) Post #B4JxeGU8fpr9c9j3aK by a@layer02.net
0 likes, 0 repeats
@pry https://www.inoreader.com/blog/2024/10/the-new-inoreader-experience-is-here.html> Oct 15, 2024> No more ads: The Free plan no longer contains ads, providing a cleaner view that allows you to focus on what matters most.i guess it used to at some point? seems like not anymore
(DIR) Post #B4JxeGiJp7COK8MNge by a@layer02.net
0 likes, 0 repeats
@pry the free version is limited to 150 feeds but i only have 17 in there
(DIR) Post #B4KDwUrrXKrMhUXPLE by a@layer02.net
0 likes, 0 repeats
@pry in theory i wanna selfhost my own thing that consumes rss/atom (among other formats) but in practice inoreader is more convenient because it has mobile apps that don't suck, so it falls into the "good enough for now" hole for memay end up writing my own thing eventually