@kik Yeah! Among other p2p protocols and regular static site publishing. Following @dripline and the hashtag #DistributedPress on here should be enough. I think we have RSS on dripline too. Also @sutty is intehrating it with their static site content management system which is nice to use.
Hey fedifolks! I was hoping to get some bikeshedding feedback on a new #FEP we're working on at #DistributedPress.
tl;dr we want #ActivityPub objects to link to #P2P URLs for alternate ways to load them. Right now I'm debating between putting them in alsoKnownAs or into the url field. e.g. "alsoKnownAs": ["<ipns://staticpub.mauve.moe>"] for @mauve
I worry that field is already in use and that it could cause trouble. Would a new field name be better? Maybe alternateURL?
@chrisg you are describing the mission of many projects and #SafeNetwork is the one I've been helping with for nearly a decade because it is driven by values I share.
The are others though, such as #DistributedPress which I only discovered today. It has similar values and is driven by a coop.
Proud of my team at Distributed.Press / @compost for releasing our new feature, the Social Inbox — It allows dweb websites to publish their posts directly to the Fediverse and integrate their comment section with users there.
Hey @mai, nice work. I was already following @dweb and have added @compost today because I like what you are doing very much. I did something much, much simpler in the past to publish static websites directly to both standard hosting and to #SafeNetwork a while ago but that work has been overtaken, though the website still exists.
I've had the pleasure of contributing to the development of the #DistributedPress Social Inbox with an incredibly talented team at hypha.coop @dripline.
This tool brings social interactions to static websites on the decentralized web. https://hypha.coop/dripline/announcing-dp-social-inbox/
writing documentation on the new stuff I've been doing with #ActivityPub and #DistributedPress and listening to this electronic music artist from Paris.
not sure what it is but french people know electronic music 🥰
We're finalizing our release so expect more info on how it works shortly!
For folks that don't want to mess with the technical details, keep wacth for @sutty which is integrating this functionality into their static site #CMS using Jekyll!
Anyone got an API endpoint of the "most blocked instances" handy? I wanna add it to the initialization flow for the #DistributedPress#SocialInbox
Ideally it'd be nice to say "Here's the top 100 most hated instances so you can preemptively block them if you'd like". It's not perfect but I think this would make it easier for small publishers to get started.
Instead of fancy frontends and databases, we're focusing on enabling statically published sites to add AP support via a lightweight Social Inbox server that they can register using standard HTTP Signed Messages.
#ActivityPub is like email but for social media. The #DistributedPress Social Inbox will enable you to get new comments and followers to your statically published website from any AP-capable service and will work across static blogs too!
@computersandblues We're currently coding it up. Aiming to have it ready by September :) I should have smaller milestones before then that folks can try out though. I'll be using the #DistributedPress tag for updates.