#dev 2021-09-19
2021-09-19 UTC
# 
astralbijection[ yesterday and today, i wrote a webmention receiver in rust that commits its received webmentions to a git repo
# astralbijection[ it's still very much a work in progress (i still need to implement a lot of stuff, like auto-creating a pull request for it, processing the webmentions in parallel, etc)
# astralbijection[ also the mentions are in the git repo, but i still need to display them too
# astralbijection[ oh right i should probably link the repo lol https://github.com/astralbijection/astrid.tech/tree/main/wm-receiver
# astralbijection[ here is what the folder containing all the webmentions looks like: https://github.com/astralbijection/astrid.tech/tree/main/content/webmentions
# astralbijection[ it writes as yaml rn but i'm changing it to use json instead
akevinhuang joined the channel
# astralbijection[ still need to come up with a name for it that's more interesting than `wm-receiver`
Seirdy joined the channel
# astralbijection[ not yet
# astralbijection[ i do have a name idea for a webmention sender, though
# astralbijection[ so i want to make this sender platform-agnostic
# astralbijection[ the idea is, it's a CLI app that you run on a webpage, or RSS feed
# astralbijection[ it crawls to find posts
# astralbijection[ parses those posts for microformats, and sends webmentions to every link inside a microformat
# astralbijection[ it also hashes the microformat data, and uses that value to determine whether or not you changed your post
# astralbijection[ so it can send an update
# astralbijection[ then, it stores all the webmentions it sent on a file
# astralbijection[ it's a crawler, and it sends, it's spidey-send
# astralbijection[ oh, it exists already?
# astralbijection[ that's true
# 
Loqi Telegram is a cross-platform encrypted messaging app https://indieweb.org/Telegram
# Loqi Telegraph is an open source API and service for sending webmentions, part of the p3k suite https://indieweb.org/Telegraph
voxpelli joined the channel
# astralbijection[ ah, in that case i can do this project later then
# 
[snarfed] kevin's is https://mention-tech.appspot.com/ ? there's also https://webmention.app/
akevinhuang2, hendursa1, Jack, jacklowe[d], Zegnat and [KevinMarks] joined the channel
# 
[KevinMarks] There is a sending part to mention.tech too, but it doesn't crawl all pages, just one.
tetov-irc and Murray[d] joined the channel
nertzy joined the channel
hendursaga and shoesNsocks1 joined the channel
# 
Zegnat I guess I am thinking of how IndieAuth can make use of the introspection standard with defining as few things as possible. If it continues to be its own endpoint, the only thing we define is how to discover it, which sounds like an essential part of IndieAuth anyway (making OAuth endpoint discoverable for non-registered clients). And then we could declare authentication on introspection optional for accessing information about a token
# Zegnat I am just not sure if existing verification being on the token endpoint (which is an extension IndieAuth does to OAuth token endpoints) is a good argument to now make the whole of the Introspection spec and extension to the token endpoint. Maybe there is a good argument for it, which is why I am still thinkig about it.
# Zegnat I guess I do not see a problem with <link rel="token_endpoint introspection_endpoint href="https://example.com/token_endpoint"> for people who want it to be the same thing without any risks, instead of the IndieAuth spec forcing them to be the same thing. That feels like we are just breaking some of the OAuth 2.0 compat we put back in with the last big update. I just haven’t been able to put my finger on why I feel that way though
shoesNsocks and nertzy joined the channel
# 
capjamesg[d] GWG I have built my own.
# capjamesg[d] But it is in need of a bit of work.
# capjamesg[d] Technically it complies with the spec on the core functions but I have been spending most of my time working on the search engine.
# capjamesg[d] IndieWeb time, that is.
# 
jamietanna Sorry GWG I think I missed where you sent the link to the code? Or were you just thinking of talking through how it works
# jamietanna Thanks GWG I missed that. I've added a few comments - looking good :)
# [KevinMarks] PESOS request - do we know of a tool for this? https://twitter.com/mxtaliajane/status/1439657798070067205?s=20
# 
@mxtaliajane I’ve been reporting from @taliaotg (which Andy also tried mass reporting into oblivion) but this account has a massive backlog of work from before I made the alt. I’d like to download my data but with media integrated/playable — twitter data download doesn’t do that. Suggestions? (twitter.com/_/status/1439657798070067205)
shoesNsocks1 joined the channel
# jamietanna Yeah I'd very much like to have someone using it outside of the IndieAuth clients I use for my personal services
# jamietanna *have a client performing refresh_token grants
# capjamesg[d] GWG Can you share a link to that code? I am using a jf2 Python utility to at is part of a microformats2 helper library I found on GitHub, combined with a bit of my own code.
# capjamesg[d] [KevinMarks] I’m not sure I can think of a tool that meets those requirements.
# jamietanna I'd looked at it briefly for Micropublish but then a few other things came up that I prioritised over it
# 
GWG capjamesg[d]: This? https://github.com/dshanske/parse-this
# capjamesg[d] Thanks for sharing!
_sayanarijit[d], nertzy, jamietanna2 and tetov-irc joined the channel