As the year winds down, thinking about the fediverse, I want to do a better job in 2024 of making the case for independent blogs. Lots of platforms with thousands of users on each server talking via ActivityPub is great, but more blogs also helps with portable identity and a more distributed web.
Great article from David Pierce at The Verge about the potential of the fediverse:
Forget the hand-wavy protocol stuff for a second — one of the best things about embracing ActivityPub is that it sticks a crowbar into a single Voltron-ic product like Facebook or Twitter or Snapchat and pries it apart into its component pieces, each one ripe for innovation and new ideas.
I'm not a web dev. The design process would often be the hardest bit. I even picked up React because it was *the* way to build interactive stuff. I would stop looking at the source once the site looked good enough (it never looks finished anyway).
In hindsight, that was overkill. If I could start over, I would go static and build on #11ty or #hugo.
A highlight from IndieWebCamp San Diego:
Them: “you can scroll if you want to”
Me: “you can leave your friends behind”
So, in my interpretation, @gRegorLove is issuing a token to my user...wpdev.gwg.us, but in his, he's issuing a token to his user that I'm allowed to use. I'm assuming his conception is based on his being the owner of the resource.
In my interpretation, when I grant a token to a client like indiebookclub, I’m issuing the token to that client and the token has my information in it. Similarly, with Ticketing, I’m granting a token to an individual site and the token has my information in it. In both cases the token is used to access something on my site.
I’m open to do this differently, but currently I don’t understand why it would be different. The issuer, subject, and resource seem to communicate all the information about who the token is for and how to use it.
A highlight from IndieWebCamp San Diego:
Them: “you can scroll if you want to”
Me: “you can leave your friends behind”
A highlight from IndieWebCamp San Diego:
Them: “you can scroll if you want to”
Me: “you can leave your friends behind”
Posting this here feels redundant, but hey.
https://www.theverge.com/23990974/social-media-2023-fediverse-mastodon-threads-activitypub
If you prefer to not use substack, you can find the #indieweb version over at: https://dreamindani.com/posts/bookmark-beat-ep18/
Some more context: this is specifically for Ticketing. I’m testing from staging.gregorlove.com and sending tickets to wpdev.gwg.us.
In my mind, sending a ticket to someone is analogous to an IndieAuth Client redeeming an authorization_code — both an authorization_code and a ticket are redeemed for an access token. As a result, my implementation for generating the access token hasn’t changed for the Ticketing flow so far. My access token response includes a me property of staging.gregorlove.com.
David’s implementation is apparently expecting that me property to be wpdev.gwg.us so he can identify which user the token can be used on behalf of (thinking specifically of multi-user environments like WordPress).
It feels odd to me to return someone else’s URL in the me property. It seems like the initial subject sent with the ticket should be verified by the recipient and used to determine the user on the site before redeeming the ticket. If a valid user isn’t identified, it should return an error instead of trying to redeem the ticket.
I think the main use for the me property in the Ticketing flow, so far, is as a reminder which site the access token can be used for. It might be displayed in an admin interface, for example.
@noellemitchell if you enjoyed that you might also like this resource I’ve been maintaining with all sorts of #webring and #indieweb goodies https://shellsharks.com/indieweb
I'm finding so many blogs and following their RSS feeds. Happy 6th anniversary to my first EP: "Purple EP"
https://erikaautumn.com/music/albums/purple-ep/
#musician #producer #IndependentMusician #IndependentProducer #artist #FreeMusic #music #BandCamp #AppleMusic #SoundCloud #Spotify #YouTube #Deezer #MusicProducer #IndependentMusic #IndependentArtist #WebDeveloper #IndieWeb
@eloquence Hey I have a fun lil website I work on with my music and art and links to many other fun indie sites!
https://wetnoodle.org
I don’t mind flying under the radar. There are benefits for a product to start small and grow slowly. But I’m still kind of puzzled why Micro.blog is rarely mentioned when articles talk about platforms that support the fediverse. We first added ActivityPub in 2018. Must be doing something wrong.