Searching yarn

Twts matching #http
Sort by: Newest, Oldest, Most Relevant

@arne@uplegger.eu I’ve tried Matrix before, it was all good and dandy until servers started getting spammed with stuff no sane human being should see (if you know what I men). So, I took down my server and never looked back.

⤋ Read More

@prologic@twtxt.net My bad. It has been a while since the last time I poked around my mystery box, and I must have Effed up something yesterday. Is it fixed now? (Also, I’ve noticed that access to my avatar is, somehow, still denied. Still poking at it. 🤦)

⤋ Read More

@bender@twtxt.net Please create an issue for this too! Probably against twtd right? We should validate new fetchers and see if they are real clients or not. I think yarnd already does ybis quite well? 🧐

⤋ Read More

@lyse@lyse.isobeef.org simplified it a little bit. Using only *bot* will bring collateral damage I want to avoid (there are, still some “good” bots):

@aibots {
      header_regexp User-Agent (?i)(GPTBot|ChatGPT|OAI-Search|anthropic|Claude|Google-Extended|FacebookBot|CCBot|Perplexity|Applebot-Extended|cohere|Omgili|Bytespider)
}
abort @aibots

⤋ Read More

@prologic@twtxt.net I linked you some of my findings on the twtxt.app on IRC. The main problem is the hashing. Totally broken. But you have got to give it some thought, because GitHub hosting of the feed is tricky (even more so if they are CNAMEing their domain to it). It is also finicky because Pages is auto-enabled on username.github.io, so actions must run each time you twt.

⤋ Read More

@david@daiwei.me Some entries can be probably simplified with just *bot*. :-) (But I don’t use Caddy, so no idea about case (in)sensitivity.

That reminds me, I should do something similar with my Nginx.

⤋ Read More