#aaronpkor more generally, SPAs that aren't actually applications, they are documents
#btremWhat is an SPA? (No, Loqi, I'm not asking you!)
#LoqiA single-page application (SPA) is a web application or web site that fits on a single web page with the goal of providing a user experience similar to that of a desktop application https://indieweb.org/SPA
#[fluffy]Hmm, so, in my h-card I purposefully overly URL-encode my email address to e.g. “mailto:fluffy%20beesbuzz%2ebiz” because it’s an easy way to defeat noncompliant things like spam harvesters from getting my address, but allows worthwhile user-agents like web browsers to work right. But I’m noticing that having that causes my webmentions to fail validation on some endpoints, such as Barry Frost’s site. Does anyone have any opinions on be
#[fluffy]There were two errors adjacent to each other, one from bridgy fed (that always occurs on my reply posts for some reason) and then Barry’s endpoint, and my error log doesn’t always make it that easy to read. 🙂
#jackyvery random but [manton] is there a way to remotely sign up for micro.blog?
#jackyI'm thinking of 'advanced' cases of a social reader
#jackyand one that kinda comes to mind is the ability to do something like a 'introspective' view
#jackylike if you provide it a URL, it'd render said post under the reader and attempt to do some more stuff like subscribe briefly to the websub hub shown to potentially give information about incoming posts
#jackyor provide a simpler interface to engage with it (similar to how mastodon kinda does it)
#jackyI don't want to bake some of this stuff into my site - I'd rather have it on a standalone tool so I can then 'link' to it and have people use it on their sites as well
#jackyI think the biggest thing is that 'engagement' (via responses, not like metrics) would only be surfaceable if they provide it on a page (like there's no means of querying replies for a particular URL)
#jacky(that's kinda where having a Webmention endpoint be queryable would come into play imo)
#jackyI'm thinking about this stuff b/c I want it mainly on my site but also to make it clear that individual sites _can_ do this and in a simpler way
ShadowKyogre and [snarfed] joined the channel; ShadowKyogre left the channel
#[snarfed]hey aaronpk, low priority, when you get a chance, could you check if wm.io’s client HTTP lib supports SNI now? it didn’t back in 2014, which was (one of) the reasons bridgy uses brid-gy.appspot source URLs. https://github.com/aaronpk/webmention.io/issues/14
#Loqi[snarfed] #14 not seeing some brid.gy source URLs
KartikPrabhu, schmudde, marinin[t], [xavierroy] and [barryf] joined the channel
#[barryf][fluffy] Sorry for the failed webmention. Your h-card is perfectly valid of course. The exception comes from the indieweb-authorship Ruby gem which my server uses. I’ll fork and see if I can add some exception handling.
#[barryf]I’m not sure if the author, deeden, drops in here?
#[barryf]Hi Stephen. My server didn’t parse Fluffy’s webmention because of `URI::InvalidComponentError: unrecognised opaque part for mailtoURL: fluffy%40beesbuzz%2ebiz` in Indieweb::Authorship.identify. I’ll see if I can recreate locally.
#[barryf]If I can fix I’ll send you a patch a bit later on.
lanodan joined the channel
#[srushe]I’ve got it recreated locally. I’m not sure what to do here. The microformats gem is raising the error. I can rescue it fairly easily but all I could really do them is return an empty response. If you find a better solution I’ll be happy to hear it 😄
shoesNsocks, shoesNsocks1, joaweyang, [KevinMarks], [schmarty], [tantek], [timothy_chambe], [snarfed] and [fluffy] joined the channel; ShadowKyogre left the channel
#[fluffy][barryf] oh hi, didn’t realize you were on this Slack 🙂
#[fluffy]well, chat in general (but you happen to be on it via Slack)
#[fluffy][srushe] Sounds like it’s turtles all the way down. Is there a particular exception that could be caught? Or maybe the mf2 parser author(s) need to be brought in too 🙂
#[fluffy]like ideally the card validation wouldn’t fail because of a single “malformed” optional attribute, but also the attribute isn’t malformed.
#[fluffy](and many people do purposefully malform that particular attribute!)
[srushe] joined the channel
#[srushe][fluffy] I can work around the issue if I explicitly decode the html before I send it to the Microformats parser, but that “feels” wrong to me. I think it should probably be up to the Microformats gem to handle the encoded html, but that may just me passing the buck. I’ll look to put up a version that works around the issue for now
#[fluffy]Whatever is parsing the HTML should also be decoding the URLs. And that does sound like it’s the Microformats parser’s responsibility.
#[fluffy]although that also heads into a gray area, like when handling HTTP URLs, should you round-trip it through a urldecode/urlencode phase or whatever? That leads to fun corner cases.
#[fluffy]like then you can’t support path-based things with /s in a path component, like `http://foo.example/blog/category/books%2fmovies/`, and I’ve seen much disagreement among web frameworks as to whether that should be supported in the first place (for example, wsgi explicitly disallows it).
#[fluffy](or rather the wsgi spec says you must url-decode the incoming URL components before passing them along to the application)
#[srushe]Exactly. My first stab at this this morning is a simple fix, but I’m certain that there will be weird cases where it’s a bad idea. I may pull the gem source down tonight and see if I can solve the problem there.
#[fluffy]%-encoding is one of those things where things were casual enough in the beginning that formalizing things now is difficult to do right. 😕
#@jasnellAll of the necessary pieces are still available. It's still possible to build these types of systems without much difficulty. It's not a technical problem, it's a logistical one. The difficulty lies in attracting the users and guarding/policing the spaces so that they remain safe (twitter.com/_/status/1356460552768212992)
#@jasnell... you see, developing the technologies is the easy part. Bootstrapping the community that uses them is hard. And FB and Twitter were investing heavily in owning the space with their own walled gardens. FB especially. We knew the standards didn't mean squat if they wouldnt adopt (twitter.com/_/status/1356460551061131264)
#[tantek]I disagree with "developing the technologies is the easy part". It's only easy if you're ok with complex solutions. Simple(r) technologies are ironically harder to develop.
#jackythat depends when you come in the process, no?
#[tantek]I disagree with "Bootstrapping", it's a regressive libertarian metaphor
[benatwork] joined the channel
#[tantek]I agree that growing a community is hard, which is one of the reasons aaronpk and I made a deliberate decision to start/grow *this* community, instead of the 2010 FSWS
#[benatwork]Or just “starting / growing” in the non business sphere
#[schmarty]i argue with the framing of "developing the technologies" as if there is one correct set of technologies and the problem is that the world won't pick them up and use them.
#[tantek]and I disagree strongly with "We knew the standards didn't mean squat if they wouldnt adopt", actually quite the opposite. So much early time on "open social web" standards was *wasted* trying to cater to BigCos who blew it all off anyway
#[benatwork]tantek++ basically, we need to work *despite* them.
#Loqitantek has 17 karma in this channel over the last year (83 in all channels)
#[schmarty]there's a case to be made that "developing _a_ technology" is easy because, sure, you pick some constraints and you solve for X.
#[tantek]I also disagree with "All of the necessary pieces are still available", because no, you don't and can't know that until you have actually built the system that solves user's problems
#[tantek]also disagree with "It's still possible to build these types of systems without much difficulty." — are you freaking kidding me? "without much difficulty" lololol
#[schmarty]my takeaway from this thread is "no one should build technology because we once tried to solve the wrong problems and it didn't fix anything."
#[tantek]this is also wrong: "It's not a technical problem, it's a logistical one." (yeah blame ops, nice try)
#[tantek]if a technology doesn't operationalize well, it's the fault of the technology design
#[schmarty]i read "logistical" in that usage as being about getting people to adopt the new tech.
#[tantek]wowow as if people are "logistics" yikes that's even worse of a capitalist framing 😞
#[schmarty]yeah the next sentence clarifies "logistical problem" as: "The difficulty lies in attracting the users and guarding/policing the spaces so that they remain safe"
#[tantek]this is what I'm saying, that's a horrible default authoritarian framing
KartikPrabhu joined the channel
#[schmarty]to borrow a phrase i read in here recently: it's like abducting the entire city into your party and getting rid of anyone who harshes the vibe.
#[schmarty]i think this exact thing is playing out with ActivityPub. it's _a_ technology that enables (and encourages) certain kinds of experiences and excludes (or makes difficult) others. even so, there is some _frothy_ evangelism around it as being The Way that social networks should work from now on.
#[KevinMarks]I can see how jasnell end up there as he has been adding corner cases to AS for years, but AP then built half thought out apis on top of it and claimed that they were done.
#[tantek]KevinMarks, adding corner cases by way of public iteration with a community of implementers is one thing, but that absolutely did not happen with AS
#[tantek]to be fair to AP, it was an iteration of what was implemented in pump.io so at least it had *some* grounding in real world public implementation
#[tantek]whereas AS never got off the ground in terms of an ecosystem of publishers & consumers
#[KevinMarks]Well, it did originally but then the community dissipated
#[KevinMarks]And Monica was a key part of implementing it in many places.
#[tantek]KevinMarks, never saw any functional consumers
#[snarfed]aaronpk one thought is to priority order the inboxes you’re delivering to. won’t improve total time, but if it hits the key ones in the first 30s or so, you might not care
#aaronpktrue, also i need to prioritize other tasks my site does over these for sure, like if i send a reply while it's in the middle of pushing them out, i want the new reply webmention to go out first