#Loqi[gRegor Morrill] I signed up for a https://micro.blog account and added my Atom feed. All went smoothly and I appreciated that it accepted the Atom feed even though the form requested “RSS feed.”
The only bug I’ve noticed so far is that images with a relative...
#tantekgRegorLove: did you check to see what the Atom spec says about relative URL resolution?
#schmartyi was. i set it up on a whim to test things against back when aaronpk and snarfed were doing initial research into federating with it, but ended up using it quite a bit.
#schmartybecause i didn't expect to keep it around, i used a random docker quickstart.
#schmartythat worked until i upgraded it, which recreated the db and destroyed everything. :}
#schmartyso i studied the docs enough to persist the db and image uploads and started over, refollowed everyone, etc.
#schmartythat worked for several months and upgrades, until docker images filled the disks.
#schmartyi tried to purge the unused docker images, but purged... all the docker images.
#schmartyit's all good! in the long run i would rather use something like bridgy fed to interact w/ the fediverse, and follow the folks there using an indie reader.
gRegorLove, jeremycherfas, AngeloGladding, leg and sknebel joined the channel
#sknebel[kevinmarks] regarding the packaging proposal, since they want to prove that the document is from the source domain, without the browser contacting it, a signature is what they need IMHO. Also adding non-repudiation to HTTPS along the way if I see this correctly (interesting for archives)
eli_oat, dougbeal|mb1, snarfed, loicm and [eddie] joined the channel
#[eddie]micropub JSON syntax. When sending a micropub request in JSON, do you prefix properties with mp-* or do you embed the mp properties within an mp object? I couldn’t find any clarity on mp properties in JSON syntax in the spec
#ZegnatProperties get the mp- prefix if they contain data for the Micropub server to handle, and not to store/be-part-of the microformats object. You can make it 100 mp- properties, or just 1 mp- property specific to your server and have a config object inside there.
#ZegnatThough for properties that several server implementations share, they probably expect them as separate properties on the main object. Makes interoperability easier.
#[eddie]ohhh okay. Yeah I’m thinking about mp-syndicate-to
#[eddie]so you would have a json object with { type: [h-entry], properties: {}, mp-syndicate-to [syndicate-url] }
#Zegnatmp-syndicate-to would go inside the properties object, I believe.
#[eddie]so just type and properties keys on the root level object. Everything else goes into the properties object, any micropub server communication gets the mp- prefix
#[eddie]I’m pretty excited. I build a native MicropubPost object in Swift, and I’m building in a method where you provide either ‘urlencoded’ or ‘json’ as an output value and the MicropubPost object will convert itself into the body content needed to be sent
#dgoldmp-syndicate-to is an _instruction_ to syndicate to these places; syndicated-to is for _already_ existing syndics
#dgoldoh. hell, I was scrolled back. never mind me, zegnat is righter
#ZegnatNote that not all micropub bodies have valid urlencoded variants, [eddie]. If you have properties with objects in them (e.g. in case of `content: { html:"" }`) you *must* use JSON
#dgoldthere's that weird guy, hangs around here a lot... writes _great_ documentation!
tomasparks joined the channel
#sknebelhm, that there is no mp- example with JSON in the spec seems like an oversight. aaronpk, can you still make such purely informative changes, or is that completely process-frozen now?
#aaronpkI think technically we can fix typos, but can't make any other updates to the doc
#aaronpkit would have to be pretty extreme to make a change too because the WG isn't actually active this year
#sknebelat least according to apples dev-documentation they'll use wrongly sized favicons if available, and if you don't link any just try the filenames on root
calumryan joined the channel
#tantekI wonder if iOS now supports space-separated rel value parsing for the icon
#tanteksknebel++ btw for redirecting the convo here
#Loqisknebel has 28 karma in this channel (84 overall)
#tantekhas anyone tried / depended on rel="icon apple-touch-icon" ?
#tantekgRegorLove: interesting. I wonder what the reasoning is. perhaps just omission? those pages all could start with an h-feed of posts, and use JS to auto-update
John___, tantek_, tantek and snarfed joined the channel
#gRegorLoveZegnat, ultimately self-hosting a reader was my goal too. I love woodwind.xyz but it's been having issues, understandably, as kylewm isn't available as much to maintain it.
#tantekI'd still like to figure out an incremental development path from including integrated reply-contexts in posts on your site to ... an integrated reader on your site
John__ joined the channel
#aaronpkI'm happy to make accounts on Monocle for anyone interested in building on top of it
#tantekmy sense is that there are useful steps along the way, each of which is both not too hard to implement, and provides actual user benefit when built.
#tantekI still need to validate that sense by improving my own reply-context retrieving / presentation on replies on my site
#tantekI'm not saying there shouldn't be separate / standalone reader UIs like Woodwind and Monocle, rather that that represents existing (pre-social-media) models / apps, and that a compelling UX (as compared to social media) for gens 2-4 will require integrated /reader UX.
#ZegnatMicrosub can't replace Feedbin for me without per item readstate, aaronpk :(
#tantekZegnat: I think I understand the need for per item readstate (some "feeds" I definitely want to make sure I see / read every item?) - could you add what your thoughts are on that to https://indieweb.org/reader#Challenges ?
#tantekhappy to help iterate, but I'd like to start with your description of "per item readstate"
KartikPrabhu joined the channel
#tantekgoes to add his "incremental path" thoughts to Brainstorming
#ZegnatI'll look into the Micropub and reader pages when the TV show I'm watching is over.
#tantek.comedited /reader (+1367) "/* Brainstorming */ Incremental development path to an integrated reader UX" (view diff)
#sknebelyes. most microblogging doesn't make sense to follow per-item. with per-item tracking + bulk-commands in the API the reader can relatively easily offer both
#ZegnatI already have some podcast feeds in my reader set to show chronologically rather than rev-chronologically. It is definitely very content dependent
#LoqiIt looks like we don't have a page for "microblog" yet. Would you like to create it? (Or just say "microblog is ____", a sentence describing the term)
#LoqiIt looks like we don't have a page for "microblogging" yet. Would you like to create it? (Or just say "microblogging is ____", a sentence describing the term)
#tantek[kevinmarks] I think that's unnecessarily conflating *possible* plumbing (attention.xml) with the UX requirements (what me, Zegnat, sknebel are talking about)
#LoqiZegnat puts his view on the read state discussion on the wiki
#[kevinmarks]There is an attempted microformats process gathering existing "I've read this" stuff there
#vanderven.se martijnedited /Microsub-spec (+2132) "/* Feedback */ My view on the two types of feeds, why one needs per-item tracking, how it does not compare to emails but to real life magazines, and an anti-pattern I have seen abused." (view diff)
#Zegnatsknebel, do feel free to review my thoughts. They got a little, uh, longer, than yours ;)
#ZegnatI hope the concept I am trying to convey is clear. Concepts are sometimes hard to express in non-native languages, no matter how fluent you think you are.
#Loqi[Aaron Parecki] I'm doing basically this already thanks to @superfeedr doing all the crawling! It translates any mention of my site into a Webmention which I handle like every other Webmention, which sends me a push notification to my phone! https://aaronparecki.com...
#tantekthis is potentially applicable to the /reader discussions
leotsem1, j12t and oodani joined the channel
#tanteke.g.a reader like Woodwind or Monocole *should* be able to use registerContentHandler to register to handle the application/atom+xml and application/rss+xml MIME types, thereby turning every *existing* link to an Atom or RSS feed into a double-opt-in Follow button!
#tantekaaronpk ^^^ thoughts? worth filing a /Monocle issue for ?
#aaronpki guess that would solve the problem of ending up on ugly XML pages when clicking feed buttons
#tantekwhich is an awful lot of existing links out there
#tantekI mean imagine if we suddenly upgraded all those RSS/Atom links to actually work like confirm-to "Follow" buttons without the sites having to do anything themselves?
#tantekin the reader of your choice? (a reader service like Woodwind, or your own site with its integrated reader!)
#tantekcaveat: currently *only* supported in Firefox (and at risk of removal!), HOWEVER, given implemented use-case like that, we could flip that and make it an actual standard that other browsers supported
#LoqiIt looks like we don't have a page for "RDS" yet. Would you like to create it? (Or just say "RDS is ____", a sentence describing the term)
oodani joined the channel
#aaronpki mean dreamhost also manages mysql for you :P
#tantekmore possible use-cases for registerContentHandler:
#[cleverdevil]RDS is Amazon Relational Database Service, a managed relational database service that is part of Amazon Web Services (AWS). RDS provides MySQL, MariaDB, Oracle, and other RDBMS's as a managed cloud service, including automated backups, provisioning, scaling, and more.
#leotsemI'm getting a "Could not find your authorization endpoint!" but AFAIC I've setup the appropriate meta-tags etc. I feel like I'm missing something but I'm not sure what :/
#aaronpkleotsem: what's your site? I can take a look real quick