!! was a sudo argument and never used it out of that context! Thanks for the $(!!) tip π€
Back to the future from start to the end.
mastodon.social, I don't wanna know about it, nor do I agree to it.
I'm literally sitting in a corner *chuckles*. I rarely get any emails nowadays. But if I do and it is not plain-text, then my Mutt gets to bark at it and I, just... won't read it. π€·π½ββοΈ
Ntfy x Crowdsec
2009 facebook/VK look, it kind of feels notsalgic. (the tld is a .me not a .com if anyone else wants to take a look atit)
Ephemera, is because I don't trust SSD/NVMe's ... it's always just a matter of time before everything goes to sh...rimps.
$ mail
[...]
The following warning/error was logged by the smartd daemon:
Device: /dev/nvme0, number of Error Log entries increased from 1587 to 1590
[...]
up -d, but then I took a look at a couple of #Snac instances at the last second and they looked pretty dope! Now I'm stuck in my own head π
> Note: "You should check https://marginalia-search.com/ I bet you'll love it."
1) Short term solution: I've geo-locked my Timeline instance since I'm the only one using it (and I only do so for reading twts when I'm away from terminal).
2) Long term: I took a look at your Caddy WAF but couldn't figure things out on my own; until then, I'll be poking at Caddy-Defender, maybe throw in a Crowdsec for lols... #FUN_
AS136907 HWCLOUDS-AS-AP HUAWEI CLOUDS > Thank you Huawei for the DDos you sons of Glitches!!!
rsync is actually THIS effing faster than scp!!? π«¨
AI sticker on it.. right? xD
refurbished hp proDesk 600 g4 mini
twtxt.net's home page doesn't load more than 13 twts, no more pagination/infinite scrolling...> Page 1/1 of 13 Twts
ProDesk 600 G4 Mini with a Core i5-8500T, 32Go of DDR4 RAM and 256Go SSD storage. A cheaper alternative to an 8GB RPi5 + Argon one v3 m.2 RPi case kit (NVME not included) π€·. It should be here by Friday π€
The keyword here is
microblogging. But it doesn't feel like we've been (relatively speaking) doing much of that lately... maybe I go the concept of microblogging wrong.
Ramadan is next week. So, we switched to UTC from UTC+1 in the weekend. As if it's going to make the days any shorter π
Ramadan is next week. So, we switched to UTC from UTC+1 in the weekend. As if it's going to make the days any shorter π
> Alert | BRAIN CELLS OOM with error message: "Ain't nobody got time for that!"
> Alert | BRAIN CELLS OOM with error message: "Ain't nobody got time for that!"
twt-A when I replay to it with fork-twt-B; I imagine elisp interpreting those as a s-expression thus breaking the generation precess of hash (#twt-A) before prepending it to for-twt-B ... but then I'm too ignorant to figure out how to test my theory (heck I couldn't even recalculate the hashes myself correctly in bash xD). I'll keep trying tho.
twt-A when I replay to it with fork-twt-B; I imagine elisp interpreting those as a s-expression thus breaking the generation precess of hash (#twt-A) before prepending it to for-twt-B ... but then I'm too ignorant to figure out how to test my theory (heck I couldn't even recalculate the hashes myself correctly in bash xD). I'll keep trying tho.
wrong hashes aka Lies π€£ Also, If you chheck your own twt on twtxt.net, it looks like a root twt instead of a replay.
wrong hashes aka Lies π€£ Also, If you chheck your own twt on twtxt.net, it looks like a root twt instead of a replay.
s243lua instead π€·
s243lua instead π€·
As an example, this one is a Fork-Replay from Jenny. My next twt will be a replay to this exact twt but from twtxt-el as a test.
Then I'will file an issue if it doesn't behave the way it's supposed to. Cheers!
As an example, this one is a Fork-Replay from Jenny. My next twt will be a replay to this exact twt but from twtxt-el as a test.
Then I'will file an issue if it doesn't behave the way it's supposed to. Cheers!