WeChat ID
aaronpk_tv
-
I'm very pleased to announce that Oxford #indiewebcamp is officially happening on the 22nd and 23rd of September! Thanks to sponsorship from @haybrookIT and @WhiteOctober. More details here: https://polytechnic.co.uk/blog/2018/08/oxford-indiewebcamp-is-go
-
This is definitely something that I want to do in the near future https://aaronparecki.com/2018/03/12/17/building-an-indieweb-reader thanks for the inspiration @aaronpk!
-
I agree with your sentiment but all I see looking at this map is that it was made in ArcGIS Online and it doesn’t have retina tiles. 😭
-
I've read about technologies under the umbrella of the "Indie Web" before but never really leaned into it. I'm categorically compelled by the idea now! It feels like an attempt at reclaiming some of what we've lost on the internet: https://indieweb.org/
-
@fiona i wish mastadon, indieweb websites and micro blog would be able to work together as one network.
-
"Dear @cwebber, I don't suppose you have opinions about how to implement a web of trust system for the fediverse???"
Heck yeah I have opinions, and here's how you do it: you combine it with a petnames system: https://chat.indieweb.org/social/2018-08-14#t1534216302328700 -
by signing your objects with LDS or another scheme, it allows a hostile implementation to boost them even if they are not public (!)
if you do not sign your objects, then they will have to be referenced with a pointer, these pointers are known as "capability URLs" and allow for your instance to make the access control decision (your code can either give them the object or not based on what they gave you) -
Great to see podcast apps picking this up again 🎉 Was our biggest success at Flattr in my opinion - that clients could discover Flattr-capability in the RSS and eg. auto-flattr episodes. We promoted and used rel-payment ourselves and I long ran a site listing supporters.
-
Mastodon is compatible with litepub by the fact that litepub is a subset of the specific variant of activitypub that Mastodon chose to use.
But I think litepub has better security attributes, because of the strong requirement for using pointers (capability IRIs) to content not controlled by the local instance.
Mastodon security posture is that LDS is good enough because Delete messages can be redistributed along the DAG (the acyclic graph of peers of peers all the way down known as the fediverse) to ensure object integrity. but, the reality is pushing state around is harmful. instead, litepub's requirement for capability IRIs solves the problem cleanly.
there are some edgecases involving tracking what instances have received an object, but it's not impossible to solve those.
I strongly believe based on real world experience that simpler protocols are more robust. LDS method is more complex than the methods proposed in litepub... -
Also reposting this on the new instance:
If any mastodon devs are looking for design help and would like a hand from the original designer of blogger.com, who recently redesigned the WordPress.com Reader, and wrote an early book on the design of community spaces online, let me know because I can put you in touch with him.
Because he’s me. Hi. Let’s talk.
