Searching We.Love.Privacy.Club

Twts matching #birthday
Sort by: Newest, Oldest, Most Relevant
bmallred
staystrong.run
 (1y ago)

Kissimmee - Long run: 7.25 miles, 00:09:55 average pace, 01:11:52 duration
fun long run while we were at universal studios for a friends birthday. google maps thought there were some cut-throughs but was obviously wrong so just kind of winged it. was able to run around some of the “pioneer village” which was a good change in scenery.
#running

⤋ 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
cncf
feeds.twtxt.net
 (1y ago)

Happy 7th Birthday, Istio!
Project post originally published on the Istio blog by Lin Sun, Solo.io, for the Istio Steering Committee Celebrating Istio’s momentum and exciting future. On this day in 2017, Google and IBM announced the launch of the Istio service mesh…. ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (1y ago)

Ignite Realtime Blog: Happy Birthday, Jabber!
Today marks the 25th birthday of Jeremie Miller’s announcement of “a new project to create a complete open-source platform for Instant Messaging” on Slashdot.

How have things progressed since then!

By far most of the projects that we maintain here in the IgniteRealtime.org community make direct use of the XMPP protocol, which is the name used for t … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (2y ago)

yaxim: Planned downtime + Happy 10th anniversary, yax.im!
Our Android XMPP client yaxim was created in 2009. A decade later,
we celebrated its round birthday.
To make the user
experience more straightforward, we launched the
yax.im public XMPP service
in November 2013, to become the default server in yaxim. Now, ten years later,
it’s time to recap and to upgrade the hosting infrastructure.

Downti … ⌘ Read more

⤋ Read More
marcos-marado-atmind_booster
feeds.twtxt.net
 (3y ago)

**The SDF Public Access UNIX System Celebrates 35 Years!

Here’s what I wrote about SDF back on the 20th anniversary, only now more impressive as SDF goes on in operation, and still faithful to the same ideas, objectives and modus operandi.

Happy birthday!

https://mindboosternoori.blogspot.com/2007/06/sdf-celebrates-20-years.html**
The SDF Public Access UNIX System Celebrates 35 Years!

Here’s what I wrote about SDF back on the 20th anniversary, only now more impressive as SDF goes on in operation, and still … ⌘ Read more

⤋ Read More