jamietanna[m]If you don't mind, go for it. I can look at removing it later on my side, just to avoid it, cause I don't really care about those mentions
[tantek]GWG math, it's shorter, more linear through the year, eliminates weird inconsistent sense of Gregorian months as well as inaccurate conveyance of months towards progress of the year (e.g. June 30th is not halfway through the year)
GWGThese are things like my On This Day Feature, sorting my date archives from oldest to newest, implementing a /updated url to show my site based on last updated order instead of publish date
[KevinMarks]You could probably support the Hebrew and Chinese calendars as the date ranges are different enough, but the Orthodox (Julian) one is harder as it overlaps with Gregorian
@DataNerderyHi friends, be careful pip installing packages - someone's just uploaded three and a half thousand packages to @PyPI that point to a malicious URL. A lot of the names are things like "numpyDjango" or other common typos (twitter.com/_/status/1366263351685226499)
@DynamicWebPaige👋 Greetings, friends! I have a question for you: If you are building a web application using Python, what tools do you reach for first? And if you aren't using Django or Flask, what Python tool *are* you using? (RTs for reach appreciated!) (twitter.com/_/status/1366445885119422465)
[tantek]interesting, I realize I'm using a hybrid approach to avoid that. I POSSE text (including replies) directly to Twitter, rather than use Bridgy. I do still use Bridgy to POSSE photo posts
[snarfed]for bridgy publish users, we could evangelize a best practice of, when you grab the published silo post’s URL from bridgy’s response (eg for u-syndication), you’d also remove the bridgy publish trigger link from the post
aaronpkbut that's a different issue anyway, cause these were just never sent out in the first place cause the first webmention wasn't sent for the post until way late
jamietannaunfortunately in this case, the WMs are queued in Telegraph, so my site doesn't know about them (it does mark them as failed so shouldn't retry them)
jamietannayeah I think you'll remember it used to send a wm to every link on every page every time D: now it only sends to posts that have updated in the last few hours, but only when it's not already gone through
aaronpki might just need to build some better smarts into telegraph for handling this case where the worker has stopped for a while. there's no reason it should be trying to send out the same webmention again within like 5 minutes
@IrisClassonThe front-end team was like: Did you try to: yarny guply webpacky something something -----f --s with cli X using cli Y at version 1.2.3.4.5.66666 (NOT 1.2.3.4.5.66667- are you CRAZY??) Me: No I did not. I did not try that. I wrote: install But it did not install. (twitter.com/_/status/1366384929815339009)