#tantekis that the first Micropub client in the Apple App Store?
davidmead joined the channel
#tantek!tell aaronpk is the Micro.blog iOS now in the Apple App Store the first officially published iOS app that is a Micropub client? That's probably worth blogging - since now anyone with an iPhone/iPod/iPad can download and use it (presumably with any Micropub server?)
#Loqiaaronpk: tantek left you a message 41 minutes ago: is the Micro.blog iOS now in the Apple App Store the first officially published iOS app that is a Micropub client? That's probably worth blogging - since now anyone with an iPhone/iPod/iPad can download and use it (presumably with any Micropub server?)
#aaronpkalmost certainly is the first Micropub client in the iOS App Store, but i'm not sure whether it's possible to use it without having a micro.blog account
[miklb], [dylanon], [chrisaldrich], jjuran, KartikPrabhu and tantek joined the channel
#[eddie]My whole internet suddenly broke and I couldn’t figure out why….. then I noticed I had “disable JavaScript” in my browser when I was testing my site without JavaScript
#Zegnatschmarty, that is really good news! libsodium seems nice as far as I have read about it :D
#ZegnatI was looking at libsodium to do public key signing for selfauth actually. Just deemed it more work than I had time to put in to it
#sknebelZegnat: libsodium is quite easy to use actually, that's the nice thing about it
#sknebelonce PHP 7.2(?) is somewhat available I'd revisit that
#ZegnatYes, I just wasn’t sure I was going to get private key signing for the tokens properly working without making mistakes in the limited time I had to get selfauth running
#sknebelsure, it's certainly an advanced feature, and right now not available to most users.
#sknebelhm, I should make a python version of the token signing in selfauth, then I could replace Kajas custom auth endpoint with selfauth
#ZegnatThere is sodium_compat, but that means extra dependencies that we didn’t want for selfauth either
[miklb] joined the channel
#sknebelyeah, unless we do some bundling etc (where I don't know if PHP world has tooling for it) more dependencies aren't so good
#ZegnatYou could bundle the entire selfauth + dependencies as a phar file
#sknebelI thought phar support that common on random hosts?
#ZegnatIf your server is correctly configured it can offer .phar files for public access and execute its contents (think of .phar as a folder with an index.php in that case)
#GWGI'm trying to figure out arguments for displaying location.
#GWGAnyone have any thoughts? I pass in longitude, latitude, and display name...or some combination therefore, and I'm trying to decide what options I would set for display.
#tantek.comcreated /Checkie (+463) "stub with dfn, app link, gh repo, brainstorming (want Micropub support), see also" (view diff)
#tantekGWG sounds like you may be solving the problem backwards? from the data up to display instead of from the UI/use-case down to the data?
#tantek.comedited /PASTA (+425) "expand dfn (why it matters), relation to backfill, see also" (view diff)
#tantekaaronpk, is https://github.com/aaronpk/Checkie worth moving to indieweb for some collaborative hacking? or better to develop it on your repo first before making it look "ready" for others?
#Loqi[aaronpk] Checkie: A lightweight foursquare client for the iOS
#tantekhey can you turn on "issues"? I want to file the "Add micropub support" feature request :)
#aaronpki think the recent discussion would lean me towards not moving it to the indieweb org yet
snarfed joined the channel
#tantekaaronpk, yeah that makes sense to me, and what I ended up leaning towards
#tantekmakes sense to keep the indieweb org repos more "real" and semi-immediately-usable by people that happen to stumble upon it
#tantekinstead of half-baked/implemented/old things
#aaronpki could at least save some state in cookies (i think localforage was a good wrapper?) but that still wouldn't give me the ability to have the photo continue uploading when the app is put in the background
#sknebeldgold: if hugo is quick enough you could run it directly from the PHP script and return a 201 afterwards. if it takes longer you should give the job to some kind of background queue
#Zegnataaronpk, why does the 202 also *require* a URL?
#ZegnatI was wondering about that not long ago. I think it came up in conversation somewhere.
#aaronpkso that clients have a URL to reference for the post
#aaronpkotherwise the client wouldn't have a URL to use to update the post for example
#ZegnatYeah, but that does mean asynchronous servers also must know the URL before processing the post. What if your URL is dependent on post type, like tantek’s? Still seems to force unnecessary synchronous tasks on the endpoint server I feel
#dgoldsknebel: im unsure how I can call hugo from a php script
#aaronpkZegnat: could always return an alternate URL that will eventually redirect to the real URL
#aaronpkkind of like how in wordpress every post has a URL like ?id=1234 even if you have custom URL slugs on
#dgoldhas his nanopub script dealing with different urls dependent on post-type
#sknebeldgold: I think PHP has "exec" to run external programs? but I'm sure someone with actual PHP experience here or Stack Overflow know better than me ;)
#ZegnatAh, so a Micropub client that gets a URL back should not treat that URL as canonical for the post?
#aaronpkZegnat: i'm not sure what the use case of treating or not treating as canonical is
#aaronpktwo things micropub clients do with URLs returned: show/redirect the user agent to the post, and store it internally to use for updates
#ZegnatSo show and redirect wouldn’t work for 202 as the client has no way of knowing when the URL gets populated. The second is the only usecase left than, though the endpoint will have to manage the client possibly having a URL in memory that is no longer a post’s canonical URL. While a secondary micropub client might try to send an update for a posts c
#Zegnatanonical URL (as discovered on the h-feed or something?).
#aaronpkthink of the alternate URL the same way it's dealt with for webmentions
#aaronpkif you receive a webmention with a target that is an alternate URL of your post (a short link on a different domain for example), you're still supposed to resolve that to the canonical URL when you're processing it
#Zegnatand yes, dgold, sknebel, PHP’s exec() can execute locally installed tools on the command line, that would include hugo.
#ZegnatThat would work, aaronpk. Just means storing an extra identifier with each post, one generated by the Micropub endpoint when it first receives a post.
#aaronpkyeah that'd be a consideration you'd have to do if you want to create the post asynchronously
#aaronpkmy endpoint creates enough of the post synchronously to get a URL and show most of the contents. I then have background scripts that go and "fill in" pieces of the post, like adding my gps location, fetching reply context or repost content, syndicating, etc
#sknebelI wouldn't expect much to break if you didn't return a valid URL anyways
#ZegnatI don’t really think servers wouldn’t be able to handle it. I just thought it weird that when asynchronous is specifically allowed by the spec, the Location was a requirement.
#Zegnatsknebel, neither do I, or a URL that will only work for a week or something, it is mostly the requirement of Location that stood out to me :)
#sknebelthat's an argument in support of "possibly shouldn't be required"
#[barryf]My site returns a 202 because post creation is async so I made Micropublish retry with a little countdown/spinner if it gets a 404 after creating a post.
#sknebeldgold: I run a private IRC server and aaronpks TikTokBot
#sknebeland my webmention verifier triggers a webhook on that
#sknebelhappy to help you set that up/publish docs on it
snarfed and KartikPrabhu joined the channel
#dgoldthanks sknebel I'd be delighted to take any/all advice
[kevinmarks], j12t, [miklb] and tbbrown joined the channel
#ZegnatHow/why the current Micropub implementations return 202 + Location:
#ZegnatKaku seems to use its own event system, queues a create event and then returns a 202 + Location. The “location” value is stored within the post metadata, it seems.
#ZegnatAruna also seems to use a job queue, but its URLs are simply a hardcoded https://j4y.co/p/ + $uid, so that is what always gets returned for the Location header.
#ZegnatTransformative seems to use octokit, which I think is a GitHub client, to store a post in a repo. I am guessing this is a 202 because the actual storing happens asynchronously (I did not dive into octokit). The location is taken from an absolute_url field on the post object, and I am not sure how it is getting filled.
#ZegnatKaku’s location value is simply generated from timestamp and the “slug” field on the micropub request
tbbrown joined the channel
#sknebelaaronpk: outside of updating cinch, did you check if any of the other updates you did to the Gems used by TikTokBot are important?
#aaronpkthe rest of the updates were because of updating cinch
#sknebelI think you just updated everything to newest available?
#tantek[chrisaldrich] noted that he wants facepiles to aggregate all the likes/reposts etc. responses out of the flow of the comments (e.g. on his FB mom-likes post)
#snarfednot great, since hsts-capable clients would need to use incognito etc to get back to http...but meh
#snarfedmore broadly, expiring ssl certs definitely hurt site longevity, but i think they're an argument for cert automation like let's encrypts, more than an argument against ssl
#snarfedie we work toward privacy/security *and* longevity, together, instead of a dichotomy
#tantekreally appreciate that analysis and conclusion snarfed