movq

uninformativ.de

No description provided.

Recent twts from movq
In-reply-to » @darch I kind of agree that we can probably omit the nick part in mentions entirely. Since they can be looked up and cached, there's no need for this. But we'll have to spec this all up. First let's see what @lyse and @movq and others like @anth thing about finally formalising a standard way to lookup feed URI(s) and define a slightly more saner? @-mention syntax/usage pattern. I for one hate manually typing out (for example) @<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch 😅

@darch@neotxt.dk Hmmm … if the argument is “not all twtxt files have all required fields”, then wouldn’t this also apply to webfinger? Not all servers that host a twtxt file will also serve webfinger info. 🤔 You’d probably always have to implement some fallback mechanism.

I don’t really know anything about “indieweb”, though. I’ll have to read up on that first. 😅

⤋ Read More
In-reply-to » @darch I kind of agree that we can probably omit the nick part in mentions entirely. Since they can be looked up and cached, there's no need for this. But we'll have to spec this all up. First let's see what @lyse and @movq and others like @anth thing about finally formalising a standard way to lookup feed URI(s) and define a slightly more saner? @-mention syntax/usage pattern. I for one hate manually typing out (for example) @<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch 😅

@prologic@twtxt.net Alright, buuuut … what do we gain from that?

You could do almost the same thing currently with just the feed URL. nick = can be read from metadata. The canonical feed URL used for twt hashing is well-defined, too (first url = in metadata).

Sorry if I’m being too dumb. 😅

⤋ Read More
In-reply-to » @darch I kind of agree that we can probably omit the nick part in mentions entirely. Since they can be looked up and cached, there's no need for this. But we'll have to spec this all up. First let's see what @lyse and @movq and others like @anth thing about finally formalising a standard way to lookup feed URI(s) and define a slightly more saner? @-mention syntax/usage pattern. I for one hate manually typing out (for example) @<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch 😅

@prologic@twtxt.net Hmmm.

So you’re suggesting to make prologic@twtxt.net the “primary identifier” of a user, right? That’s the string that I would configure in my twtxt client when I want to follow someone. Then when my client fetches the feed, it first does a webfinger lookup to find the feed URL and the nickname. (Or maybe this only immediately after adding the user to my client and then maybe update it every now and then.)

Did I understand correctly so far? 😅

⤋ Read More
In-reply-to » @darch I kind of agree that we can probably omit the nick part in mentions entirely. Since they can be looked up and cached, there's no need for this. But we'll have to spec this all up. First let's see what @lyse and @movq and others like @anth thing about finally formalising a standard way to lookup feed URI(s) and define a slightly more saner? @-mention syntax/usage pattern. I for one hate manually typing out (for example) @<darch https://neotxt.dk/user/darch/twtxt.txt> like this @darch 😅

@prologic@twtxt.net I’m not really sure what you mean. Don’t we already have nick = and url = in the metadata section? Which problem are we trying to solve? 🤔

⤋ Read More
In-reply-to » I currently have 153 browser tabs open so maybe my resolution for 2023 is to reduce that.

@abucci@anthony.buc.ci I don’t. 😅 I might accumulate quite a lot of tabs throughout the day (especially at work), but eventually, meh, hardly any of them matter. If something really is important, I store a link at the appropriate place. Let’s say some web site is relevant to a bit of code I’m writing, then it ends up as a comment in said code …

Other than that, I have a bookmarks file with stuff I’m regularly visiting.

And that’s it.

Which brings me to the important question: What are those 153 tabs of yours? 😅

⤋ Read More
In-reply-to » Fuck me, how awesome was this sunset!? Fantastic end of the year, no fireworks can keep up this night, that's for sure. Well, fireworks is very lame in my opinion anyways.

@lyse@lyse.isobeef.org Fireworks sure do look nice, though. 😅 I’m surprised that you managed to take such good shots – it’s pretty finnicky to get the exposure right, IIRC. (I guess your camera had good auto-settings here.)

We were watching from our balcony. Well, not the balcony actually, we were behind the windows. You can’t watch fireworks from the balcony of a (small-ish) tower building, because the rockets will explode right in your face. 🧨

Where I live, it has actually gotten a bit better. Before Covid, people were shooting fireworks like maniacs. Then in 2020 there were basically no fireworks (I think there were restrictions back then), which was a little strange, but very relaxing. In 2021, some fireworks got replaced by laser shows – pretty cool! And this year we’re back to standard fireworks again – but not to the pre-Covid extent. They stopped sooner and I hardly remember any bombs going off today (January 1st).

⤋ Read More
In-reply-to » Finished Advent of Code and rejoined the private leaderboards out of curiosity -- only to find out that the other people stopped doing the puzzles halfway through. 🥴

Summary of the event: gopher://uninformativ.de/0/phlog/2022-12/2022-12-25–advent-of-code-2022.txt

⤋ Read More