Searching We.Love.Privacy.Club

Twts matching #birthday
Sort by: Newest, Oldest, Most Relevant
bender
twtxt.net
 (3d ago)

@zvava@twtxt.net happy belated birthday! Also, I would love to see that website. I went to the one listed on your profile, and saw the old one, not this one. I like the current, and also the pink look of the one of the screenshot!

⤋ Read More
lyse
lyse.isobeef.org
 (4d ago)

@zvava@twtxt.net Late happy birthday! :-)

Cool, your website indeed mostly works even in w3m and ELinks. Sending notifications in the about page is out of question, since it requires JS. Apart from that, this is very good, keep it up!

Not sure how I can get the deskop look and feel working in Firefox, but since I’m a tiling window manager user, I prefer linear webpages anyway. :-)

⤋ Read More
lyse
lyse.isobeef.org
 (14w ago)

@thecanine@twtxt.net Nice! :-)

When tidying up my good mate’s birthday party site last night we emptied the beer pong cups which had been filled with just ordinary tap water. There was also a cute dog whose owner gave it its drinking bowl, but it was not interested. Just for fun I offered it one of those water cups and it began to drink. We all had to laugh so hard because it was completely unexpected and looked so funny. Can’t describe this comicalness of the situation. :-D

⤋ Read More
prologic
twtxt.net
 (27w ago)

Finally I propose that we increase the Twt Hash length from 7 to 12 and use the first 12 characters of the base32 encoded blake2b hash. This will solve two problems, the fact that all hashes today either end in q or a (oops) 😅 And increasing the Twt Hash size will ensure that we never run into the chance of collision for ions to come. Chances of a 50% collision with 64 bits / 12 characters is roughly ~12.44B Twts. That ought to be enough! – I also propose that we modify all our clients and make this change from the 1st July 2025, which will be Yarn.social’s 5th birthday and 5 years since I started this whole project and endeavour! 😱 #Twtxt #Update

⤋ Read More
falsifian
www.falsifian.org
 (1y ago)

@prologic@twtxt.net earlier you suggested extending hashes to 11 characters, but here’s an argument that they should be even longer than that.

Imagine I found this twt one day at https://example.com/twtxt.txt :

2024-09-14T22:00Z Useful backup command: rsync -a “$HOME” /mnt/backup

Image

and I responded with “(#5dgoirqemeq) Thanks for the tip!”. Then I’ve endorsed the twt, but it could latter get changed to

2024-09-14T22:00Z Useful backup command: rm -rf /some_important_directory

Image

which also has an 11-character base32 hash of 5dgoirqemeq. (I’m using the existing hashing method with https://example.com/twtxt.txt as the feed url, but I’m taking 11 characters instead of 7 from the end of the base32 encoding.)

That’s what I meant by “spoofing” in an earlier twt.

I don’t know if preventing this sort of attack should be a goal, but if it is, the number of bits in the hash should be at least two times log2(number of attempts we want to defend against), where the “two times” is because of the birthday paradox.

Side note: current hashes always end with “a” or “q”, which is a bit wasteful. Maybe we should take the first N characters of the base32 encoding instead of the last N.

Code I used for the above example: https://fossil.falsifian.org/misc/file?name=src/twt_collision/find_collision.c
I only needed to compute 43394987 hashes to find it.

⤋ Read More
quark
ferengi.one
 (4y ago)

Now, onto the real question: what to eat? Partner isn’t home, so zero nutritional supplements have been consumed, and I have been lazy enough not to go out to fetch me something. So… hmm, yeah. Going to an eight years old niece birthday “roller scatting” party in an hour, maybe I get lucky with a slice of pizza, or two. 🤣

⤋ Read More