Search Options
Search Type:
SearchField: by default all fields are searched
Sort by: Newest, Oldest, Most Relevant
@prologic (#pu5mbba) Hahaahaaa, brilliant, you're right, it's the A-Team lawnmower. :-D I took the photo yesterday in front of a new background – here in much higher resolution. Unfortunately, I don't have enough dark gray bricks to better imitate the original coloring. There are also plenty of pictures from a couple of years ago: I definitely should weed out all the duplicates someday…

matched #fuveoka score:5.75 Search by:
Search by 1 mentions:
Search by 1 tags:
@prologic (#4uhyaha) Just request the last seen twt as well in the `Range` header and if it doesn't match the old one you've already seen, you know that this feed doesn't operate in append only mode, so that you can request the whole feed. It's worth mentioning that this also happens if the key value comments at the beginning of the file have changed, too, e.g. when the maintained subscription list has been modified. Yes, not ideal. Healthy 2021 everybody!

matched #jlm6ywq score:5.75 Search by:
Search by 1 mentions:
Search by 1 tags:
@gareppa @gareppa (#7mcr2ea) Hey, same to you! Which of your feeds is the real deal? The one on twtxt.net or tilde.club? It also seems that your User-Agent HTTP header from tidle.club is broken, there's a superfluous "public_html/" in the path. ;-)

matched #dfe6igq score:5.75 Search by:
Search by 2 mentions:
Search by 1 tags:
@vain @deadguy @prologic (#qwpzeka) I'm currently in the process to come up with something automated, too. At the moment I manually check my Nginx access log with `cut -d ' ' -f 12- ~/www/logs/twtxt.log|sort|uniq -c` It works for now, but it's certainly not good enough. I definitely want to filter out search engine and other unusable UAs, fold software versions (twtxt.net with its git hashes comes to mind ;-)) and also check the result against my subscribed feeds, to quickly discover new subscribers.

matched #lyrb36a score:5.75 Search by:
Search by 3 mentions:
Search by 1 tags:
I just noticed a bug in my twtxt client's twt publish form – luckily just before submitting. Why on earth make it most programming languages so easy to misuse their damn date time APIs!? On today's episode we have Python's `datetime.datetime.utcnow().replace(second=0, microsecond=0).astimezone().isoformat()` which is not what we want, it's actually `datetime.datetime.now(datetime.timezone.utc).replace(second=0, microsecond=0).astimezone().isoformat()` instead. The former gives us the time in UTC and thus is off by an hour in my case: `2021-01-03T23:30:00+01:00` vs. what I'm really after: `2021-01-04T00:30:00+01:00`

matched #uj2oxcq score:5.75 Search by:
@prologic (#qwpzeka) Exactly, that's what I probably end up doing. But first I have to write up the spec on this extension, I reckon. :-D Yesterday I came across that issue and pull request, both you and @vain had discussed back then.

matched #woa6l2q score:5.75 Search by:
Search by 2 mentions:
Search by 1 tags:
This is twtxt search engine and crawler. Please contact Support if you have any questions, concerns or feedback!