I looked through the DreamWidth source code to see if I could implement full-history syndication feeds for them, but they don't have things like querying for posts oldest-first, so it's more invasive than I feel like tackling right now.
Also it's in Perl which would be the fifth programming language I'd have worked on this stuff in over the last ~2 weeks, and the third one I've had to (re-)learn, and I'm getting kind of tired of switching languages this fast.
People who say San Diego doesn’t have seasons are mistaken. We have many seasons:
If you’re familiar with OAuth, this introduction to IndieAuth walks through the process of how auth for the open web works. Really happy that Micro.blog supports this now.
→ 2018/07/07 3:41 pmThoughts: The requirement of apps to have a publicly accessible website conforming to the IndieAuth API might be a limiting factor
On the other hand, globally unique identifiable apps is a huge benefit in terms of admins being able to restrict app access. I.e., currently every user can revoke app access to their account, but server admins cannot say "I don't want the cross-poster to work with my server" because there is no such thing as *the* cross-poster
IndieAuth sounds interesting as a more generic way for federated applications to allow app registrations https://indieauth.spec.indieweb.org/
The question is how do we adapt this after our current, extremely similar but somewhat different system has been in production use for around 2 years #mastodev
