Aaron Parecki

That is pretty cool!

That's awesome! Is it open source? I'd happily link to it in the Overland readme so people know they have another option!

I've never added any automatic trip detection like Moves had though. They really were the best at that.

Thanks! I've been collecting my location data since 2008, and since 2013 using Overland! The good part is you own the data, the bad part is it means you have to run a server to collect it somewhere.

as someone who flies @AlaskaAir a lot, it's always disorienting to step into the old Virgin planes, so I do appreciate the notice that they'll be updated soon!

do I detect a hint of sarcasm? I actually am legit excited for this lol

Oh no, I actually really like their hub! It hosts an HTTP API on it with no account crap, so you can control everything from the local network.

This sounds like a great thing to watch on the plane 😂

aw I miss when @ meant email and not Twitter

that is adorable i want it

Just for fun 😆 Or maybe eventually we add support in readers!

oh did you actually get the user's name and email address?

contains? The access tokens I was seeing were super short strings. I didn't see any user details in them at all.

Yes I did, but I have no idea what the access token can be used for.

Fantastic! Do you know the dates yet?

I've had this on my todo list for Aperture for quite a while: https://github.com/aaronpk/Aperture/issues/37

Moving a feed/subscription to a new channel does seem like something potentially useful for a client to do, although I'm not sure what I would want the UX of that to look like.

Before this ends up in the Microsub spec, I'd want to see at least Aperture and one other server support the feature on its own even without a client UI for it.

If any client developers have an idea for what this might look like in the apps that'd be great to see sketched out here as well.

Thanks for starting this discussion!

One of the main reasons to use h-feed and h-entry is that RSS/Atom really only can represent blog posts and podcasts. For those purposes, they're fine formats, but the reality is there are many more kinds of content on the social web today, such as replies like this one which can't really be represented in RSS.

What features are you finding that Microsub doesn't support? Like most of the IndieWeb protocols, Microsub is supposed to be an evolving protocol based on the needs and implementations of people using it. I don't expect that we will ever say "Microsub is done!" the way that some specs put a stick in the ground, since the reality is that things change and need to adapt to new use cases to remain relevant.

This is really cool! Out of curiosity, where are you seeing out of date information? If it's the wiki, we'd love to know which pages need an update so we can fix them!

Check out https://microcast.club as my modern take on a webring specifically for podcasts!