





https://git.mills.io/yarnsocial/go-lextwt/pulls/17
Actually it was your old feed on eapl.mx
https://git.mills.io/yarnsocial/go-lextwt/pulls/17
Actually it was your old feed on eapl.mx
https://github.com/villares/python-visual-context/blob/main/Processing-Python-py5/simultaneous_keys.md
This is a machine translated version of a tutorial I made for my classes (from https://abav.lugaralgum.com/material-aulas)... I'd like to translate more stuff into English this year, but I'd need more support (donations) in order to have the time to do this. Things have been tough lately: I should be trying to find more classes to teach, but I'm somewhat overworked already :(
If you'd like to support my work:
- https://liberapay.com/villares
- https://www.paypal.com/donate/?hosted_button_id=5B4MZ78C9J724
#Processing #Python #CreativeCoding


https://history.state.gov/historicaldocuments/frus1969-76ve11p2/d99
via Matias Spektor
> Video unavailable
🥲🥲
EuroActiv has a nice new article about all of this:
https://www.euractiv.com/section/tech/news/deafening-commission-silence-with-no-credible-eu-us-data-oversight-left/
The most important thing there, for me, is at the end:
"if the EU executive does scrap the deal, it will undoubtedly be seen as a political move against Washington. Better to say and do nothing in the meantime, seems to be the policy.
But silence can’t last forever.
On 5 February, 19 MEPs from across the political spectrum called on the Commission to address the question of whether the DPF is still viable. The Commission has until 19 March to respond in writing.
On 6 February, the chair of the Civil Liberties, Justice and Home Affairs (LIBE) Committee wrote to Commissioner McGrath asking whether the DPF still meets the essential equivalence requirement established by the ECJ after the PCLOB shootings and whether this affects the validity of the DPF.
Schrems told Euractiv that the Commission's silence could leave companies in the legal limbo of an invalidated DPF.
“My biggest worry... is that there is no fucking contingency plan,” he said."
EuroActiv has a nice new article about all of this:
https://www.euractiv.com/section/tech/news/deafening-commission-silence-with-no-credible-eu-us-data-oversight-left/
The most important thing there, for me, is at the end:
"if the EU executive does scrap the deal, it will undoubtedly be seen as a political move against Washington. Better to say and do nothing in the meantime, seems to be the policy.
But silence can’t last forever.
On 5 February, 19 MEPs from across the political spectrum called on the Commission to address the question of whether the DPF is still viable. The Commission has until 19 March to respond in writing.
On 6 February, the chair of the Civil Liberties, Justice and Home Affairs (LIBE) Committee wrote to Commissioner McGrath asking whether the DPF still meets the essential equivalence requirement established by the ECJ after the PCLOB shootings and whether this affects the validity of the DPF.
Schrems told Euractiv that the Commission's silence could leave companies in the legal limbo of an invalidated DPF.
“My biggest worry... is that there is no fucking contingency plan,” he said."
#running
#running
#running


86 more photos: https://lyse.isobeef.org/wanderung-auf-den-hohenrechberg-2025-03-03/
What about discussing it in https://git.mills.io/yarnsocial/twtxt.dev ?
The only con I see is that everyone would need to create an account there to participate.
The editing process needs a lot of consideration and compromises.
From one side, editing and deleting it's necessary IMO. People will do it anyway, and personally I like to edit my texts, so I'd put some effort on make it work.
Should we keep a history of edits? Should we hash every edit to avoid abuse? Should we mark internally a twt as deleted, but keeping the replies?
I think that's part of a more complete 'thread' extension, although I'd say it's worth to agree on something reflecting the real usage in the wild, along with what people usually do on other platforms.
96473B4F_1
-- That is SHA256SUM(feed_url)_<monotomic_feed_post_id>
About alice's hash, using SHA256, I get
96473b4f
or 96473B4F
for the last 8 characters. I'll add it as an implementation example.The idea of including it besides the follow URL is to avoid calculating it every time we load the file (assuming the client did that correctly), and helps to track replies across the file with a simple search.
Also, watching your example I'm thinking now that instead of
{url=96473B4F,id=1}
which is ambiguous of which URL we are referring to, it could be something like:{reply_to=[URL_HASH]_[TWT_ID]}
/ {reply_to=96473B4F_1}
That way, the 'full twt ID' could be
96473B4F_1
.
# default_lang = en
# discovery_url = https://example.com/discovery/
# follow = alice https://example.com/alice.txt ABCDEF12
# follow = alice gemini://example.com/alice.txt
# avatar = https://example.com/avatar/alice.png
# avatar = gemini://example.com/avatar/alice.png
1 2025-03-03T15:00:00-04:00 {lang=en} Hello, world! Welcome to my twtxt feed. UTF-8 check: é, ö, ü.
2 2025-03-03T15:05:00-04:00 {lang=es} ¡Hola, mundo! This tweet is in Spanish.
3 2025-03-03T15:10:00-04:00 {url=ABCDEF12,id=1} Replying to tweet 1 using its URL hash.
4 2025-03-03T15:15:00-04:00 {edited=1} This tweet has been edited once.
5 2025-03-03T15:20:00-04:00 {lang=fr} Bonjour le monde! A French twt overriding the default language.
6 2025-03-03T15:25:00-04:00 Regular twt without metadata defaults to en.
As in https://eapl.me/timeline/post/s7gv6zq
I changed my URL to experiment on this exact situation, and deleted the symlink on my server, so now tw.txt is the only way to get the file, although I could bring it back, what does everyone say?