movq

www.uninformativ.de

No description provided.

Recent twts from movq

@rrraksamam@twtxt.net

Even the Tech news doesn’t grab my attention anymore

I noticed that as well about me. I stopped reading big and popular news outlets long ago. Maybe it’s because I’m getting old or maybe it’s because the 73128937189th article about blockchain (or “AI” these days) just isn’t interesting anymore. 🤔

⤋ Read More
In-reply-to » Tried to get a Covid booster, lady at the phone told me: “Nah, fuck off, you’re too young.” 🥴

@prologic@twtxt.net Well, she didn’t use those exact words, but since I’m under 60 years old and not in a “risk group” either, she didn’t want to give me an appointment. 🤪

Getting Covid shots is ridiculous here in Germany. Not once have I gotten a shot from my GP. Every time I had to hunt down some doctor who’s willing to do it. It’s almost like a black market …

(Okay, granted, in that one year, there was an official vaccination campaign and there was an official vaccination center where you could go.)

⤋ Read More
In-reply-to » Alright. I am---actually, "we" are---out for the next couple of days. Do me a favour and stick some needles on that orange voodoo doll you got---make one, if you don't!

@bender@twtxt.net I’m so deeply concerned we even have to discuss the orange clown. 😩 All voodoo dolls up and running. ✅

⤋ Read More

So, I’m forced to use WhatsApp now. Someone told me: “Hey, I’ve been doing $thing, check my status!” Okay, fine, I open that and it shows a photo.

Then, while looking at that photo, it’s suddenly gone. No, not gone – there are several photos and it switched automatically to the next one. The timeout appears to be four seconds.

JFC, I’m getting too old for this. Let me look at the damn photo! Don’t rush me! 😂

⤋ Read More

I’m seeing strange lights in the sky. None of my cameras are sensitive enough to make a video.

It’s probably one of two things:

  1. A ship on the nearby river with a lightshow going. It’s rare but it happens.
  2. A steap hill nearby, cars driving “upwards”, and since super bright LED lights are normal nowadays, they reflect from the clouds.

Either way, looks fancy.

⤋ Read More
In-reply-to » That was a nice 12km walk today. Got home just in time before all the Halloweenies got out. 😅

@lyse@lyse.isobeef.org Honestly, I feel horrible today. 😂 I had to pump lots of cold air through my lungs yesterday because I walked so fast – and now I feel like having a cold. 🤒 Like that cold air did some minor damage in there … (I have no idea if it really works like that.)

I’ll certainly test for Covid before meeting people tomorrow.

⤋ Read More
In-reply-to » I need to wait 30 seconds every start of mutt with 8 feeds

@doesnm@doesnm.p.psf.lt May I ask which hardware you have? SSD or HDD? How much RAM?

I might be spoiled and very privileged here. Even though my PC is almost 12 years old now, it does have an SSD and tons of RAM (i.e., lots of I/O cache), so starting mutt and opening the mailbox takes about 1-2 seconds here. I hardly even notice it. But I understand that not everybody has fast machines like that. 🫤

⤋ Read More
In-reply-to » Tried migrating to jenny... So seems it not suitable for my phone. Fetch command fetched archived feeds so i have 37k+ entries and mutt hangs for several seconds for loading this. Also i don't like hardcoded paths for config and follow file

@bender@twtxt.net Right, it fetches archived feeds on the first run (because it wants to grab all twts from that feed). Later on, it keeps track of the last seen twt hash per feed – if it cannot find that hash anymore, then it concludes that the feed must have been rotated/archived, so it fetches some/all archived feeds again until it finds that twt hash. Easy, right? 😅

⤋ Read More

@falsifian@www.falsifian.org

[…] and then manually push it to my web servers […]

Funny, I also push manually, kind of. My publish_command includes a [Y/n] question and I very often hit n, so I can keep writing a thread until it’s finished. And sometimes I delete stuff again and never publish it. 😅

I use Mastodon similarly. I write posts in Vim until I’m happy with them. Then copy-and-paste to the browser …

⤋ Read More
In-reply-to » That was a nice 12km walk today. Got home just in time before all the Halloweenies got out. 😅

And that means I’m back to 50km+ per month after the summer break.

2023-10    81 km  in 20 tracks
2023-11   100 km  in 23 tracks
2023-12    76 km  in 21 tracks
2024-01    59 km  in 20 tracks
2024-02    48 km  in 12 tracks
2024-03    65 km  in 16 tracks
2024-04    55 km  in 12 tracks
2024-05    58 km  in 20 tracks
2024-06    34 km  in 19 tracks
2024-07    25 km  in  6 tracks
2024-08    18 km  in  5 tracks
2024-09    52 km  in 14 tracks
2024-10    74 km  in 17 tracks

⤋ Read More

That is weird, though:

Is Loops open source?

It will be! We plan on open sourcing the platform after it reaches a stable and easy to maintain state.

Why the delay? 🤨

⤋ Read More
In-reply-to » My very strong opinion on the use of Twtxt is if you intend to use it, you should be prepared to let people pull your feed or at least check it and regular rentals.

@prologic@twtxt.net Yeah, that’s what I don’t understand about this behavior. Once you put up a web server on the internet, you’ll be hit by so many bots instantly – the few hits on my twtxt file hardly matter … 🤷

⤋ Read More
In-reply-to » There might be a bug in jenny that causes it to re-fetch archived feeds on every run. Probably happens on edits/deletes. I’ll look into it soon-ish.

(I screwed up the commit message and force-pushed a fix after checking the web server logs. I hope I didn’t break anybody’s repo. 😂)

⤋ Read More
In-reply-to » After the behaviour of a clearly very angry feed author over the past few days, I'm very tempted to give up on Twtxt and allow it to go back to being dead. What really is the point of building and supporting a way to exchange little pieces of text with one another in a completely decentralized way, if you're just going to keep bumping up against such hostility? I don't know why I do this anymore.

@prologic@twtxt.net Yes. 😅

⤋ Read More
In-reply-to » After the behaviour of a clearly very angry feed author over the past few days, I'm very tempted to give up on Twtxt and allow it to go back to being dead. What really is the point of building and supporting a way to exchange little pieces of text with one another in a completely decentralized way, if you're just going to keep bumping up against such hostility? I don't know why I do this anymore.

@prologic@twtxt.net Oh, yeah, it certainly is more work for you than it is for me. 🫤

⤋ Read More
In-reply-to » After the behaviour of a clearly very angry feed author over the past few days, I'm very tempted to give up on Twtxt and allow it to go back to being dead. What really is the point of building and supporting a way to exchange little pieces of text with one another in a completely decentralized way, if you're just going to keep bumping up against such hostility? I don't know why I do this anymore.

@prologic@twtxt.net I don’t understand that behavior either, but I’m afraid stuff like that is always going to happen. (I think it already happened once in the past?) As long as we have an easy way to ignore such a feed and remove it from our databases, we should be fine. 🤔

⤋ Read More
In-reply-to » Simplified twtxt - I want to suggest some dogmas or commandments for twtxt, from where we can work our way back to how to implement different feature like replies/treads:

@sorenpeter@darch.dk As a replacement, it should be doable. But it won’t work together with hashes. So the community has to agree on one or the other first.

⤋ Read More
In-reply-to » @movq, having an issue fetching a twtxt context. I am getting:

@prologic@twtxt.net I’m not sure this isn’t a bug. The feed’s URL must have changed at some point but Yarn is still using the old URL for hashing. And it’s inconsistent now:

curl -s -H 'Accept: application/json' https://twtxt.net/twt/mowsvgq

This gets you a twt which, when hashed again now using all the information from that API reply, does not yield the hash mowsvgq but bjs6aua.

But when you use the URL http://prismdragon.net/twtxt.txt for hashing instead of http://twtxt.prismdragon.net/twtxt.txt, it’s mowsvgq.

So I would expect Yarn to either know about mowsvgq (showing the new URL http://prismdragon.net/twtxt.txt) or about bjs6aua (showing the old URL http://twtxt.prismdragon.net/twtxt.txt). But not mowsvgq with the old URL. 😅

I don’t see how the second # url = metadata field is relevant here. 🤔

⤋ Read More