Post
This is likely not what you seek in terms of simplicity, but I wanted to mention in the context of earlier discussion on #ActivityPub JSON-LD versus #RDF XML.
The #openEngiadina project for a long time pursued an ActivityPub-based implementation for its open local knowledge network, but found it too complex, esp. in the areas where the specs are immature and incomplete.
So the research project switched to #XMPP/RDF and had some good experiences.
Oh, what also just comes to mind is the #Polyproto protocol. I think it may have been created in reaction to ActivityPub's complexity and issues around identity, not sure.
And another protocol in the works, inspired by AP is #Versia.
What I notice is an uptick in interest in #Hypermedia and using the open web standards as intended and best supported in browsers.
You see that in web frameworks that go for radical simplicity, like #Datastar at https://data-star.dev where the front-end offers intermediate-mode #UI and logic shifts to the back-end.
What I found interesting (for its concepts) many years ago when #LinkedData was still hottish, was the #Hydra hypermedia project.
I'll keep adding, as I just bumped into some great feed reader best-practices to share..
https://rachelbythebay.com/frb/
https://rachelbythebay.com/fs/help.html
A space for Bonfire maintainers and contributors to communicate
