Ō̴̡̨͍͕̠̹̘͖͓̭̝̰̖͉̬̫͍̝̰̟͖͖̞͇̟̻̫͇̠̯̋̋̂ͅͅA̷̡̧͎̫̬͖̠͍̼̗̠͊̉̏̓̈́̂̀̈́͆͘͜uth @oktadev oauth.wtf oauth.net 🎥 livestreaming youtube.com/aaronpk aaronpk.tv 💛 #indieweb 🐘🦋
Portland, Oregon
Joined April 2008
- Tweets 11,388
- Following 1,223
- Followers 6,415
- Likes 9,609
How long are you going to be in Austin? I'm going to be there this weekend! Maybe we can grab coffee!
1
Yeah it is! Here's a post that outlines some of the technical details! aaronparecki.com/2018/03/12/…
1
1
This is the best.
I often describe my second favorite cocktail, the Boulevardier, as a Negroni but with whiskey instead of gin.
1
1
But then they literally have to visit Twitter to see it. I still think it's a cool idea and would help me stay in touch with more people but it still seems like only half a solution.
1
There is definitely already a *lot* of my content that doesn't make it to Twitter and you have to follow my website to see it. I hadn't considered actually promoting this fact on my Twitter account tho! Not a bad idea!
1
Wouldn't making my content available via a browser plugin that shows it on twitter.com still do exactly the thing you're talking about, not giving my tweeps a reason to stop visiting Twitter?
1
I've been stuck at the airport in Chicago since 6am. It's 5pm now. I've never been so happy to get on a plane. #travel #selfie #firstclass
12
I mentioned in my #OAuth talk last week that I was working on a blog post describing how to add the Device Flow to any OAuth server, and I just finished the post! \o/ 🔐 developer.okta.com/blog/2019…
3
8
and here is my previous post pushed out to Twitter and visible on Mastodon! #indieweb #ftw #distribution
2
1
1
Pretty pleased I managed to have this entire conversation with @lsanger on Twitter using only my own website and tools! Never had to visit Twitter or use any Twitter apps! Our #indieweb tools have come a long way! #ownyourdata
3
5
20
Every W3C working group has a defined start and end date up front, and they have to be renewed explicitly. Twitter and Facebook of course aren't going to support the group, (not that they are members anyway), and the space is still new to other companies.
It's a bit complicated, but there isn't a "W3C entity" that can be interested. Instead, representatives of member companies have to show support, and there wasn't enough interest from companies to keep it going after the 4 year charter was up.
Wonderful!
Yes, three of them are W3C Recommendations! There's also a few more pieces to the puzzle that were created after the W3C group concluded, more details here:
spec.indieweb.org/
1
I agree, but a good first start is to treat it as ephemeral and own all of the content you post there so it doesn't matter if it disappears. I see you have a blog, so you can do it right now! Start posting there and use plugins to syndicate to Twitter!
1
Maybe this example would help illustrate? Here's our conversation we've been having as far as I see it: aaronparecki.com/replies
It's true that I still need a Twitter account for this to work, but if Twitter disappears tomorrow I wouldn't care.
2
1
It would actually solve the issue with Facebook since they disabled their API and I can't post to it anymore. It'd be fun if my Facebook friends could still see my stuff! I'm just not willing to post there manually.
1
Yeah I do like that idea! I might have to experiment with something like that. All the pieces are already in place to have that work with the IndieWeb building blocks too!
1
This way none of my content really lives on twitter since it's all on my site. Twitter is just a channel for me to have conversations with people who don't yet post on their own websites.
1
Yeah basically 4 and 5 are covered by the idea of POSSE indieweb.org/POSSE but it works the opposite direction.
I'm writing this on my website, and it gets automatically copied to Twitter. I also am reading your replies in Monocle, my reader app.
1
2