@aelaraji@aelaraji.com I figure it will be the same as those on a tilde server, right? Try https://tilde.town/ !

@aelaraji@aelaraji.com LOL. You got me! :-D

@aelaraji@aelaraji.com yeah, but he is shacking his finger at you for your use of markdown, and emoji. :-)

PHP uses \t as well for TABs.

@sorenpeter@darch.dk oh, I thought we were settled on TABs for a while now, weren’t we? 🤔 The new website mentions TABs too. The command echo -e (on any shell?) will use \t for them.

@lyse@lyse.isobeef.org what are you building now? The things you are mentioning I couldn’t even start wrapping my head around them! 😅 They sure sound expensive, tough.

Thanks @david@collantes.us, good to know, but we need to agree on what character we use, otherwise the hashes will not be the same:)

@sorenpeter@darch.dk a TAB is simply \t. Just add it to that echo line, and that’s it.

Oh boy, I’m looking for trapezoidal (like ACME thread) screws and nuts in left hand form. The rods are already expensive, but nuts feel like a total ripoff. A hex nut for Tr20x2 being 30mm long and 30mm in “diameter” costs me 22 bucks! O_o Just a single one, made of regular steel. A meter of rod is 21€. The more common Tr20x4 hex nut is just 7€ and the rod 17€, but 4mm pitch is a bit much for a leadscrew for semi-precision work I reckon.

Well, maybe I just use metric threads. I will sleep on this.

@prologic@twtxt.net from IRC:

“Hashes will increase then, and will use SHA256 instead? That is the end result of weeks long discussions, correct?”

@lyse@lyse.isobeef.org Maybe you’re right: Let’s pause this while edit/delete discussions.

@mckinley@twtxt.net they are fighting to make more money. Seeing it any other way is rather naïve.

Context for those who don’t know: Epic Games is the company behind the hugely popular video game Fortnite. As far as I know, the core game is still free-to-play and supported by microtransactions. It’s available on Windows, consoles, and mobile platforms. They sued Apple a few years ago because they felt the 30% cut Apple takes for in-app purchases was unreasonable and that they should be allowed to distribute their software independently of the App Store. It didn’t turn out so well for them. https://en.wikipedia.org/wiki/Epic_Games_v._Apple

@prologic@twtxt.net That can only work if I happen to have the original one as well. But what are the odds for that? Quite low I’d say. It’s rare that I see a once working thread to be cactus later on. Usually, when I arrive, police already broke up the party. Yarnd might be more lucky in that it constantly pulls, but I don’t.

Anyway, I won’t implement that in my client. Sounds too much effort for the tiny gain.

@slashdot@feeds.twtxt.net They must have spent such an ungodly amount in legal fees by now that I wonder if they’ll come out of this in the green if they get to keep all the money from in-app purchases. Don’t get me wrong, I’m glad they’re doing it, but I think there’s a reason why Epic Games is the only one fighting for app store neutrality.

Ta, @movq@www.uninformativ.de and @bender@twtxt.net! No, that is Wäschenbeuren: https://en.wikipedia.org/wiki/W%C3%A4schenbeuren My town is in the opposite direction.

And yes, it literally took hours to remove 90% of the photos. It’s the necessary evil. I’m never looking forward to the sorting process. The longer the hike, the worse the aftermath.

We had 3°C the other night, quite cold. That’s the price to pay for the nice temperatures at daytime.

@aelaraji@aelaraji.com You could just remove the {getuser()} part because you added ~.

@doesnm@doesnm.p.psf.lt 👌

Understand, ok seems i should leave gemini untouched

@bender@twtxt.net Good point! 👌 I’ll make it so 👌

@prologic@twtxt.net yup, it was muted. I didn’t do it purposely, though. I truly don’t know how that happened. That beget the question, shouldn’t that be disallowed? That is, muting ourselves should not be possible. That same for following/blocking ourselves (if that breaks functionality).

@doesnm@doesnm.p.psf.lt No.

iirc in twtxt v2 it starts prohibited

This is not true. There are no issues supporting fetching feeds via Gemini/Gopher. This is totally fine. What will likely happen is “recommendations” and “drawbacks of using Gemini/Gopher”

I mean thread command but bash escapes quoted as command…

Ok, i know how to command working (not sure), but seems it only grab from cache. Maybe make fetch from twtxt.net if hash not found?

@prologic@twtxt.net Regarding the new way of generating twt-hashes, to me it makes more sense to use tabs as separator instead of spaces, since the you can just copy/past a line directly from a twtxt-file that already go a tab between timestamp and message. But tabs might be hard to “type” when you are in a terminal, since it will activate autocomplete…🤔

Another thing, it seems that you sugget we only use the domain in the hash-creation and not the full path to the twtxt.txt

$ echo -e "https://example.com 2024-09-29T13:30:00Z Hello World!" | sha256sum - | awk '{ print $1 }' | base64 | head -c 12

should i delete gemini support from twet? iirc in twtxt v2 it starts prohibited. And all of my fields are https

Really you stopped 22hrs ago? https://twtxt.net/twt/iaautmq

Hmm da fuq?! @tiktok@feeds.twtxt.net ?

@bender@twtxt.net I see it here hmm 🤔 Dis you accidentally mute your own Twt?

@doesnm@doesnm.p.psf.lt me too! 🤭 (kidding, kidding!)

No, im just crazy (joke)

@off_grid_living@twtxt.net mind sharing the PDF, to take a look? Some PDF containing text as images, which makes it more difficult to complete the task you want to perform.

@doesnm@doesnm.p.psf.lt am I understanding correctly that you do not have a desktop/laptop computer, but a pocket Android based one?

Lol, good but why why not /data/data/com.termux/files/usr/tmp?

Rightfully so, @xuu@txt.sour.is pod has it on cache: https://txt.sour.is/twt/v6eemvq. This pod (twtxt.net), knows nothing about it, so it seems.

I don’t see it on the client (Yarn), but as you can see it is on the raw feed. 🧐

@prologic@twtxt.net I wonder where did this one went to:

2024-09-29T12:08:15Z	 @<lyse https://lyse.isobeef.org/twtxt.txt> love 27! Is that your town as seeing from the mountain, or some other town? From 395 to 40 is quite some picking! I figure that’s the most difficult part, right?

Ah, 16°C… what dreams are made of! 😍

@movq@www.uninformativ.de Hmmm 🤔 Intuitively I say “No they’re not the same”; but let me sleep on it 🙏😴

@prologic@twtxt.net If I understand correctly, then this means that twt hashes no longer uniquely refer to one specific twt. When someone talks about #1234567, it could refer to the original or some edit of it. It is up to clients to find out what this hash could mean (by keeping a historical database of all feed versions, basically).

Isn’t this essentially the same as only including url and timestamp in the hash?

@bender@twtxt.net Just once I tell ya:

Ah, 16°C… what dreams are made of! 😍

I’d like it to be a nice cool 16°C here 🤣

@lyse@lyse.isobeef.org love 27! Is that your town as seeing from the mountain, or some other town? From 395 to 40 is quite some picking! I figure that’s the most difficult part, right?

Ah, 16°C… what dreams are made of! 😍

@lyse@lyse.isobeef.org The view from the top of the “mountains” never gets old. 😊

Personally I don’t see it as a problem. I didn’t even really see edits as a problem either tbh, but this is just an incremental improvement I think.

It’s no worse than what we have now, it’s better. But yes caveats still apply.

@movq@www.uninformativ.de Yup.

@prologic@twtxt.net So this hinges on clients keeping a history of the twt hashes. Clients that clean their cache or simply start following a feed later on have no way of reconstructing older twt hash versions and thus no way of reconstructing existing threads. Right?

@slashdot@feeds.twtxt.net No 😅

@doesnm@doesnm.p.psf.lt I think it’s a good idea to fork twet and continue to improve it. It’s an “okay” Twtxt cli client, but it needs a bit more work 👌

@doesnm@doesnm.p.psf.lt Sorry I meant twet 🤦‍♂️