#dev 2021-06-27

2021-06-27 UTC
[jacky], samwilson and jeremycherfas joined the channel
#
astralbijection[
Why is quill reporting that something went wrong with my micropub endpoint when I create a post? The post got created, it returned a 201 created status, and there is a Link: in the header, which I believe follows the micropub spec.
#
astralbijection[
Wait, never mind, I'm stupid. It's supposed to be a Location, not a Link header
jeremycherfas, samwilson, [fluffy], [tantek] and jjuran joined the channel
#
[tantek]
what is a hashtag
#
Loqi
hashtags are the use of the hash "#" symbol followed immediately by a word/phrase/abbreviation to explicitly denote a topic inline in a post https://indieweb.org/hashtag
#
[tantek]
hmmm, I thought I'd documented my use there but apparently not (cc: KartikPrabhu)
#
KartikPrabhu
great, so I know where to find it now. Have you also done something similar for "@" ?
#
[tantek]
yes, that was easier
#
[tantek]
what is autolink
#
Loqi
An autolink is a hyperlink that was automatically added to some text to link that text to an obvious or useful destination, like hyperlinking a URL in plaintext to the URL itself, linking hashtags to search results, and @-names to their profile pages https://indieweb.org/autolink
#
[tantek]
though the Python version may be out of sync
#
KartikPrabhu
:thumbsup:
hendursaga, eco, samwilson, pepperoni_, hendursa1, KartikPrabhu and capjamesg joined the channel
#
sknebel
what is analytics?
#
Loqi
analytics is the collection, analysis and reporting of a websites traffic https://indieweb.org/analytics
#
sknebel
analytics << https://github.com/berthubert/audience-minutes self-hosted tracking of time spent on articles
#
Loqi
ok, I added "https://github.com/berthubert/audience-minutes self-hosted tracking of time spent on articles" to the "See Also" section of /website-analytics https://indieweb.org/wiki/index.php?diff=76190&oldid=76169
#
Zegnat
That looks interesting
#
Zegnat
bookmarks for dayjob
#
GWG
Morning, Zegnat
Seirdy and [manton] joined the channel
#
[manton]
I was out of town yesterday and missed the pop-up… Thanks everyone for writing up the notes. (Will try to rewatch the video too when it’s online.)
#
[manton]
Speaking of private data, I’ve tried a couple times recently to export my Foursquare/Swarm check-in data and never receive the download link. The RSS feeds are also broken. Concerned that I’m putting more location data into a black hole now. Export working for anyone else?
#
GWG
[manton]: It's online already
#
GWG
I uploaded it yesterday
#
GWG
[manton]: aaronpk was just talking about an export script he'd hacked together
#
Zegnat
Did you also upload the group photos, GWG? I did not see those anywhere
#
[manton]
@GWG Thanks!
#
[manton]
Maybe I need to write my own script too. There’s also a script linked on the wiki at /Foursquare but it’s 404.
#
[manton]
Micro.blog can import Foursquare’s JSON export, but that doesn’t do a lot of good if their export is broken. Sigh.
#
aaronpk
i used the API to page through 250 results at a time, it worked great
#
aaronpk
i only needed the stuff from before OwnYourSwarm too. everything since I launched that is already on my website
shoesNsocks and Seirdy joined the channel
#
GWG
Zegnat: I totally forgot, thanks for reminding me
#
GWG
I need to experiment with the Foursquare API for backfilling venue support
[fluffy] joined the channel
#
GWG
Zegnat: How comes the ticket auth?
#
Zegnat
I need to do some restructuring of my token endpoint to support tokens from tickets
#
Zegnat
E.g. my tokens are always me=mywebsite
#
GWG
That's why I'm starting with receiving over sending tickets.
#
GWG
I need the same sort of restructuring.
#
[fluffy]
Once someone has a ticket endpoint to test against I can finally get around to justifying spending time to implement the TicketAuth flow on Publ. 🙂 I have most of the stuff necessary already, I’m just missing the actual ticket grant flow.
#
GWG
[fluffy]: Zegnat's your person
#
Zegnat
What did I do now?
#
[fluffy]
I still have to decide whether I want to put the endpoint discovery into Authl’s profile parser (which would save an http request but require adding it on a per-identity-type basis) or into Publ’s login flow (which would allow things that aren’t IndieAuth to support it). Given how galactically unlikely it is for anyone outside of IndieWeb to support it I’ll probably go with the former.
#
[fluffy]
I mean it’d be really cool if, say, Mastodon grew that feature, but the chances of that seem to be approaching 0.
#
[fluffy]
Oh, right, for the Mastodon use case that’s why I still want to add native ActivityPub eventually.
#
[fluffy]
And I can’t think of any other identity provider where it could even remotely be relevant, unless we somehow convince Twitter/Facebook/etc. to allow users to provide arbitrary endpoints on their user profiles.
#
[fluffy]
And given Twitter’s weaksauce explorations into reinventing federated social media the long way around and Facebook’s Facebookiness, those again seem ridiculously unlikely.
#
GWG
Zegnat: A ticket endpoint to test against
#
Zegnat
I am wondering what the https://indieauth.spec.indieweb.org/#access-token-verification-response of a ticket-given token will look like, at the moment
#
Zegnat
Thinking about setting the ticket endpoint as client
#
Zegnat
Or maybe the verification response should be something completely different. Hmm.
#
GWG
It should be the same, except adding the extra parameters
#
GWG
Resource and subject
#
Zegnat
I just assume all tokens have a me. And in this case, I think me=subject. Not sure how I will handle resource. I might just not handle it at all. Just like default indieauth tokens, manage all the rights through scopes and not also add resource/realm scoping
pepperoni_, [chrisaldrich], alex11 and samwilson joined the channel