@bender@twtxt.net / @mckinley@twtxt.net could you both please change your password immediately? I will also work on some other security hardening that I have a hunch about, but will not publicize for now.

Hmm I see it! It’s so obvious 🤦‍♂️ I smell an attack of some kind.

@lyse@lyse.isobeef.org No problems! Is it stils in the list when I redo this search, it’ll be gone 😅

@lyse@lyse.isobeef.org This is really weird. Do you have an example of this bracketed text? Re peers, I’m aware of all the peers, nothing surprising there.

@mckinley@twtxt.net That’s actually all I used it for myself 👌 All those other “bells ‘n whistles” are really just Traefik supporting lots of alternate setups and drivers for discovery, etc.

@bender@twtxt.net LOL 🤣

@bender@twtxt.net LOL 🤣

$ wc -l inactive.txt
152 inactive.txt

👋 At some point over the next day or two I will be deleting the following feeds/accounts:

https://gist.mills.io/prologic/ae61ae2bfba6401e8955a33394fd858b

If anyone spots anything on this list that shouldn’t be deleted, please let me know! 🙏

@lyse@lyse.isobeef.org@

We’ll kind of the backend fixes it or grid to 🤣

@movq@www.uninformativ.de@ does not hmmm

@prologic@twtxt.net works

The mobile autocomplete bug is something I can reproduce and likely fix soon™ – I think its happenning because I accidentally nuked this pod’s cache the other day (sorry!) 😢 – But it is also a bug 🐛

Like what was this meant to be anyway?

"[Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=]"

As for @mckinley@twtxt.net ’s odd Twt, I only see one instance of this:

2023-01-09T22:42:37Z	(#dusjj6a) @<lyse https://lyse.isobeef.org/twtxt.txt> As far as I know, they're still visible in the Web UI. Although, in the mobile app and youtube.com, I believe it tells you that the video isn't available without having to click on it. They don't tell you that in the RSS feed, and I agree; it gets annoying.

If we had a custom feed generator that hooks directly into the YouTube API, I'll bet we could find that information and put "[Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=][Scheduled][Scheduled=]" in the title for premieres and remove it when the video is available.

And I have no fucking clue how this happened. I can’t imagine anything in the yarnd codebase would be responsible for this weirdness 🤣

@mckinley@twtxt.net Nah it wasn’t me, trust me 🤣 I actually use Traefik for my ingres.

I don’t think I’m smart enough to figure this out 😅

I can’t explain this. I’m leaning towards a peering pod being responsible for producing a different hash, and twtxt.net pulling that in from a peer. But that would only happen if my pod doesn’t have the Root Twt ans asked its peers for it. And that implies other pods are producing incorrect/different hashes “somehow”. So all of that seems highly unlikely tbh.

bsormva is not a hash found in @lyse@lyse.isobeef.org ’s feed at all according to yarnc debug which is printing the hash and corresponding Twt per line.

That is this one:

ta6uu5q 2024-08-03T19:30:00+02:00	(#puxvjcq) Hmmm, what is going on here? ...

A equivalent yarnc debug <url> only sees the 2nd hash

Computers aren’t meant to give me three different answers 🤣

@movq@www.uninformativ.de / @lyse@lyse.isobeef.org / @xuu any ideas wut da fuq is going on here?! 🤣

In fact I cannot produce eitehr of these hashes:

$ pbpaste | ./yarnc hash -u https://lyse.isobeef.org/twtxt.txt -t 2024-08-03T19:30:00+02:00 -
bsormva

What da fuq?!

$ bat https://twtxt.net/twt/7hraijq | jq -r '.text' | ./yarnc hash -u https://lyse.isobeef.org/twtxt.txt -t 2024-08-03T19:30:00+02:00 -
bsormva

Yeah, this looks like a hash collision to me right? Same twt, same timestamp, same twter, produces two different hashes? I’m not even sure how da fuq this is even possible?

$ diff <(bat https://twtxt.net/twt/7hraijq | jq '.') <(bat https://twtxt.net/twt/ta6uu5q | jq '.')
10c10
<   "hash": "7hraijq",
---
>   "hash": "ta6uu5q",

@lyse@lyse.isobeef.org (ahh auto-complete is broken only on Mobile?) @xuu is our hashing reached a point where it’s broken and needs to be dumped? 🤔

What da actual fuq?! They have the same timestamp too!

$ bat https://twtxt.net/twt/7hraijq | jq '.created'
"2024-08-03T19:30:00+02:00"
$ bat https://twtxt.net/twt/ta6uu5q | jq '.created'
"2024-08-03T19:30:00+02:00"

And the same Twter (URI)

Hm mm these are identical in content:

$ diff -Ndru <(bat https://twtxt.net/twt/7hraijq | jq -r '.text') <(bat https://twtxt.net/twt/ta6uu5q | jq -r '.text') | wc -l
0

@bender@twtxt.net Shy are those seem like dupes with different hashes?

Nope none that I can think of 🤔

Yeah okay I can reproduce that weird auto-complete bug

Hmm like @lyse@lyse.isobeef.org

Hmm I’m not sure either 🤔

I’ve been tricked! 🤣

@lyse@lyse.isobeef.org Of! It’s not real?! 😱

@movq@www.uninformativ.de I think you’re mistaking expectations for quality software 🤣 When have you ever seen quality software out of an enterprise? 😅

@movq@www.uninformativ.de Bahahaha 🤣

@movq@www.uninformativ.de So you gotta write your own TCP/IP stack right? 😅 Did that for an undergrad uni assignment, how hard can it. be 🤣

@movq@www.uninformativ.de Oh wow that’s a nice shot! 👌 Don’t think I’ve ever seen an Owl like this! What species of owl is it? 🤔

@movq@www.uninformativ.de And you thought it would be what exactly? 🤔 This is Meta we’re talking about 🤣

@lyse@lyse.isobeef.org Well we lost all three rounds 🤣 6-1 6-1 7-0 😱

@lyse@lyse.isobeef.org Hehe these are accounts that haven’t been used for over 800 days 🤣

@mckinley@mckinley.cc what makes it so great? 🤔

@shreyan@twtxt.net Haha my criteria is being inactive for over two years 🤣

If every Yarn pod had a good ~10 or so friends/family/co-workers/colleagues and we grew Yarn.social one pod at a time, I’d be very happy 😊

Interesting stats here. My pod has some ~250 accounts/feeds, of which only ~10 are actually actively used. Just doing some “house cleaning” here, and since the good ‘ol days of “oh wow this is cool, new and shiny!”, well that’s gone, and since then I’ve turned off open registration, so most of this is just garbage and spam. 😅

FYI: I will be deleting the following 57 inactive (dead?) users on this pod today:

henseegeek fundor333 westbam onlyfansreview mabdalrahman retronav crunched deebs tca qwe234 pfefferle razetime kayos marguesto john yale slackjeff kodaira313a denisovich mlctrez jcrawford l3db3tt3r crunch homer mjy testdrive neoboard svendowideit palash k0rr stxh nirmal_kumar jan6 bram frankiem cvshumake qazsx apoorv10 duriny_test heyjude asepaned testest kevin natascha_e papz anvis spammer lonfas kamme dooven aatikakhan enochthec aman justinakers pc dai superyarn

If you wish to keep your account/feed, please login immediately. You have ~12 hours from this post (as I’ll be out playing table-tennis 🎾)

@tkanos@twtxt.net Thanks!

Pretty sure those peaks and troughs are the feed fetchers, which one of these days I’ll trry to optimize and smooth out. 😅