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!
https://py.geocompx.org/
#GIS #geodata #FLOSS #Geocomputation #Python
Update: já no Garoa
#hackerspace #SãoPaulo #carnaval #carnahacking
Still, it is important to acknowledge what is and has been going on - how a web browser currently became a lot more than just a piece of software implementing a number of open standards, how they are all basically based over one of two existing browser agents (Gecko and Webkit) with the emergence of two upcoming ones (Servo and LibWeb); the difficulties of creating or maintaining a new web browser, or how dependent are all firefox forks (or older, harder derivatives like SeaMonkey) of Mozilla (both Firefox and Gecko).
I'm not trying to get to any point with this text, but rather to highlight that now is the time to have a few conversations around open standards, and in particular web standards. And as it happens, the "annual day" to have discussions of that sort is around the corner: @dff@dff's Document Freedom Day 2025 is already in the 26th of this month. So why aren't there more events on the map? How is your community, user group, etc. going to mark and celebrate this day?
Organize something, and put it on the events map, right this way: https://digitalfreedoms.org/en/dfd
Still, it is important to acknowledge what is and has been going on - how a web browser currently became a lot more than just a piece of software implementing a number of open standards, how they are all basically based over one of two existing browser agents (Gecko and Webkit) with the emergence of two upcoming ones (Servo and LibWeb); the difficulties of creating or maintaining a new web browser, or how dependent are all firefox forks (or older, harder derivatives like SeaMonkey) of Mozilla (both Firefox and Gecko).
I'm not trying to get to any point with this text, but rather to highlight that now is the time to have a few conversations around open standards, and in particular web standards. And as it happens, the "annual day" to have discussions of that sort is around the corner: @dff@dff's Document Freedom Day 2025 is already in the 26th of this month. So why aren't there more events on the map? How is your community, user group, etc. going to mark and celebrate this day?
Organize something, and put it on the events map, right this way: https://digitalfreedoms.org/en/dfd
Forest animals also have to do the laundry, they even have a proper clotheshorse! See: https://lyse.isobeef.org/wanderung-zu-den-schurrenhoffuechsen-2021-05-15/07.jpg :-D
Having said that, it appears that this only affects me personally, noone else. I don't know of any other client that saves read statuses. But don't worry about me, all good. Just keep doing what you've done so far. I wanted to mention that only for the sake of completeness. :-)
i just had no strength today. the work still hasn't stopped or slowed down and my son had a sleep over last night. got it done but just drained. now gotta get donuts for the kids.
#running
i just had no strength today. the work still hasn't stopped or slowed down and my son had a sleep over last night. got it done but just drained. now gotta get donuts for the kids.
#running
i just had no strength today. the work still hasn't stopped or slowed down and my son had a sleep over last night. got it done but just drained. now gotta get donuts for the kids.
#running
In all reality, though, I don't see that our community will come to an agreement. Some folks just don't want to give up on the content-based addressing scheme.
#<Alice https://example.com/twtxt.com#2024-12-18T14:18:26+01:00>Hashes are not a problem on PHP, I dont know why it's slow to calculate them from your side, but I agree with your points.
BTW, did you have the chance to read my proposal on twtxt 2.0? I shared a few ideas about possible improvements to discuss:
https://text.eapl.mx/a-few-ideas-for-a-next-twtxt-version
https://text.eapl.mx/reply-to-lyse-about-twtxt