Lest my sudden reappearance look like a write-only attention grab: don't worry, I'm subscribed to a ton of you via RSS and I've been reading all your toots in my feed reader this whole time. This thing still works great: http://mastodon-feed-converter.johnholdun.com
Anyway I popped back in here because it's been a year since I started sharing the music I've been making, and I'm proud of this trip-hop jam I improvised live last night, to which maybe you're interested in listening: https://soundcloud.com/johnholdun/pepcumber
Oh hi Mastodon. My homebrew ActivityPub publisher thing still doesn't really work and I haven't taken the time to fix it, but I've been microblogging on my website and you can always subscribe via RSS if you like: https://johnholdun.com/microblog
@darius Have you read this? I think it aligns nicely with your CSVConf talk https://www.manton.org/2019/06/02/open-gardens.html
What does the #indieweb make of syndication versus content negotiation when it comes to microblogging with ActivityPub? Given that I have a microblog on my personal website, should I add ActivityPub alongside RSS as another way of consuming that content, or should I cross-post to e.g. this Mastodon account, in the same way I might cross-post to Twitter? I am torn.
My latest themed attractions pops up for one weekend only, April 18-21 in Park Slope! It’s about a dog and a cat who are roommates, it’s an art show AND a little story AND a place for you to hang out with me and be cute AND I am excited to see you! https://variablestage.com/attractions/bobbys-birthday
Also the sequel to this spec would swap JSON for HTML and provide a new perspective on building MVC-style websites.
Basically I was excited that JSON-API was so respectful of hypermedia in theory but then underwhelmed by how little it delegated to hypermedia in practice. The popularity of GraphQL has emphasized how powerful hypermedia is (by reinventing it) but we still have this whole other thing that's more mature and deployed everywhere that I think we should use more powerfully and thoughtfully.
One of these days I want to draft a API specification that is like JSON-API (https://jsonapi.org) but…
- URLs are determined by resources (strictly /:type/:id)
- Relationships have required URL counterparts (i.e. /:type/:id/:relationship is a 301)
- Resource objects are less strictly defined (the nested attributes/relationships with a shared namespace thing never felt right to me)
- filter, order, and pagination schemes are MORE strictly defined (a weird oversight of the spec imo)
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!