I’ll be using another URL for this twtxt.

The older one will redirect to the new for a while (I’m not sure what would happen if you follow both URLs, I assume it’s better to add the new one and remove the older)

Please update your following list to https://eapl.me/tw.txt !

Thanks @lyse@lyse.isobeef.org! I’m replying here https://text.eapl.mx/reply-to-lyse-about-twtxt

I’ve been thinking of a few improvements for the next generation of twtxt spec, let me know if these are useful or interesting :) https://text.eapl.mx/a-few-ideas-for-a-next-twtxt-version

I came across Google Summer of Code

This one looks interesting, I’ll apply soon, and perhaps is interesting for you as well
https://kiwix.org/en/google-summer-of-code/

Would ‘twtxt’ be a good project for the next one? 🤔

After getting used to it, I’m loving this date format:
2024-02-06

I liked ‘6feb2024’, although isn’t as international as the former.
And… ‘06/02/24’ is awful, don’t use it!

Ha, this is cool. Has its flaws, although is easy to remember.

An RNG that runs in your brain

https://www.hillelwayne.com/post/randomness/

Ha, this is gold!

Raymond Chen Interview (19:31)
https://youtu.be/HDicLHBvQQM

I’ve been reading “Shareware Heroes: The renegades who redefined gaming at the dawn of the internet” learning of games developed before I was born, or when was too small.
I’m finding old gems to play and understanding that we have the same problems developing games 30+ years after, although with some obvious differences.

Currently playing:
https://www.classicdosgames.com/game/Kentris.html

Which reminds me of another Tetris I don’t know how it came to my PC in the 90s.
https://www.youtube.com/watch?v=VaK7v8UNjo0

I’ve been thinking of how to notify someone else that you’ve replied to their twts.

Is there something already developed, for example on yarn.social?

Let’s say I want to notify https://sour.is/tiktok/America/Denver.txt that I’ve replied to some twt. They don’t follow me back, so they won’t see my reply.

I would send my URL to, could be, https://sour.is/tiktok/replies?url=MY_URL and they’ll check that I have a reply to some of their twts, and could decide to follow me back (after seeing my twtxt profile to avoid spam)

Another option could be having a metadata like
follow-request=https://sour.is/tiktok/America/Denver.txt TIMESTAMP_IN_SECONDS
that the other client has to look for, to ensure that the request comes from that URL (again, to avoid spam)
This could be deleted after the other .txt has your URL in the follow list, or auto-expire after X days to clean-up old requests.

What do you think?

Today I was fighting against a TOTP library in PHP, since it works for 6 and 8 digits, but for 10 it was giving inconsistent values, due to a conversion to a 32 bits int.

It felt amazing when, after a few hours, I found what was causing the error…

And found that many libraries have the same problem.
Now I get why TOTP is limited to 8 chars. It’s a 2FA but not a Password. Perhaps another algorithm will be needed to support 16 digits.