LoqiIt looks like we don't have a page for "decentralized social media app" yet. Would you like to create it? (Or just say "decentralized social media app is ____", a sentence describing the term)
gxt, [jgmac1106] and [schmarty] joined the channel
[KevinMarks]Interesting - that makes sense, though not sure if the current version would do that. It would work for a figcaption. Another tricky case is in a <details > - should it expand it?
[tantek]should the img alt text be considered in-stream (the way a screen reader would read it?) that seems to make the most universal-access sense to me
[KevinMarks]Not sure if screen reader and text copy are the same. The text copy is appealing because it has whitespace handling defined, and because that is the easy way to do a link by hand - copy text and paste after a # in the url
[tantek]a screenreader user wanting to reference something they happened have heard in an alt text would absolutely copy paste it with a # after the URL
LoqiIt looks like we don't have a page for "Project Xanadu" yet. Would you like to create it? (Or just say "Project Xanadu is ____", a sentence describing the term)
[tantek]petermolnar, IDK, Xanadu was more of a brainstorm (never practical) than anything actually relevant. Certainly not indieweb relevant, nothing beyond its Wikipedia article.
[snarfed]hey jamietanna, any thoughts on the meetup API requiring a Pro subscription? (~$35/mo.) not sure where that leaves us re adding it to bridgy. you don't currently subscribe yourself, right?
jamietanna[m]Snarfed no I don't subscribe but I have got an oauth client registered for brid.gy already so we may be safe (although it leaves me as the owner)
jamietanna[m]Nope, I've not received anything so far about it. I didn't even know about it being a thing until you said, and it's not clearly called out on their docs so 🤷🏽♂️ they obviously don't seem to want to publicise it
[snarfed]could you please also ask their support what they plan to do with existing API keys without subscriptions? we'll want to know if they plan to turn them off anytime soon
gRegorLove, leg, [CrowderSoup], [schmarty] and swentel joined the channel
[snarfed]oh also jamietanna i guess we should remove meetup from https://oauth-dropins.appspot.com/ since we don't have an API key for it? (it would stay in the library, just not on that demo app.)
jamietanna[m]Snarfed I'm having some difficulty working out the best way of hooking in the scopes to the start of the request, which file would you recommend looking at for how best to do it?
superkuhindieweb should drop, or modify, webmention so that full manual and distributed receiving of webmentions is possible. All it would take is putting the data in the URL string instead of using form encoded POST.
aaronpkwith webmention, the only data sent is the source and target URL. turning that into a comment that's displayed will always require additional work by some software somewhere.
aaronpkif you move the data from the post body to the query string, you just move the attack surface to the processing script instead of the server side environment
aaronpkif you really think it would solve it, i encourage you to build a webmention receiver for your static site that processes the webmention via query string parameters
superkuhI've looked into ways of getting form encoded data to log to disk with nginx. Mostly it requires about 30 lines of lua scripting in the location directive for the webmention endpoint.
aaronpkif you're concerned about running some piece of software that handles a form post, and want to also run that software yourself, then you can write a web server that only parses the exact format that webmention requires and can't do anything else, eliminating any concerns of other "attacks" you're describing
aaronpkagain that's the beauty of webmention, it leaves that possibility open for you while also making it easy for others who don't have those same concerns
aaronpkyou're missing the point here though. moving the data from the post body to the url doesn't actually change anything, because once you want to process that webmention you're going to parse the access logs and now you're parsinjg the query string from the log file insteadf of the http request and your'e open to all the same attacks again
aaronpki'm not sure how familiar with HTTP verbs you are, but there are other implications of sending data via GET vs POST that make GET not a good fit for webmention
jamietanna[m]!tell snarfed looks like I need https://github.com/snarfed/granary/pull/180 (just raised it) before the Brid.gy stuff can continue as that method's used by Brid.gy's code - just doing some validation to confirm it's working ok
Loqi[snarfed]: jamietanna[m] left you a message 59 minutes ago: looks like I need https://github.com/snarfed/granary/pull/180 (just raised it) before the Brid.gy stuff can continue as that method's used by Brid.gy's code - just doing some validation to confirm it's working ok
jamietanna[m]That's allowed me to authorize bridgy locally, so now all I need to test is publishing. How did you recommend in the past? Publish an RSVP with the prod bridgy meetup url, then try publish locally via the preview?
[snarfed]also, if you run a normal python shell while in your virtualenv and while dev_appserver is running, and then do eg `Meetup.get_by_id(...)`, it'll use your local datastore