Post B5wiX7r4UGRiTTXhJI by Profpatsch@mastodon.xyz
 (DIR) More posts by Profpatsch@mastodon.xyz
 (DIR) Post #B5v7HHjW6NCT11dGme by Profpatsch@mastodon.xyz
       0 likes, 0 repeats
       
       your daily dose of json+ld, #fedidev
       
 (DIR) Post #B5v7HHurQCH3aCwKSu by icedquinn@blob.cat
       0 likes, 0 repeats
       
       @Profpatsch one of the worst of the glorified stick prefix in front of string systems
       
 (DIR) Post #B5wiX7KSRWMGqKHeTY by phnt@fluffytail.org
       0 likes, 0 repeats
       
       @Profpatsch enjoy: https://github.com/swicg/activitypub-api/issues/1#issuecomment-3708524521
       
 (DIR) Post #B5wiX7WVii01RhvHGK by Profpatsch@mastodon.xyz
       0 likes, 0 repeats
       
       @phnt OAuth is another “standard” that we should develop some workaround for
       
 (DIR) Post #B5wiX7kgrzLG9gYbMe by thisismissem@activitypub.space
       0 likes, 0 repeats
       
       @profpatsch@mastodon.xyz OAuth 2.1, which is what I've been steering people towards is much safer and easier to implement than OAuth 2.0 as a lot of the security footguns have been solved or very well documented. We will end up with an OAuth profile for ActivityPub, but it'll probably just be mostly identical to the OAuth profile from AT Protocol.Though, at the same time I'll often ask "do we really need OAuth for this, or would ... be a better solution?"
       
 (DIR) Post #B5wiX7r4UGRiTTXhJI by Profpatsch@mastodon.xyz
       0 likes, 0 repeats
       
       @phnt If you depend on specialized “profiles” for a “standard” with multiple RFCs of thousands of branching MAYs and MIGHTs, your just sidelined any non-professional developers into never being able to interact with your protocol
       
 (DIR) Post #B5wiX8AZJm2fRwfGhU by Profpatsch@mastodon.xyz
       0 likes, 0 repeats
       
       @phnt corollary: if you need people to include libraries with the footprint of multiple garbage trucks just to interface with your thing, your thing is GARBAGE, sorry I don’t make the rules …