If you are coming to FOSDEM, and will be at the AP panel in the decentralized internet and privacy room (or at my talk in the minimalist languages room) please drop by and say hello. I'll be wearing my GuixSD shirt :)
2) The reason DNS/SSL are so hard is *because* of the coordination with central authorities. 3) If your address was your key fingerprint, no need for a CA; you already know how to make a secure connection (why .onion does not need https) 4) SSL CAs are as weak as the *weakest* CA in your CA list. It only takes one badly acting CA for you to be man in the middled. 5) DNS and SSL CAs centralize the otherwise decentralized fediverse.
The demo I'm working on at this hackathon is for a secure way of hosting content so that if your instance goes down, your content can survive, and if your content becomes popular, the whole network can help balance the work of hosting it. #activitypub#wizardstower2019
Anyone can participate remotely! We will be chatting in #social on irc.w3.org
But you can also come in person if you can make it to Vlissingen! There is still plenty of space, and it will be in this cool tower: https://www.watertorenvlissingen.com/
Just got in my donation to Conservancy. Our donation is much larger than usual in order to reflect the proportionally important role that I think Conservancy is taking in the software freedom space. I hope you might consider donating also! https://sfconservancy.org/supporter/
@ted The recent fedidrama appears to stem from the pains of dealing with blocking-centric anti-abuse tooling. On a small level, that's hard enough; on an instance to instance level, it's going to end up with nation states.
Erin is the person who transformed the Pump API into the first draft of what became ActivityPub. ActivityPub wouldn't have happened without her hard work!
If you're thinking "gosh, isn't the opposite route of what several 'let's simplify activitypub' threads" have been going towards then yeah, it's in the opposite direction, because I think there's a real risk of losing a better future with making that the "standard".
So if you wonder why ActivityPub doesn't include webfinger, it's because we left ActivityPub open to be the fediverse of the future, not just the fediverse of today.
Okay anyway I said a lot of things here... but here's the general idea: current federation rollout assumes:
- there's one you - there's one path to get to you - one naming authority should get to define our names - when it comes to breadth vs depth, popularity is more important than deep relationships
But these assumptions comes from surveillance capitalism social networks. Reverse all of these and things get interesting.
Okay, lots of posts about "could you elaborate" so let me attempt.
What would we like? - Strong resilience to abuse, spam, dogpiling - Networks which focus on *deeper* relationships with your community rather than *popularity*... in depth vs breadth, depth matters more (this ain't a high school popularity contest) - support for anonymnity and multiple identities without increased support for abuse, spam, dogpiling
it frustrates me that I believe that the way we're handling identity and social relationships on the current iteration of the fediverse is Very Wrong, but it's just a lot of talk from me until I can demo with real code I guess
I hope we don't get locked into dangerous antipatterns before it's too late to shift the direction of the network