#[tantek]lol the reply guys pointing out .dev is on the HSTS preload list. I literally ran into that ages ago when that switch was flipped (was using .dev for local development)
#Loqi[snarfed] #253 support HTML meta http-equiv=refresh redirects
bterry, Seirdy, h4kor[m], lqdev[m], jacky_ and mro joined the channel
#@ummjackson↩️ Makes sense, but how do you ensure all federated data repos sync with one another if there isn't something akin to a Webmention taking place? Also, I'm guessing it'll be kinda impossible in this federated world to avoid faked like/retweet count counts? (twitter.com/_/status/1582615000958369792)
#@ummjackson↩️ > Then your PDS will notify the PDS of the recipient(s) of the content to sync up
Makes sense, is the protocol for that in the docs somewhere? Feels like a Webmention. (twitter.com/_/status/1582615267464486914)
#capjamesg[tantek] The @ syntax felt most intuitive for me.
#capjamesg"i find that it usually involves writing @domain.com in source code and then replacing the @ and the domain name with the nick or known name of the identity causing it to lose some of the implicit UX of the raw domain name." - +1 on this
#capjamesgBut I didn't cover the point about why I chose the syntax.
#Loqi[James] IndieWeb New Years' Eve Commitment: Expanding my person tags
#[Jamie_Tanna]Tantek I want to say I followed seb's example, but can't remember if I went a step further to make it an FQDN. Since a few folks recently have changed URLs, however, I have been considering using a better nickname (ie `@jamie`) when I migrate to my new site
#@brob↩️ I can't wait to see your implementation on this. I ended up removing webmentions from mine due to some spam issues and the management of the spam, but I feel like it was more of an implementation issue there! (twitter.com/_/status/1582729347689222149)
#barnabybut presumably it’s a result of bad experiences with people coming from those sites
#[Murray]I think it's partially that, partially just a fun demo for Edge functions (which likely get a lot of traffic from this types of aggregator sites)
jacky joined the channel
#sknebelbarnaby: jwz redirects HN referrers to a not really NSFW image... compared to that a small header is quite fine :P
#barnabyI mostly find it hard to believe that reddit is much worse than twitter in terms of harrassment and abuse
#barnabybut I suppose it varies depending on the individual
#jackyesp on direction, popular content promotion, etc
#barnabythe only tech-related subreddit I spend any time on is r/rust, which seems pretty reasonable. I have no idea where reddit abuse directed at web design blogs would even come from
#sknebelyeah, really depends. (and I'd agree in the specific example, r/rust is doing a reasonable job at not amplifiying the bad parts)
geoffo, jacky, miklb, EncryptedGiraffe and barnaby joined the channel
#@person72443↩️ Oh and webmentions. Webmentions are the COOLEST thing, imo. It's basically globally-compatible @ notifications, replies, bookmarks, etc. I have it set up for replies on my blog. (twitter.com/_/status/1582775498584645636)
#[tantek]jacky, if by "site management" you mean coding on my own "CMS" (yes, deliberate scare quotes), I keep a private text file for specific bugs to fix (seems like prudent security), and the rest sometimes go into a private text file, though eventually I try to dump them into https://indieweb.org/Falcon#Working_On, inserting them into a rough priority order, or if it's a far-off thing I can't even try to prioritize, I may put it on the
#[tantek]My hope is that those async additions to the wiki may serendipitously show up in someone else's search of the wiki when they're looking to work on something similar, and then that can be a source of conversation in chat to perhaps try to collaboratively solve a problem space (rather than attempting to solve problems purely on my own)
#[tantek]I think that's in general a good feature of such public "to do" lists
jacky, mro and jacky_ joined the channel
#barnabyhaving a sqlite explorer built into my editor is so convenient. being able to treat an sqlite db as a big file which I can easily poke around in gets close to the convenience of flat files, with the added convenience of SQL functionality
#barnabyooh no I’m not Zegnat, didn’t know that was possible. very cool
#barnabynot sure I’ll use it for taproot as part of using sqlite for storage is getting my data and code separate, so the plan is for the db not to be in git
#ZegnatIt is not generally a good idea to store sqlite files in git because it makes your repo size grow (stores full binary blobs for each commit), but if you just have a small or empty db for setup purposes in a repo the quick diffing thing is nice to visualise schema changes and what not
#barnabytaking the simple approach of storing rejected responses allows me to have basic moderation immediately but lets me procrastinate on developing a more comprehensive moderation rule system
#[tantek]and what user functionality does rel=manifest add to your website?
putierre joined the channel
#[tantek]aciccarello++ indeed. We should write-up similar recommendations for Twitter meta tags that can be dropped
#Loqiaciccarello has 1 karma in this channel over the last year (8 in all channels)
#ZegnatFrom what I can see, capjamesg, the rel-manifest spec only mentions <link> elements and nothing about HTTP headers. So consumers might not parse headers for it. Could be worth testing.
#[aciccarello]Twitter cards also fall back to og: tags so you shouldn't need to duplicate them.
#[aciccarello]They do support OGP, but they have their own tags if you want to override the property just for twitter
#ZegnatThere you go, tested by someone who takes minimal HTML very-very serious, get link previews cross-silo in 4 elements thanks to fallbacks all around
#jackyoh yeah sure - I'm saying more that I wish the extra functionality was done as part as an OGP extension :)
#Zegnatjacky: have you ever seen any ogp extensions? They even added namespace support, but I think I have never seen anyone do ogp stuff outside of the handful of link preview elements
#jackyI haven't (hence my hope - it's overly optimistic)
#sknebelI technically have encountered ogp for business information (like opening times) in the wild. I have not encountered such information that actually was correct though
#jackythis reminds me of doctorow's "metacrap" concept lol
#[aciccarello]TIL: "Note that Open Graph recommends specifying the “og” RDFa Core 1.1 CURIE prefix mapping via <html prefix="og: http://ogp.me/ns#">"
#ZegnatAtleast you hope it makes no difference, you never know, in a world where it matters whether you put quotes around your HTML attribute values or not ;)
#[KevinMarks]the card validator used to be good at cache busting the main cache, guess they broke that
#[snarfed](unrelated, Bridgy has blithely disobeyed the webmention spec and cached endpoints per domain for pretty much its entire life. not recommended for the usual indieweb site sender, but 😎 )
#ZegnatI have had mixed results with the FB validator too, especially with images ...
#barnaby[snarfed]: huh I’m pretty sure my webmention endpoint URLs have an expiring token in which prevent them from being reused after five minutes or so
#barnabyso either my tokens don’t work (entirely possible) or bridgy re-fetches them occasionally, or on errors or something
#[snarfed]I looked through your last 3 mos or so of Bridgy wms, they've been too sparse for this to become a problem. averaged maybe 1 a week or so, and no bursts of more than one in 2h (Bridgy's cache expiration)
#barnabyah okay, yeah if the cache expires every 2h then that’s unlikely to be a problem
#barnabyand I already have to write a bunch of exceptions for bridgy, I’m happy to add another ;)