@falsifian@www.falsifian.org Yeah I agree with this actually (introducing too many changes at once is often a bad idead):
but IMO that shouldn’t be done at the same time as introducing new untested ideas
@bender@twtxt.net Bahahahahahahaha 🤣
This is why we need “authenticity” 🤣 Yes if you copied my feed’s UUID, then you’d end up generating identical hashes to me if we posted at identical times with identical timestamps. Not good 😌
Also, was the dot after the timestamp intended?
No, sorry.
@bender@twtxt.net It’s the experience of an ordinary person in a strange place where memories are disappearing with the help of the Memory Police. The setting feels contemporary (to the book’s 1994 publication date) rather than futuristic, except for some unexplained stuff about memories.
@prologic@twtxt.net what if I copy your uuid, and use it on my feed? What happens then? Also, was the dot after the timestamp intended?
Yes, that is exactly what I meant. I like that collection and “twtxt v2” feels like a departure.
Maybe there’s an advantage to grouping it into one spec, but IMO that shouldn’t be done at the same time as introducing new untested ideas.
See https://yarn.social (especially this section: https://yarn.social/#self-host) – It really doesn’t get much simpler than this 🤣
Again, I like this existing simplicity. (I would even argue you don’t need the metadata.)
That page says “For the best experience your client should also support some of the Twtxt Extensions…” but it is clear you don’t need to. I would like it to stay that way, and publishing a big long spec and calling it “twtxt v2” feels like a departure from that. (I think the content of the document is valuable; I’m just carping about how it’s being presented.)
@falsifian@www.falsifian.org “The Memory Police” sounds like an interesting title. What is it about, if you don’t mind? Even a brief sentence would suffice. Thanks!
For example a v2 spec might just simply mandate the following as a starting point:
cat <<EOF
# nick = $USER
# avatar = https://example.com/$USER.png
# description = Hi 👋 I'm Bob!
# uuid = 7E9BC039-4969-4296-9920-4BACDBA8ED5C
2024-09-28T11:19:25+10:00 Hello World!
EOF > ~/public_html/twtxt.txt
And:
Content-type: text/plain; charset=utf-8@falsifian@www.falsifian.org I don’t have a problem with continuing the way we have been for the past ~4 years, little extensions and improvements that we try along the way. That has worked quite well 💪 As a blind person myself, I can totally empathise with reading a full (lots of text) spec. Even if we decide to combine all the ideas into a full fleshed out v2 spec, it might be worthwhile having a cut-down version that is as simple as it can be a no less.
Recent #fiction #scifi #reading:
The Memory Police by Yōko Ogawa. Lovely writing. Very understated; reminded me of Kazuo Ishiguro. Sort of like Nineteen Eighty-Four but not. (I first heard it recommended in comparison to that work.)
Subcutanean by Aaron Reed; https://subcutanean.textories.com/ . Every copy of the book is different, which is a cool idea. I read two of them (one from the library, actually not different from the other printed copies, and one personalized e-book). I don’t read much horror so managed to be a little creeped out by it, which was fun.
The Wind from Nowhere, a 1962 novel by J. G. Ballard. A random pick from the sci-fi section; I think I picked it up because it made me imagine some weird 4-dimensional effect (“from nowhere” meaning not in a normal direction) but actually (spoiler) it was just about a lot of wind for no reason. The book was moderately entertaining but there was nothing special about it.
Currently reading Scale by Greg Egan and Inversion by Aric McBay.
Deprecating non-UTC times seems reasonable to me, though.) Having a big long “twtxt v2” document seems less inviting to people looking for something simple. (@prologic@twtxt.net you mentioned an anonymous comment “you’ve ruined twtxt” and while I don’t completely agree with that commenter’s sentiment, I would feel like twtxt had lost something if it moved away from having a super-simple core
See https://yarn.social (especially this section: https://yarn.social/#self-host) – It really doesn’t get much simpler than this 🤣
@falsifian@www.falsifian.org We’ve been doing this for years:
There are lots of great ideas here! Is there a benefit to putting them all into one document? Seems to me this could more easily be a bunch of separate efforts that can progress at their own pace:
More thoughts about changes to twtxt (as if we haven’t had enough thoughts):
1a. Better and longer hashes.
1b. New possibly-controversial ideas like edit: and delete: and location-based references as an alternative to hashes.
1c. Best practices, e.g. Content-Type: text/plain; charset=utf-8
1d. Stuff already described at dev.twtxt.net that doesn’t need any changes.
We won’t know what will and won’t work until we try them. So I’m inclined to think of this as a bunch of draft ideas. Maybe later when we’ve seen it play out it could make sense to define a group of recommended twtxt extensions and give them a name.
Another reason for 1 (above) is: I like the current situation where all you need to get started is these two short and simple documents:
https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html
https://twtxt.readthedocs.io/en/latest/user/discoverability.html
and everything else is an extension for anyone interested. (Deprecating non-UTC times seems reasonable to me, though.) Having a big long “twtxt v2” document seems less inviting to people looking for something simple. (@prologic@twtxt.net you mentioned an anonymous comment “you’ve ruined twtxt” and while I don’t completely agree with that commenter’s sentiment, I would feel like twtxt had lost something if it moved away from having a super-simple core.)
All that being said, these are just my opinions, and I’m not doing the work of writing software or drafting proposals. Maybe I will at some point, but until then, if you’re actually implementing things, you’re in charge of what you decide to make, and I’m grateful for the work.
@bender@twtxt.net I’m not following it, but someone on my pod is 🤣 And yes based on statistical evidence, I doubt you’ll see a reply either 🤣
@prologic@twtxt.net it was discovered because aelaraji engaged with it. I don’t think you will see a reply. 😩
@doesnm@doesnm.p.psf.lt The useragent tool now natively supports the Caddy (JSON) logfile format. 🥳
@prologic@twtxt.net Done. Also, I went ahead and made two changes: changed hexadecimal to base64 for hashes (wasn’t sure if anyone objected), and changed “MUST follow the chain” to “SHOULD follow the chain.
This is a 1-way feed by the looks 🤣 Maybe someone can figure out how to reach out to this person and see if they’re aware and interested in something a bit more “social” (albeit slow) 🤣
@falsifian@www.falsifian.org Sorry I didn’t make that super clear 🤦♂️ Be happy to see you there and some new folks 🙇♂️
🥳 NEW FEED: @3r1c@3r1c.net
@prologic@twtxt.net Thanks for pointing out it lasts four hours. That’s a big window! I wonder when most people will be on. I might aim for halfway through unless I hear otherwise. (12:00Z is a bit early for me.)
This Facebook/Meta story on storing passwords in plain text it just wow 😮 – Like how da fuq does a company, or anyone for that matter in the business of software / technology even do this?! Like at least base64 encode the fuckers right?! (oh wait 🤦♂️)
yarnd hwoever:
@xuu If you have time, could you help me pinpoint this bug? 🐛
@lyse@lyse.isobeef.org It’s from 12pm to 4pm UTC so if you can make it at all, that’d be great 👍
@xuu Do you think we should just detect edits at the client-level then? 🤔
Probably the best idea I’ve heard/seen si far is @anth@a.9srv.net’s idea of a feed having a uuid # uuid = (if present) otherwise just falling back to the URL you fetched it from and dropping the idea of a feed # url = entirely.
@lyse@lyse.isobeef.org Yup you’re right, it’s s terrible idea 💡
Well the poll clearly shows:
And an NPS score of 7/10 🤣
@bender@twtxt.net Zero technical issues 🤣 I never claims otherwise 😅
Definitely NOT editing that Oupsie… + It looks all the same in terminal, so I can live with it.🤣
@prologic@twtxt.net do you think that, I don’t know, but maybe(?), Gopher/Gemini feeds might lack, pffff, I don’t know, any mechanisms for discovery…. and caching?!?! 🤣
@aelaraji@aelaraji.com LOL. For lyse’s sake (and everybody else’s), let’s not! 😂😂😂
”@bender I am also in camp no edit signals. deletes only breaks the head of a thread. all the replies are unaffected.”
I figure I could also answer every single twtxt like this, so that if the original gets edited, or deleted, at least I don’t sound foolish without knowing exactly what I replied to. 🤭
It Sounds like a good idea! should that be limited to just direct replays or can it be extended to replays to other replays, that way and With just the right amount of chain-replays, we’ll be RRrrrrrevolutionizing the way people Mailing Lists like, in no time! xD
P.S: Just a reminder! I’ve already told you not to mind my twts for the next couple of hours, right!
@aelaraji@aelaraji.com @bender@twtxt.net Bwahahahaa, brilliant! :‘-D
@bender@twtxt.net HAHA I’ve just bookmarked that Repo to go through it tomorrow 👌
@xuu wrote:
”@bender I am also in camp no edit signals. deletes only breaks the head of a thread. all the replies are unaffected.”
I figure I could also answer every single twtxt like this, so that if the original gets edited, or deleted, at least I don’t sound foolish without knowing exactly what I replied to. 🤭
@aelaraji@aelaraji.com LOL, now that’s rich! Hahahaha!
@xuu@txt.sour.is what do we want then? Just up the hash size to avoid collisions? I figure that’s easy. It’s going to be a short call tomorrow then. 😂🥳
@bender@twtxt.net I am also in camp no edit signals. deletes only breaks the head of a thread. all the replies are unaffected.
See!? Even Meta/Facebook uses plain text, not just Twtxt! 🤣
@aelaraji@aelaraji.com it is just plain text. :-) Up for the challenge? Convert this: https://github.com/coignard/weblog, to shell!
@3r1c@3r1c.net Woa! I love this blog’s format! _ it’s just perfect for reading from terminal…
@lyse@lyse.isobeef.org that sounds truly idyllic! 🤭
@lyse@lyse.isobeef.org HAHA Nice one!
@bender@twtxt.net Well Matt should definitely get better Lawyers/PR people who could slap em’ on the wrest and tell “NO!” before he does something childish and effs things up. As for WPE, I believe a billion dollar company should be able to afford investing in their own infrastructure, hosting their resources, deploying their own CDNs and what not instead of leaching on Wordpress (’s infrastructure) for free (as in free coffee) + The Stripe thing they did is so disgusting given the circumstances, I don’t even want to talk about it.
Things could/should’ve been handled better, now it’s just another sh…rimp show.
@bender@twtxt.net Hahaha, I had to look this idiom up, but you’re spot on. :-D
@lyse@lyse.isobeef.org in other words, you will take a hike. :-D
I heard a funny saying today: Democracy is when three foxes and a bunny decide what to have for dinner.