@rdlmda@rdlmda.me Holy fuck, you were really lucky! This could have gone really bad. You noticed it because of the blackout?
@lyse@lyse.isobeef.org Thanks for letting me know. HTML checkers seem happy now. I’m not sure what to do about the images not loading. The photos have three sizes (thumbnail, photo page, and original if you click the img tag on the photo page); can you at least see the smaller two sizes? Maybe I will do some experimental fetches and/or start measuring things on my web server.
@movq@www.uninformativ.de @lyse@lyse.isobeef.org It’s not that bad. She let me sleep three times last night alone!
@lyse@lyse.isobeef.org still not as bad as the time a fire started in the breaker panel for my building and I had to personally put it out myself with a fire extinguisher.
@rdlmda@rdlmda.me @prologic@twtxt.net The web is fucked. :-(
@rdlmda@rdlmda.me What a truly wonderful description. ;‘-D But sorry to hear that. Luckily, no issues over here. It’s extremely rare that this happens. Last time (around five years ago or so) they were cutting down trees in the forest and threw a tree in the overhead power line (which had been converted to underground last year). Power had to be killed in order for the fire brigade to actually extinguish the fire.
@bender@twtxt.net H-Blockx covered it, the original was by Snap! https://en.wikipedia.org/wiki/The_Power_(Snap!_song) But it’s actually not my type of music at all. The high pitch refrain “I’ve got the power” is iconic and has somehow burned itself into my brain. Must have been a short circuit.
@rdlmda@rdlmda.me Yeah the “web” is pretty broken™ right? 😅
@lyse@lyse.isobeef.org 😂 Pretty cool remix(?)!
My twtxt instance is under a de-facto attack. Or, at this point, I can’t even differentiate an attack from the other in the constant barrage or malicious requests.
There were so many bots hammering it, in only 3 days, they consumed the ironically significant amount of 666 MB — I kid you not! In the last 24 hours, there were 59,673 hits on this endpoint alone.
I had to put my twtxt web interface behind a password-protected BasicAuth directive. As I’m the only one using it, it’s fine.
Bots, scrappers and Large Laggy Manglers are poisoning the open web.
@quark@ferengi.one Ignored. ✅
@rdlmda@rdlmda.me @bender@twtxt.net Eventually: “I’VE GOT THE POWER!” https://www.youtube.com/watch?v=rOScKjXH-HE
@lyse@lyse.isobeef.org Yes 🙌
@movq@www.uninformativ.de This is how my SSH proxy setup works.
@lyse@lyse.isobeef.org Hm, I’m not sure I would want to do that:
ForwardAgent
...
Agent forwarding should be enabled with caution. Users
with the ability to bypass file permissions on the remote
host (for the agent's Unix-domain socket) can access the
local agent through the forwarded connection. An attacker
cannot obtain key material from the agent, however they
can perform operations on the keys that enable them to au‐
thenticate using the identities loaded into the agent.
@kiwu@twtxt.net after you upload, make sure the audio file looks like this:

And it will work.
Testing…
Testing jenny. You should probably ignore this, and the next twtxt.
@rdlmda@rdlmda.me that’s odd. In here is similar, but not random. All it takes is some rain, and then flip a coin: we may, or may not lose power.
@lyse@lyse.isobeef.org no dice. Same.
Authenticated to git.mills.io ([199.247.16.95]:2222) using "publickey". ssh-add ... had no effect (even after ssh-add -D).
@movq@www.uninformativ.de I don’t think it is anything you are doing wrong. I think it is on @prologic@twtxt.net side. I am getting the exact same result, but I never cloned that repository. Maybe it worked fine at certain point, when @lyse@lyse.isobeef.org cloned it, but I doubt brand new users can get through.
@lyse@lyse.isobeef.org Changing the user name helped, it now says Authenticated to git.mills.io ([199.247.16.95]:2222) using "publickey". ssh-add ... had no effect (even after ssh-add -D).
Here’s a debug log, @prologic@twtxt.net, perhaps you could take a look at this 🙏: https://movq.de/v/116c5f514b/clone2.txt
(Might be a silly mistake on my part. Wrong remote path or something?)
@rdlmda@rdlmda.me LOL. Do it, do it!
@lyse@lyse.isobeef.org “deep layers of the Mills infrastructure” LOL.
@rdlmda@rdlmda.me it is called, in Spanish, “the mother”. It is created through a bit (not by much) effort, and kept as a starting point. Just like Asian cuisine has dishes that never cool, always cooking leaving always a base on it.
How do you think a lathe (and just about any tool, etc.) is done? Yup, in part by using a lathe. 😅
“Yes… Look at everyone @prologic@twtxt.net is following! Next, look at everyone each one of them is following… Next… Hmm… Build a graph of follows and mentions, it’ll be so FUN and not at all time-consuming”
– My evil ADHD brain
@bender@twtxt.net Somehow, the enshittificator himself does not have to deal with enshittification in his own life. In fact, his job gets better with the internet! This can only mean one thing, we all have to becom…
@falsifian@www.falsifian.org Congrats, mate, no sleep at night anymore! ;-D That’s a cool age measuring blanket. Haven’t seen something like that before.
Btw. the index.html includes an out of place </ul>. And I just wanna let you know that the full-size photos don’t load for me over here across the pond. They always run into a timeout after a few slooow percent. But no worries. :-)
@movq@www.uninformativ.de @bender@twtxt.net You need a running SSH agent in order to make it through the deep layers of the Mills infrastructure: After ssh-add, git pull always works for me.
And contrary to what the UI shows, the username git always has to be replaced with your own one.
@prologic@twtxt.net network is very secure! 🤪
@movq@www.uninformativ.de just use https instead:
git clone https://git.mills.io/yarnsocial/twtxt.dev.git
Anyone else having trouble pulling from git.mills.io? 🤔
$ g clone ssh://git@git.mills.io:2222/yarnsocial/twtxt.dev.git
Cloning into 'twtxt.dev'...
git@git.mills.io: Permission denied (publickey).
fatal: Could not read from remote repository.
The key verification function on https://git.mills.io/user/settings/keys says I’m using the correct key.
This also looks good:
$ GIT_SSH_COMMAND="ssh -v" g clone ssh://git@git.mills.io:2222/yarnsocial/twtxt.dev.git
...
debug1: Authentications that can continue: publickey
debug1: Offering public key: /home/user/.ssh/keys/key-millsio ED25519 SHA256:nVNT... explicit
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
git@git.mills.io: Permission denied (publickey).
fatal: Could not read from remote repository.
Does it work for you, @lyse@lyse.isobeef.org @prologic@twtxt.net?
@falsifian@www.falsifian.org My condolences. I mean, errr, congratulations! 😅
@falsifian@www.falsifian.org congratulations mate! Let it be joy, and happiness! Enjoy every moment. Time will fly, and next you know you will be a curmudgeon who knows nothing. 😅
@falsifian@www.falsifian.org Congrats! 🥳
today’s mood
@bender@twtxt.net Lets bend it!
@rdlmda@rdlmda.me welcome!
@bender@twtxt.net Oops, missed this. I haven’t done any client work since my brief experiment modifying jenny a while back.
Hello twtxt! I still exist. I have a baby now and put some pictures at https://photos.falsifian.org/ . Album HTML loosely inspried by @lyse@lyse.isobeef.org
@bender@twtxt.net It is not yet lost, other than the ongoing communication with local politicians, the European Commission, (thanks to other developers) the U.S. Department of Justice, over 50 other organizations (see some of them, signed on the open letter, top of the before mentioned website), we’re also actively looking into possible workarounds and exploring other available legal options, while companies like Motorola, are already planning to offer GrapheneOS, on some phones.
@kiwu@twtxt.net those moods don’t play, they download. 😩
@thecanine@twtxt.net sorry to hear that, mate. Don’t worry, something better will come up. After all, it has got to be easy to beat Android, right? :-)
@movq@www.uninformativ.de and @lyse@lyse.isobeef.org rock, and thank you for taking the initiative to get this done. @prologic@twtxt.net, what say you?
Let’s finalize https://git.mills.io/yarnsocial/twtxt.dev/pulls/28/.
@bender@twtxt.net Yes, really should have chosen my words more wisely. As @movq@www.uninformativ.de mentions, we got a vague promise of an “advanced flow” being implemented, and in my case also a vague promise of a video call, with someone at Google, regarding it. Now when the backlash died down, it does not look like Google plans to follow through, with any of this and they’re completely unwilling to elaborate and get back to us, about if and how any of this will be implemented.
@lyse@lyse.isobeef.org We’ll see. Hasn’t really happened in the past. 🤔
@thecanine@twtxt.net are you referring to the “WE FUCKING WON!” twtxt?
@movq@www.uninformativ.de Now, they’re always cloning the entire repo I suppose. X-(
@arne@uplegger.eu (Arrrrrgh, bitte lass’ mich nicht noch ein Spielzeug kaufen … 😂)