There are still lots of items on my TODO list, but if X.Org were to die tomorrow, I wouldn’t be completely screwed. Only, like, 30% screwed.
There are still lots of items on my TODO list, but if X.Org were to die tomorrow, I wouldn’t be completely screwed. Only, like, 30% screwed.
There are still lots of items on my TODO list, but if X.Org were to die tomorrow, I wouldn’t be completely screwed. Only, like, 30% screwed.
There are still lots of items on my TODO list, but if X.Org were to die tomorrow, I wouldn’t be completely screwed. Only, like, 30% screwed.
He is
neofetch main developer/maintainer. Archived all repositories, and updated GitHub's profile README file to read "Have taken up farming." 🥳
ai.txt / robots.txt, but I wouldn’t trust that they don’t spoof their user agent. 🤔
ai.txt / robots.txt, but I wouldn’t trust that they don’t spoof their user agent. 🤔
ai.txt / robots.txt, but I wouldn’t trust that they don’t spoof their user agent. 🤔
ai.txt / robots.txt, but I wouldn’t trust that they don’t spoof their user agent. 🤔
{
"name": "Synapse",
"version": "1.96.1"
}
I am running Conduwuit (https://github.com/girlbossceo/conduwuit). :-)
UserAgent header and respond accordingly.
UserAgent header and respond accordingly.
AI Bots based on a list of User Agents in an interesting way. 👍
AI Bots based on a list of User Agents in an interesting way. 👍
-- Or just write your web application as a normal set of pages in the Hypermedia Driven Application (HDA) style/architecture, than sprinkle a few hx-* attributes and get the same user experience? 😅 #htmx
-- Or just write your web application as a normal set of pages in the Hypermedia Driven Application (HDA) style/architecture, than sprinkle a few hx-* attributes and get the same user experience? 😅 #htmx
https://hypermedia.systems/
https://hypermedia.systems/
Part 2 of this answer explains it fairly well: https://stackoverflow.com/a/477578 Also, this was a nice read: https://web.archive.org/web/20180819014446/http://jaspan.com/improved_persistent_login_cookie_best_practice
It depends on your threat model, but the use of public computers in libraries, internet cafés or similar is probably the most relevant here, when arguing against activating "remember me". These days, shared computer use is declining I'd assume. With twtxt being a niche for more computer-affine folks, I'd reckon this threat is not that high up the list. On the hand, you want to bring yarnd to the average non-nerd user, so this threat might actually rank more important.
It's probably okay and safe enough to remove "remember me" entirely and just issue a long-lived session cookie and be done with that. Optionally, power users or the administrator could benefit from configurable cookie lifetime(s).