@Gargron @zack @jalefkowit Agreed about the minimum. I've been wondering about treating RSS as a bridging problem, trying to have a small number (maybe one, mostly) hosts doing the bridging using full OStatus. So you follow email@example.com (with full ostatus support) until the media lab is ready to do ostatus properly. Also maybe bridging reddit, tumbler, medium, ...
@maloki It's no joke. I was in the audience when this happened: https://medium.com/@natematias/dissertation-defense-918cf47fa45d
@jalefkowit @gcupc @bea @stefanieschulte I think the way to bootstrap out of this is for some large-user-base reader to consume some nice formats and show the demand. I nominate Mastodon as that reader. Not sure the right protocol/format yet though; ought to be figured out in concert with some large commercial content producers, like https://iptc.org/standards/rnews/
@jalefkowit I was on a public wifi the other day that was IPV6 only. It was hell. After I eventually figured out the problem, I still couldn't reach enough sites to break my way out. digitalocean and aws also not reachable. https://tunnelbroker.net/ seemed promising, but was pretty confusing. Also, since then I discovered that letsencrypt tends not to work if you have ipv6 enabled, although they've ack'd that as a bug, at least.
@maiyannah Alternatively, users who already have a github account could delegate that to the bot, but that's not helpful to folks who don't want a gh acct. Ha -- crazy idea -- user1 could let the bot use their account to post for user2. So your gh issues could show up under my name, but always starting, "I'm just relaying this post from OStatus user Maiyannah Bishop. This content is on her website at https://..."
@maiyannah Thinking about the UX for a second. Maybe it would appear like a user firstname.lastname@example.org? You mention it with tag #newissue to create an issue, then it boosts that, and replies to it are the commentary on the issue? If a project chooses, it could of course run its own bridge with its own name@domain, but for getting started we want this to work when the dev doesn't know or care. Problem, on gh, all the issues would be from the same user. :-(
@maiyannah @matteodem @ghedipunk @simonv3 Because so many folks are already locked into github, another option would be to add an ostatus bridge for github. I think an independent 3rd party could do that, but I haven''t worked through the details. I prefer not trying to convince everyone to move, but just letting the folks who want to move do so. Github could revoke its API key, but unlike some, I doubt they would.
@nolan Good article. More to the point that my blog post about this from ... a while ago... https://decentralyze.com/2008/10/27/what-is-the-web/
All y'all on Mastodon asking about how you can make your instances more inclusive or how Mastodon in general can be a more welcoming space for minorities:
Book me for a session and I'll talk to you about it.