For the first time, this year this "japanese quince" flowered. I only think it is a japanese quince now due to the red flower with yellow stems in this picture, I had no clue what it was previously.
For the first time, this year this "japanese quince" flowered. I only think it is a japanese quince now due to the red flower with yellow stems in this picture, I had no clue what it was previously.
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
Great spotted woodpecker hammering on a branch in a tree
Ruined Hohenrechberg Castle, today's hiking destination86 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?
Website: https://baldo.cat/
Twtxt: https://baldo.cat/twtxt.txt
#catsoftwtxt
Website: https://baldo.cat/
Twtxt: https://baldo.cat/twtxt.txt
#catsoftwtxt
2025-03-02T13:20:00-07:00 (#<fmgas3a https://twtxt.net/user/prologic/twtxt.txt?t=2025-03-02T10:12:13Z>) @<prologic https://twtxt.net/user/prologic/twtxt.txt> its hard to change by consensus. Some things are won in implementation.
if you look at the subject for that twt you will see that it uses the extended hash format to include a URL address.
https://blog.jupyter.org/real-time-collaboration-and-collaborative-editing-for-gis-workflows-with-jupyter-and-qgis-d25dbe2832a6
#Python #GeoData
About the idea of improving the "thread" extension, what if we set aside March 2025 to gather proposals and thoughts from everyone? We could then vote on them at the end of the month to see if the change and migration are worth it.
The voting could include client maintainers (and maybe even users too). That way, we get a good mix of perspectives before taking a decision in a decent timelapse.
What do you think? If this sounds good, we can start agreeing on this. Let me know your thoughts!