jdormit
commented
5 years ago Thanks for the encouraging words! A few thoughts on this:
with the project and codebase structured such that additional connectors become easy to add
This wouldn't be possible with this code base. It's tightly coupled with the way WordPress does things, uses WordPress-specific functions and classes, etc.
In general, I like the idea of building out a more generic ActivityPub connector for sites. I've thought about building out AP integrations for Hugo or Jekyll, although that's inherently problematic since ActivityPub requires dynamic responses from the server to respond to e.g. WebMentions, which makes it difficult to see how to build something for a static site generator.
My ultimate mission is to put the whole web into the Fediverse. I started with WordPress because WordPress runs 30% of the internet. But I don't think the way to do that is with some sort of generic library/SDK - I'm not sure such a thing is even possible, given how different every web content platform is. So I'm going to start with Pterotype (the WordPress plugin) and use it to build up interest in the Fediverse, to add lots of content to the Fediverse, and to learn what I can about designing federated software.
At some point in the future I will want to expand that - I've been thinking about ActivityPub clients that let you view/read/organize federated content in novel ways; ActivityPub-powered apps for businesses like federated wikis or bug trackers; even analytics and advanced marketing tools for ActivityPub services (nothing shady or privacy-invasive, though). Basically, I'm not sure what's next after Pterotype, and I don't want to commit to anything until I've seen this project out. There's still a lot we can do for the Fediverse with a WordPress plugin before we need to think bigger.
aschrijver
Hi @jdormit ,
Great project you got going here. I just found out about it, and love the idea. But there is one thing I was wondering about.. Aren't you selling this idea short, by positioning like this:
Why not position the project like your statement further on:
And then not just for blogs, but for content in general, positioning something like:
You'll just keep doing what you were before, creating a WordPress plugin, but with the project and codebase structured such that additional connectors become easy to add, and with more focus on the specification, documentation and API of the 'Fediverse connector' (which is not a bad thing, as with most AP projects the specs + docs are usually mostly 'hidden in the code').