@prologic@twtxt.net just create an account on mastodon.social, wouldn’t that work?

Someone, on the Bridge, this is meant to have sent @manton@bridge.twtxt.net a “Follow Request” via Activity Pub hmmm 🧐

Test (_did I fix this shit™-)?

Hey @manton@bridge.twtxt.net 👋 Why yes I believe I did!

@bender@twtxt.net I need another side that I can unblame 🤣

@prologic@twtxt.net we are not going to get far by blaming the other side. 😅😂

I think because it still inserted the wrong alias in my following list:

# follow = manton@bridge.twtxt.net https://bridge.twtxt.net/twtxt/remote/d428c49928a4a0d1.txt

Testing 1 2 3 @manton@twtxt.net

Test @-mentioning@twtxt.net an AP actor via the Bridge. Hey @manton@twtxt.net 👋

WOW LOL

fetch https://weaknotes.com/users/david: status 500 Internal Server Error

First real test failed trying to lookup / follow @david@weaknotes.com

For those curious, the new Twtxt <-> ActivityPub bridge I’m building (bidirectional) simply requires three things:

1. You register your Twtxt feed to the bridge: https://bridge.twtxt.net
   
2. You verify that you in fact own/control the feed by putting the verification code somewhere on/in your feed (doesn’t matter where or how)
   
3. You proxy/forward requests for /.well-known/webfinger to the Bridge bridge.twtxt.net.
   

I’m still testing through and ironing out bugs 🐛 Please be patient! 🙏

@lyse@lyse.isobeef.org LOL, that one was too good to pass, right? I am glad you are enjoying my little notes in a bottle!

Man, @quark@ferengi.one has an absolute gold mine. Having dealt again with different clocks and all sorts of strange time things at work today, this made my day! https://netbros.com/1755172401/ :‘-D

@bender@twtxt.net Hahahahahaahaaa, you’re right, it can’t be anything else! :‘-D Must have been one of these manmade objects. Let’s hope they will become a full member of the Grant Wishes Council soon. In any case, I will keep trying.

@prologic@twtxt.net oh dear god. Keep us posted! 😅

@bender@twtxt.net Twtxt <-> ActivityPub (2nd time’s the charm? 🤣)

@prologic@twtxt.net how could we ignore it?! Twtxt bridge? Of what kind? Say more! :-P

Beam Dump
⌘ Read more

@lyse@lyse.isobeef.org then it was, most likely, space debris—which, sadly, make up for 98% of all space anomalies these days. And thought they have applied to the Grant Wishes Council, they are yet to be approved. Keep playing, though. 😅

@bender@twtxt.net I wished my mate would see it, too. But he turned his head a second too late. :-(

@lyse@lyse.isobeef.org I hope you were prepared to cram those wishes in 3 seconds. I am always prepared for that eventuality. You don’t have to mutter a word, nor clearly think much about it—that is, you don’t need to think your wish(es) word-by-word. As long as you stay within the wish(es) main goal(s), you should be fine, and it/they shall be granted, of course.

@kiwu@twtxt.net is it almost over, or just got closer to the next one? 🧩

The sky picked up a few colors for just a few minutes: https://lyse.isobeef.org/abendhimmel-2025-11-13/

@bender@twtxt.net I’m doing alright! happy for the week to be almost over ^.^

@kiwu@twtxt.net doing awesome, how about ya? We are having some coolish days, which are super rare, so I am enjoying them plenty!

@movq@www.uninformativ.de Yup, it’s been some days here, too.

@movq@www.uninformativ.de Haha, you were spot on! It took me a bit to figure this out on my own. I’m actually very surprised to have gotten this wrong. Oh well.

@lyse@lyse.isobeef.org Yeah, I noticed that too. I haven’t double-checked my code, though. Maybe it has something to do with selecting the correct URL? I mean, these feeds don’t have any # url = fields, so maybe that’s it?

@lyse@lyse.isobeef.org Ah, there it is. 😃 Never gets old. 👍

@arne@uplegger.eu … I still haven’t watched that show. 🤦

@prologic@twtxt.net And none of them use Yarn-style threading. I don’t think they’re aware of us, they’re probably using plain twtxt. Other than one hit by @threatcat@tilde.club a few days ago, I’ve seen no traffic from them. 🤔

@bender@twtxt.net Hmm, didn’t find anything. But you mean a giant bucketload of access_log /home/$USER/logs/access.log if=… where the condition matches the requested path for said user? Yeah, that gets annoying very quickly. :-D

@movq@www.uninformativ.de Uuuhhh, beautiful! <3

Speaking of sunsets … https://movq.de/v/753ab5f9e5/sunset.jpg

@threatcat@tilde.club Let me guess, sl? 😏

This looks like a botnet, to be honest. The IPs are all over the place. Ethopia, Brazil, Kenya, Lebanon, Netherlands, … I mean, that’s the logical thing to do, isn’t it? Do your web crawling on infected PCs. Nobody will block those, because those are the same IP ranges as legitimate requests. And obviously you don’t have to pay for computing time.

… and they all send invalid HTTP requests, all answered with HTTP 400 … How silly.

@bender@twtxt.net Just wrote better code with tests 🤣

@prologic@twtxt.net 🎉, what did you do? Details, details!

Car Size
⌘ Read more

@lyse@lyse.isobeef.org nginx allows logging per user, via using defined variables on configuration. Not sure, though, if a Tilde would be willing to go to those “extremes”.

Nothing too crazy, but still nice:

@bender@twtxt.net Sounds about right.

I had a brainfart yesterday, though. For whatever reason I thought of subdomains, which are modeled with server entries in nginx. So, each could define its own access_log location. However, there are no subdomains in place! Searching around, I didn’t find any solution to give each user their own access log file.

One way would be a cronjob, aeh, systemd timer as I learned the other day, that greps the main access log and writes all user access log files with only the relevant stuff.

@movq@www.uninformativ.de Haha, right. :-D

Ah, it’s this famous font. :-) I already thought so, but wasn’t sure if it’s actually the same.

Hmm, so it seems this Mike is the one who inherited it: https://tilde.club/~deepend/, but not too active anywhere, though pinging “deepend” on Libera might work…

@lyse@lyse.isobeef.org was it? Hmm, am I back to square one? 😅 Contacting one tilde could be a step ahead, but there are so many…!

@bender@twtxt.net Wasn’t that transferred to somebody else?

@movq@www.uninformativ.de Oh, fuck them!

@bender@twtxt.net Better safe than sorry, I guess. 😅

My goodness, a new level of stupidity.

The bots are now doing things like this:

GET http://uninformativ.de/projects/lariza/feednotify/datenstrahler/slinp/countty HTTP/1.1

1. That URL does not exist.
   
2. By including http://uninformativ.de in that request, this instructs the webserver to do an HTTP proxy request. Of course, this isn’t allowed on my webserver (and shouldn’t by allowed on any normal webserver), resulting in HTTP 400. And even if it were, the target would be the exact same server, making a proxy request unnecessary.
   

And of course, it’s not just 50 hits like this or 100 or 1’000 or 10’000. No, it’s over 150’000 in the last 2 days. All from vastly different IP ranges of different cloud hosters.

This almost looks like a DDoS attack, but it’s just completely stupid. This feels more like some idiot vibe coded a crawler.

@prologic@twtxt.net I found it for you. It is ford@ftrain.com.

@lyse@lyse.isobeef.org Well, they say you have to build up stocks, don’t they? 😅

The font is fiamf3 (scaled up 2x, it would be too small when printed). It’s the same one that I use in my terminal and the status bars. 😃