I mean, really, it couldn’t get any better. I love it!

@prologic@twtxt.net Wikipedia claims sha1 is vulnerable to a “chosen-prefix attack”, which I gather means I can write any two twts I like, and then cause them to have the exact same sha1 hash by appending something. I guess a twt ending in random junk might look suspcious, but perhaps the junk could be worked into an image URL like . If that’s not possible now maybe it will be later.

git only uses sha1 because they’re stuck with it: migrating is very hard. There was an effort to move git to sha256 but I don’t know its status. I think there is progress being made with Game Of Trees, a git clone that uses the same on-disk format.

I can’t imagine any benefit to using sha1, except that maybe some very old software might support sha1 but not sha256.

@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

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

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.

@bender@twtxt.net, cool, so I can join the threads, but your edit to the original will never show at my end. Will have @bender@twtxt.net show the screenshot.

@prologic@twtxt.net What? I compiled, updated, and restarted. If you check what my pod reports, it gives that 7a… SHA. I don’t know what that other screenshot is showing but it seems to be out of date. That was the SHA I was running before this update.

you’ll probably get an Error 1011 🤦 … just copy and paste the link in a new tab if you can Screenshot of neomutt running Jenny

@bender@twtxt.net My index formatting is intact, probably because I still haven’t figured out how to set up my terminal to show RTL text correctly! 😅 but hey, that won’t be a problem anymore, I don’t feel like twting in Arabic. Sorry for the inconvenience.

@quark@ferengi.one this is what I see:

@aelaraji@aelaraji.com, this one, @movq@www.uninformativ.de, is slightly breaking my neomutt index. Will post screenshot from @bender@twtxt.net’s account.

my current desktop #screenshot https://0x0.st/XKRk.png . I enjoy june’s scheme https://causal.agency/scheme.png

I guess I’m not missing my GUI Web Browser yet. In fact, I think I’m enjoying this. 😆

I might even drop to TTY to try stuff I read about earlier today.

@aelaraji@aelaraji.com a bit on the tangent, what font is that one on your screenshot?

@prologic@twtxt.net Thank
you! and here’s a twt with the said random characters, since I’ve been
cleaning them up manually, earlier before scp-ing my twtxt.txt file. And
maybe a screenshot of how things look in my editor?

Those new lines are added automatically as I type (except for the ones
after the screenshot.

@lyse@lyse.isobeef.org its a hierarchy key value format. I designed it for the network peering tools i use.. I can grant access to different parts of the tree to other users.. kinda like directory permissions. a basic example of the format is:

@namespace
# multi
# line
# comment
root :value

# example space comment
@namespace.name space-tag 

# attribute comments
attribute attr-tag  :value for attribute

# attribute with multiple 
# lines of values
foo :bar
      :bin
      :baz

repeated :value1
repeated :value2

each @ starts the definition of a namespace kinda like [name] in ini format. It can have comments that show up before. then each attribute is key :value and can have their own # comment lines.
Values can be multi line.. and also repeated..

the namespaces and values can also have little meta data tags added to them.

the service can define webhooks/mqtt topics to be notified when the configs are updated. That way it can deploy the changes out when they are updated.

@prologic@twtxt.net I always liked bit.
I am disappointed that a GUI app would not at least have screenshots.

One year ago to the date I made the lastest update for #phpub2twtxt to github and now 365 days later I have published #pixelblog as its successor - lets see where things are going for trip around the sun

New darchness coloursceme

testing public path copy/pasted from code:

More #pixelblog‘ing - today wotking on fixing all the semi-hardcoded paths an moving them to config.php

#pixelblog is slowly coming together with support for posting images and simple theming

@movq@www.uninformativ.de This is awesome! Your server/connection is slow, thought. It took ages to load the GIF! Off topic, what font are you using on that screenshot?

Added to the fun.

Geting screenshots from video element seems to be relatively easy