twtxt

Timeline for https://twtxt.net/user/homer/twtxt.txt

🔄 Refresh timeline

👨‍💻 Login

Following: 16

darch https://twtxt.net/user/darch/twtxt.txt Remove

david https://netbros.com/user/david/twtxt.txt Remove

eaplmx https://twtxt.net/user/eaplmx/twtxt.txt Remove

fastidious@txt.quisquiliae.com https://txt.quisquiliae.com/user/fastidious/twtxt.txt Remove

fox https://twtxt.net/user/fox/twtxt.txt Remove

homer https://twtxt.net/user/homer/twtxt.txt Remove

jdtron gemini://tilde.team/~jdtron/twtxt.txt Remove

jlj https://twt.nfld.uk/user/jlj/twtxt.txt Remove

lyse https://lyse.isobeef.org/twtxt.txt Remove

movq https://www.uninformativ.de/twtxt.txt Remove

observer https://twtxt.net/user/observer/twtxt.txt Remove

prologic https://twtxt.net/user/prologic/twtxt.txt Remove

quark https://ferengi.one/twtxt.txt Remove

stigatle https://twtxt.net/user/stigatle/twtxt.txt Remove

tamer https://twtxt.net/user/tamer/twtxt.txt Remove

ullarah https://txt.quisquiliae.com/user/ullarah/twtxt.txt Remove


prologic
Cool! Our park has disappeared again this morning! 😱 Also it was cold outside! 🥶
5 hours ago
💬 Reply


prologic
Reply to #bbnfuvq
@lyse I'll fix it tonight Sadly I have to rebuild the index 🤦‍♂️
5 hours ago
💬 Reply


prologic
Reply to #bgoecxa
@lyse This ☝️
5 hours ago
💬 Reply


lyse
Reply to #adwbalq
@thecanine Step 1: Uninstall it. Step 2: Success! :-D
6 hours ago
💬 Reply


lyse
Reply to #qgdbh2a
@stigatle Safe ride, don't get injured!
6 hours ago
💬 Reply


lyse
Reply to #vyd7h3a
@bender Ah, thank you! <3 So, 14:00 UTC+2 might work out.
6 hours ago
💬 Reply


lyse
Heck yeah! I saw my first slow worm this year. Very cool. :-) We also came across some art in the woods. Surprisingly, the blackberries in the forest were mellower than the ones on the south side bushes with sun exposure all day long.

Blackberries
11 hours ago
💬 Reply


lyse
Reply to #vyd7h3a
@prologic I will try. Which time was it again?

The search engine is broken:

> Error error parsing created field: parsing time "1689093798000000000" as "2006-01-02T15:04:05Z07:00": cannot parse "093798000000000" as "-"
11 hours ago
💬 Reply


lyse
Reply to #g6v4kxq
@movq Ah, I did not have a portable diskman. Just a stationary radio with an integrated CD player. Or my parent's stereo. But it's sooo long ago, I can't remember how long switching tracks took. Yeah, on second thought, maybe a second. Well, that actually improved then. Finally. Nice. :-) Loading the CD took several seconds, that's for sure. And some devices were certainly slower than others.
11 hours ago
💬 Reply


movq
Reply to #g6v4kxq
@lyse Yeah, that has nothing to do with fun. 😅

I was thinking back to CD players. Switching tracks took a moment, although I don’t know anymore how long exactly. IIRC, playing CDs on a computer was a bit slower than in a dedicated player.

Don’t worry, switching to the next OGG file on my disk is basically instant. 😅
13 hours ago
💬 Reply


lyse
Reply to #juhuf5a
@prologic @bender Yep, @xuu's watcher would be my guess as well. :-D
13 hours ago
💬 Reply


lyse
Reply to #c7kyxoa
@movq @bender Thanks, mates. I was on the fence with 13 and 15. :-)
14 hours ago
💬 Reply


lyse
Reply to #g6v4kxq
@movq There's a big difference between being usable somehow and having fun using it. My tolerable limits are lower, but yeah. Up to five seconds for the "next track"? What music player are you using? :-D This must happen in way under a second, and luckily, this works here. :-) (But I'm also not streaming my music, it's all on the local disk.)
14 hours ago
💬 Reply


prologic
Oh I forgot again 🤦‍♂️ Last Saturday of the month, so if anyone's up for a friendly catch up over video tomorrow? Same time, same place 👌
14 hours ago
💬 Reply


prologic
Reply to #kwepmhq
@bender Weird dunno what to say🤣
14 hours ago
💬 Reply


prologic
Reply to #kwepmhq
@bender Huh? 🤔
15 hours ago
💬 Reply


prologic
Reply to #2rxkcca
Also FWIW this is all my fault for writing shitty vulnerable code 🤣 So blame me! I'm sorry 🙏
23 hours ago
💬 Reply


prologic
Reply to #2rxkcca
FWIW I'm still trying to find the the cause of the mult-GB avatars that both @stigatle and @abucci 's pods were both teying yo download. The flaw has since been fixed in the code but I'm still trying to investigate the source 🤞
23 hours ago
💬 Reply


prologic
Reply to #2qczosq
@bender Hehe 🤣
1 day ago
💬 Reply


prologic
Hmmm something happened last night at ~3am (AEST) that decrased traffic to my pod quite considerably... Hmmm? Anyone have any ideas? 💡
1 day ago
💬 Reply


movq
Reply to #g6v4kxq
@lyse But stuff is still “mostly usable”, isn’t it? It’s not like it became impossible to write a letter because everything has gotten so slow.

That’s what I meant by “absolute” performance: A human being tolerates a system boot up time of 0.5-2 minutes, for example, so there’s an absolute/fixed duration that any task is allowed to take. Boot: 0.5-2 minutes. Opening Word: 1-10 seconds. Saving an image file: 1-10 seconds. Time until the next song starts to play when you click “next track”: 0-5 seconds. Stuff like that. As long as we don’t exceed those durations, people will be more or less happy.

Wasted potential? Ab-so-fucken-lutely.

(Maybe I’m repeating myself. I’m tired. Sorry. 😅)
1 day ago
💬 Reply


movq
Reply to #c7kyxoa
@lyse Uhh, nice. Haven’t seen a sunset like that in a while, I think. 🤔
1 day ago
💬 Reply


lyse
Reply to #2rxkcca
@abucci Can you please check if you reported @xuu's IP address 162.211.155.2 on mistake and let his ISP know that this was some false alarm? They're monitoring his traffic to your server and treating this as continued abuse. :-(

(His twts have been synced to your yarnd by yarnd's gossip protocol.)
1 day ago
💬 Reply


lyse
Reply to #2rxkcca
@abucci Just making sure you're seeing @xuu's twt, in case he's still on your blacklist:

> Hey so.. i just got an email from my ISP saying they will terminate my service. Did i break something @abucci ?
>
> – https://txt.sour.is/twt/oohzbqa
1 day ago
💬 Reply


prologic
Reply to #rdeh4dq
@abucci No worries! All in the name of better reliability and security 😅
1 day ago
💬 Reply


prologic
Reply to #4ljpfuq
@stigatle Thanks! Sooo cold 🥶
1 day ago
💬 Reply


prologic
Reply to #2rxkcca
@stigatle no problems 👌 one problem solved at least 🤣
1 day ago
💬 Reply


prologic
Anyway, I'm gonna have to go to bed... We'll continue this on the weekend. Still trying to hunt down some kind of suspected mult-GB avatar using @stigatle 's pod's cache:

```
$ (echo "URL Bytes"; sort -n -k 2 -r < avatars.txt | head) | column -t
URL Bytes
https://birkbak.neocities.org/avatar.jpg 667640
https://darch.neocities.org/avatar.png 652960
http://darch.dk/avatar.png 603210
https://social.naln1.ca/media/0c4f65a4be32ff3caf54efb60166a8c965cc6ac7c30a0efd1e51c307b087f47b.png 327947
...
```

But so far nothing much... Still running the search...
1 day ago
💬 Reply


prologic
Reply to #2rxkcca
Out of interest, are you able to block whole ASN(s)? I blocked the entirely of teh AWS and Facebook ASN(s) recently.
1 day ago
💬 Reply


prologic
Reply to #2rxkcca
@abucci Oh 🤣 Well my IP is a known subnet and static, so if you need to know what it is, Email me 😅
1 day ago
💬 Reply


prologic
Reply to #2rxkcca
@abucci Seems to be okay now hmmm
1 day ago
💬 Reply


prologic
Reply to #qv5sgja
@abucci Hmm I can see your twts on my pod now 🤔
1 day ago
💬 Reply


prologic
@abucci / @abucci Any interesting errors pop up in the server logs since the the flaw got fixed (_unbounded `receieveFile()`_)? 🤔
1 day ago
💬 Reply


prologic
Hmmm 🧐

```
for url in $(jq -r '.Twters[].avatar' cache.json | sed '/^$/d' | grep -v -E '(twtxt.net|anthony.buc.ci|yarn.stigatle.no|yarn.mills.io)' | sort -u); do echo "$url $(curl -I -s -o /dev/null -w '%header{content-length}' "$url")"; done
...
```

😅 Let's see... 🤔
1 day ago
💬 Reply


lyse
Reply to #g6v4kxq
@movq My issue is, now that we have the chance of getting something fast, people artificially slow it down again. Wether they think it's cool that they added some slow animation or just lack of knowledge or whatever. The absolute performance does not translate to the relative performance that I observe. Completely wasted potential. :-(

In today's economy, nobody optimizes something if it can be just called good enough with the next generation hardware. That's especially the mindset of big coorporations.

Anyway, getting sidetracked from the original post. :-)
1 day ago
💬 Reply


prologic
Reply to #ve43paq
@stigatle The one you sent is fine. I'm inspecting it now. I'm just saying, do yourself a favor and nuke your pod's garbage cache 🤣 It'll rebuild automatically in a much more prestine state.
1 day ago
💬 Reply


prologic
Reply to #ve43paq
That was also a source of abuse that also got plugged (_being able to fill up the cache with garbage data_)
1 day ago
💬 Reply


prologic
Reply to #ve43paq
Ooof

```
$ jq '.Feeds | keys[]' cache.json | wc -l
4402
```

If you both don't mind dropping your caches. I would recommend it. Settings -> Poderator Settings -> Refresh cache.
1 day ago
💬 Reply


lyse
Reply to #c7kyxoa
@prologic Yup. Didn't regret climbing these three hundred odd meters of elevation. :-)
1 day ago
💬 Reply


prologic
Reply to #ve43paq
@stigatle Thank you! 🙏
1 day ago
💬 Reply


prologic
Reply to #ve43paq
@stigatle Ta. I hope my theory is right 😅
1 day ago
💬 Reply


prologic
Reply to #ve43paq
But just have a look at the `yarnd` server logs too. Any new interesting errors? 🤔 No more multi-GB tmp files? 🤔
1 day ago
💬 Reply


prologic
Reply to #ve43paq
@stigatle You want to run `backup_db.sh` and `dump_cache.sh` They pipe JSON to stdout and prompt for your admin password. Example:

```
URL=<your_pod_url> ADMIN=<your_admin_user> ./tools/dump_cache.sh > cache.json
```
1 day ago
💬 Reply


lyse
Reply to #ug2ndqa
@stigatle Worky, worky now! :-)

Mate, these are some really nice gems! What a stunning landscape. I love it. Holy cow, that wooden church looks really sick. Even though, I'm not a scroll guy and prefer simple, straight designs, I have to say, that the interior craftmanship is something to admire.
1 day ago
💬 Reply


prologic
Reply to #ve43paq
Just thinking out loud here... With that PR merged (_or if you built off that branch_), you _might_ hopefully see new errors popup and we might catch this problematic bad feed in the act? Hmmm 🧐
1 day ago
💬 Reply


prologic
Reply to #ybzi67q
@slashdot I _thought_ Sunday was the hottest day on Earth 🤦‍♂️ wtf is wrong with Slashdot these days?! 🤣
1 day ago
💬 Reply


prologic
Reply to #ve43paq
if we can figure out wtf is going on here and my theory is right, we can blacklist that feed, hell even add it to the codebase as an "asshole".
1 day ago
💬 Reply


prologic
Reply to #ve43paq
@stigatle The problem is it'll only cause the attack to stop and error out. It won't stop your pod from trying to do this over and over again. That's why I need some help inspecting both your pods for "bad feeds".
1 day ago
💬 Reply


prologic
Reply to #ve43paq
@abucci / @stigatle Please `git pull`, rebuild and redeploy.

There is also a shell script in `./tools` called `dump_cache.sh`. Please run this, dump your cache and share it with me. 🙏
1 day ago
💬 Reply


prologic
Reply to #ve43paq
I'm going to merge this...
1 day ago
💬 Reply


⏭️ Next