… aaaaaaand it’s over.
@prologic@twtxt.net Our media still shows a theoretical chance for Harris. 😬
@lyse@lyse.isobeef.org Great shots indeed! 👌 The return of Slenderman. :-)
Oh, since @falsifian@www.falsifian.org mentioned it: I think I’m gonna steal this:
a{cursor:zoom-in}
😅
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. 🤔
@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.)
Tried to get a Covid booster, lady at the phone told me: “Nah, fuck off, you’re too young.” 🥴
@bender@twtxt.net I’m so deeply concerned we even have to discuss the orange clown. 😩 All voodoo dolls up and running. ✅
Funny wobbly moon sets:
https://movq.de/v/4bba078992/moon1.ff.jpg
I also tried to do a little stacked thingy, not too happy with it:
$thing
, check my status!” Okay, fine, I open that and it shows a photo.
@prologic@twtxt.net Lol, people with poor vision are properly fucked in that app. 🫤
@doesnm@doesnm.p.psf.lt If I’ve learned one thing over the years: If there is a feature, people will use it. No matter what. 😂
@lyse@lyse.isobeef.org I’ll be happy to wait until the show finishes. Just get me off this planet! 😂 https://movq.de/v/96d00c53b5/borg.png
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! 😂
@lyse@lyse.isobeef.org It was pretty obviously man-made. Or … creature-made. 😏 Who knows, maybe it was aliens! But why didn’t they take me with them? 😩
Too irregular for a lightshow. Must be cars. Damn, I wish I could tape this. 😅
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:
- A ship on the nearby river with a lightshow going. It’s rare but it happens.
- 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.
@lyse@lyse.isobeef.org I … I can’t … what? 😅
@bender@twtxt.net Oh noooooo! 😱 Poor you. 😅
@bender@twtxt.net … well, we had people lighting fireworks and bangers. 😂
@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.
@doesnm@doesnm.p.psf.lt Yeah, wow, that’s tough. But it’s good to know that the headercache helps. 👍
@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. 🫤
@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? 😅
@bender@twtxt.net Somehow I’m too lazy for a Mastodon client. 😂
@bender@twtxt.net Uhh, I don’t remember. 😂 I don’t think so?
[…] and then manually push it to my web servers […]
Funny, I also push manually, kind of. Mypublish_command
includes a[Y/n]
question and I very often hitn
, 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 …
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
@asquare@asquare.srht.site As far as jenny is concerned, it’ll create a thread. 😅 https://movq.de/v/207254756a/s.png
That was a nice 12km walk today. Got home just in time before all the Halloweenies got out. 😅
@rrraksamam@twtxt.net The world news? Better not do that. 🤣
@xuu Yep, I’ll be doing it as well. The plan is to use Java 1 on OS/2 Warp 4: https://tilde.zone/@movq/113114730253242098
The private leaderboard from last year should still work.
@lyse@lyse.isobeef.org Ha! 😄
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? 🤨
@johanbove@johanbove.info Taste all the flavors all at once. 😅
@eldersnake@we.loveprivacy.club I’m happy about any open platform that allows us to not use closed/commercial services. ✌️
@sorenpeter@darch.dk WeeChat in a detachable tmux session. No mobile stuff, I hate typing on a phone with a passion. 🥴
@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 … 🤷
@lyse@lyse.isobeef.org Oof! That’s impressive. (And what an interesting mask that is.)
(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. 😂)
This should be fixed in Git. ✅
301 Moved Permanently
redirect(s) for https://dev.twtxt.net/ and all relevant pages to the new domain https://twtxt.dev 👌
@prologic@twtxt.net Alrighty, I replaced the links in the jenny repo. 👍
# nick
as a sort of "identifier". This gets us out of this mess of when feeds move locations or authors decide to host on 3 or 4 different protocols 🤣 Downside? Something picks the same nick? (they'll still hash differently, so that's fine).
@lyse@lyse.isobeef.org Guilty as charged. 😂
@prologic@twtxt.net LGTM. 👍
@lyse@lyse.isobeef.org Better Nate than lever …
@prologic@twtxt.net I haven’t changed anything, either. 😅 jenny uses the first URL: https://www.uninformativ.de/git/jenny/file/jenny.html#l191
@prologic@twtxt.net Yes. 😅
@prologic@twtxt.net Oh, yeah, it certainly is more work for you than it is for me. 🫤
@prologic@twtxt.net As per https://dev.twtxt.net/doc/metadataextension.html, it’s the first URL. 😅 I think using the last URL was one of the new proposals. Or has that already been implemented? 🤯
@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. 🤔
@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.
@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. 🤔
@bender@twtxt.net That broken mention might have the same cause as the other issue you mentioned. Changed URL and all that. 🤔