#sy2nsaq
(#bbnfuvq) @lyse@lyse.isobeef.org I’ll fix it tonight Sadly I have to rebuild the index 🤦♂️
#f5z4u5a
(#bgoecxa) @lyse@lyse.isobeef.org This ☝️
#joyhtaa
(#adwbalq) @thecanine@twtxt.net Step 1: Uninstall it. Step 2: Success! :-D
#bgoecxa
(#qgdbh2a) @stigatle@yarn.stigatle.no Safe ride, don’t get injured!
#56op4pa
(#vyd7h3a) @bender@twtxt.net Ah, thank you! So, 14:00 UTC+2 might work out.
#mfecska
(#74h6s4a) its not remote… though its on a mountain side where the land grants allowed monopolies to occur. Pretty wild that it happened but only specific vendors have utility right of ways. Its been in litigation with the city for years.
#q7aq4eq
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.
#n4hrq4q
(#vyd7h3a) @prologic@twtxt.net I will try. Which time was it again?
Error error parsing created field: parsing time “1689093798000000000” as “2006-01-02T15:04:05Z07:00”: cannot parse “093798000000000” as “-”
#bbnfuvq
(#g6v4kxq) @movq@www.uninformativ.de 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.
#uw2s6ja
(#g6v4kxq) @lyse@lyse.isobeef.org 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. 😅
#p4bkqja
(#juhuf5a) @prologic@twtxt.net @bender@twtxt.net Yep, @xuu@txt.sour.is’s watcher would be my guess as well. :-D
#jg7vgza
(#c7kyxoa) @movq@www.uninformativ.de @bender@twtxt.net Thanks, mates. I was on the fence with 13 and 15. :-)
#gb5zbya
(#g6v4kxq) @movq@www.uninformativ.de 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.)
#okcba3a
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 👌
#vyd7h3a
(#kwepmhq) @bender@twtxt.net Weird dunno what to say🤣
#z6h6lea
(#kwepmhq) @bender@twtxt.net Huh? 🤔
#lr6jm3a
(#2rxkcca) Also FWIW this is all my fault for writing shitty vulnerable code 🤣 So blame me! I’m sorry 🙏
#qbhy3aa
(#2rxkcca) FWIW I’m still trying to find the the cause of the mult-GB avatars that both @stigatle@yarn.stigatle.no and @abucci@anthony.buc.ci ’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 🤞
#67izzzq
(#2qczosq) @bender@twtxt.net Hehe 🤣
#kdylkbq
Hmmm something happened last night at ~3am (AEST) that decrased traffic to my pod quite considerably… Hmmm? Anyone have any ideas? 💡
#juhuf5a
(#g6v4kxq) @lyse@lyse.isobeef.org 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. 😅)
#d3phqxq
(#c7kyxoa) @lyse@lyse.isobeef.org Uhh, nice. Haven’t seen a sunset like that in a while, I think. 🤔
#dou2fsa
(#74h6s4a) @bender@twtxt.net haha funny! though i just realized my ISP is the only one with fiber pulled to the property so i would have to get a phone line from them some how. The other ISP in the area is basically a mobile hotspot.
#gxkkveq
(#2rxkcca) @abucci@anthony.buc.ci Can you please check if you reported @xuu@txt.sour.is’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.)
#fpkcola
(#2rxkcca) > We received the abuse report below regarding network abuse from the IP address indicated.
On researching I see that HTTPS (tcp 443) traffic is continuing and originating from you NAT IP address 100.64.x.x
This was further found to be originating from your firewall/router at 192.168.x.x (MAC D8:58:D7:x:x:x).
This abuse is continuing and constitues a violation of [ISP] Acceptable Use Policy and Terms of Service.
Please take action to identify the source of the abuse and prevent it from continuing.
Failure to stop the abuse may result in suspension or cancellation of service.Thank you,
#g76hxoq
(#2rxkcca) he emailed my ISP about causing logging abuse. This is the only real ISP in my area, its gonna basically send me back to dialup.
#74h6s4a
(#2rxkcca) @abucci@anthony.buc.ci Just making sure you’re seeing @xuu@txt.sour.is’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 ?
#iwghaoa
(#2rxkcca) Hey so.. i just got an email from my ISP saying they will terminate my service. Did i break something @abucci@anthony.buc.ci ?
#oohzbqa
(#rdeh4dq) @abucci@anthony.buc.ci No worries! All in the name of better reliability and security 😅
#antz3fq
(#4ljpfuq) @stigatle@yarn.stigatle.no Thanks! Sooo cold 🥶
#az3enqa
(#2rxkcca) @stigatle@yarn.stigatle.no no problems 👌 one problem solved at least 🤣
#mif74ta
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@yarn.stigatle.no ’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…
#4ljpfuq
(#2rxkcca) Out of interest, are you able to block whole ASN(s)? I blocked the entirely of teh AWS and Facebook ASN(s) recently.
#jdbq3la
(#2rxkcca) @abucci@anthony.buc.ci Oh 🤣 Well my IP is a known subnet and static, so if you need to know what it is, Email me 😅
#at366ma
(#2rxkcca) @abucci@anthony.buc.ci Seems to be okay now hmmm
#6if5wwq
(#qv5sgja) @abucci@anthony.buc.ci Hmm I can see your twts on my pod now 🤔
#jefrymq
@abucci@anthony.buc.ci / @abucci@anthony.buc.ci Any interesting errors pop up in the server logs since the the flaw got fixed (unbounded receieveFile()
)? 🤔
#2rxkcca
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… 🤔
#axhnc6a
(#g6v4kxq) @movq@www.uninformativ.de 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. :-)
#ae43b6a
(#ve43paq) @stigatle@yarn.stigatle.no 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.
#fx2mzfq
(#ve43paq) That was also a source of abuse that also got plugged (being able to fill up the cache with garbage data)
#pa54ixq
(#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.
#mwe4fhq
(#c7kyxoa) @prologic@twtxt.net Yup. Didn’t regret climbing these three hundred odd meters of elevation. :-)
#cz65dda
(#ve43paq) @stigatle@yarn.stigatle.no Thank you! 🙏
#dpclfsa
(#ve43paq) @stigatle@yarn.stigatle.no Ta. I hope my theory is right 😅
#jjpj3ra
(#ve43paq) But just have a look at the yarnd
server logs too. Any new interesting errors? 🤔 No more multi-GB tmp files? 🤔
#bg6ssma
(#ve43paq) @stigatle@yarn.stigatle.no 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
#d2lvjma
(#ug2ndqa) @stigatle@yarn.stigatle.no 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.
#botltwa
(#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 🧐
#t4h77hq