You know whats awesome about the fediverse?
Developers working together. This isn't a competition. Everyone wins.
@dansup and anyone writing an activitypub application instantly has about 2 million users rather than starting from 0
@kaniini I am using GIthub pages for the pixelfed.org website. I didn't think cloudflare would be an issue, I turned down security to "essentially off". I am investigating OVH for DDoS protection when the site launches.
Someone please explain to me. AFAIK ActivityPub is a transmission protocol, not a storage one, right? You just send stuff to your outbox and the server resends it to your followers, but a blog is not simply a buffer of ephemeral stream entries. It's more like a permanent storage, with date search functions, etc.
So... how do we federate that? Can anone explain?
I think that if we want to federate web storage, we might need to install a whole new software in each federated server - BESIDES Mastodon or Pleroma or whatever - , so that users can retrieve the blog from their local instance, right?
Or am I making a fundamental mistake?
I've heard of plume, but it seems to me that it's specifically for blogs. It doesn't seem to cover full static webpages (html, css, js). If they can manage to pull it off, I'd be delighted.
However, I think we still need something more low level; a federated web storage framework upon which we can base other things.
@rick_777 @gargron static websites are federated because anyone can selfhost or find someone (among thousands of companies) that will host a webpage for you.
And the storage doesn't need to be standardized for everyone to access it, just the transport protocol - and luckily the HyperText Transport Protocol (http) is pretty widely adopted.
But if you want webpages that are hosted more peer2peer that the traditional federation of the web, then take a look at Dat.
My point is that one thing is to be able to upload/rehost content, but that didn't make the content federated. We need a way to a) Federate that content in real-time after a change is published, and b) to verify that I was the one who published that change.
What I'm suggesting here is multiple copies of a website rehosted and authenticated via ActivityPub or other protocol, so that you can browse your local instance and not have to depend on a single point of failure.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!