lyse

lyse.isobeef.org

No description provided.

In-reply-to » (#j7i6yra) Yeah, @eapl.me, I kinda like file extensions in some situations. What do you think of twtxt.exe, @bender? ]:->

@eapl.me@eapl.me @bender@twtxt.net @skinshafi@thunix.net The feed that nobody follows out of fear.

When I started programming in Delphi, I always included all the files (not only the *.exe, but also *.pas and what else there was) when giving friends my programs on floppy disks. I didn’t know that the executable was technically enough. :-)

​ Read More
In-reply-to » Imagine if all computer UIs would act like the UI from my NAS system... I feel I need to be waiting for output from the machine like it's 1973.

Yeah, @movq@www.uninformativ.de! “Sorry boss, I accidentally removed the bug report, because the button suddenly materialized under my cursor.” :-D

Luckily, I do not have to deal with that UI from hell for three and a half weeks very soon.

​ Read More
In-reply-to » Imagine if all computer UIs would act like the UI from my NAS system... I feel I need to be waiting for output from the machine like it's 1973.

I hear you, @movq@www.uninformativ.de! I have to wait five seconds after opening any Jira ticket before the JS garbage has eventually fetched all the other information and rebuilt the DOM. Only then I can actually begin to scroll down to the information I’m after. Every fucking time.

​ Read More
In-reply-to » Finally, the message rendering in my tt Go rewrite produces some colors. There is definitely a lot more tweaking necessary. But this is a first step in the right direction.

Thank you @bender@twtxt.net and @movq@www.uninformativ.de!

I partially fixed the code block rendering. With some terrible hacks, though. :-( I see that empty lines in code block still need some more work. There are also some other cases around line continuation where the result looks ugly. I have to refactor some parts to make this go more smoothly and do this properly. No way around that.

Image

Turns out, my current message text parser does not even parse plain links. That’s next on the agenda.

Oh, I also noticed that this thing crashes when there is not enough space to actually draw stuff. No shortage of work. Anyway, time is up, good night. :-)

​ Read More
In-reply-to » Fuck me dead, what a giant piece of shit. On my Linux work laptop I have the problem that some unknown snakeoil "security" junk is dropping any IPv4 connections to ports 80 and 443. All other ports and IPv6 seem unaffected. I get an immediate "connection refused" when trying to estabslish a connection.

It just worked fine like nothing had ever happened when I booted my laptop this morning.

​ Read More
In-reply-to » Fuck me dead, what a giant piece of shit. On my Linux work laptop I have the problem that some unknown snakeoil "security" junk is dropping any IPv4 connections to ports 80 and 443. All other ports and IPv6 seem unaffected. I get an immediate "connection refused" when trying to estabslish a connection.

Thank you, @movq@www.uninformativ.de! Luckily, I can disable it. I also tried it, no luck, though. But the problem is, I don’t really know how much snakeoil actually runs on my machine. There is definitely a ClownStrike infestation, I stopped the falcon sensor. But there might be even more, I’ve no idea. From the vague answers I got last time, it feels like even the UHD/IT guys don’t know what is in use. O_o

Yeah, it is definitely something on my laptop that rejects connections to IPv4 ports 80 and 443. All other devices here can access the stuff without issue, only this work machine is unable to. The “Connection refused” happens within a few milliseconds.

Unfortunately, I do not have the slightest idea how it works. But maybe I can look into that tomorrow. Kernel modules are a very good hint, thank you! <3

You’re right, it might be some sort of fail-safe mechanism. But then, why just block IPv4 and not also IPv6? But maybe because the VPN and company servers require IPv4, there is zero IPv6 support. (Yeah, don’t ask, I don’t understand it either.)

​ Read More

Fuck me dead, what a giant piece of shit. On my Linux work laptop I have the problem that some unknown snakeoil “security” junk is dropping any IPv4 connections to ports 80 and 443. All other ports and IPv6 seem unaffected. I get an immediate “connection refused” when trying to estabslish a connection.

I had this problem four weeks ago on Friday morning the very first time at home. On Thursday evening, everything was perfectly fine. Eventually, I plugged in the LAN cable in the office and everything got automatically fixed. Nobody can explain what’s happening.

Then, last week Friday morning out of the blue, the same issue was back. So, I went to the office yesterday and it got fixed again by plugging in the network cable. This evening, I have exactly the same bloody problem again.

What the hell is going on? Does anyone have any ideas? I’m certainly not an expert, but I don’t see anything suspicious in iptables or nft rules. I also do not see anything showing up in /var/log/kern.log. Even tried to stop firewalld, flush the iptables and nft rules, but that didn’t result in any changes.

​ Read More

@movq@www.uninformativ.de Oh man, this is beautiful! We had sunshine all day long. But it was cold, too. When I left the house in the late afternoon, the sun was creating this magical red light. I just hit the right time, all the autumn colors popped out like crazy when I walked down the street. Didn’t bring my camera, though.

​ Read More
In-reply-to » I'm very glad that I decided to have a very long lunch break today. When I reached the summit, dark clouds came from the northwest and the sun was gone for the day. But on the way there I was delighted about all the beautifully blazing colors around me. https://lyse.isobeef.org/waldspaziergang-2024-11-25/

@movq@www.uninformativ.de I’ll ask them when I see somebody around next time. :-)

​ Read More
In-reply-to » I'm very glad that I decided to have a very long lunch break today. When I reached the summit, dark clouds came from the northwest and the sun was gone for the day. But on the way there I was delighted about all the beautifully blazing colors around me. https://lyse.isobeef.org/waldspaziergang-2024-11-25/

@movq@www.uninformativ.de Exactly, that’s a really weird “r”. The only thing I can think of is that the wooden letters were cut out on a bandsaw. Whoever made the sign wanted to avoid cutting a hole in an uppercase “R”, because they had no jigsaw on hand. So, they went with the lowercase one.

​ Read More
In-reply-to » I'm very glad that I decided to have a very long lunch break today. When I reached the summit, dark clouds came from the northwest and the sun was gone for the day. But on the way there I was delighted about all the beautifully blazing colors around me. https://lyse.isobeef.org/waldspaziergang-2024-11-25/

@bender@twtxt.net Ta! <3

​ Read More

We had 5cm snow at our scout yard at 10 o’clock. But it was nearly fully gone when we called it quits after sunset.

In May we charred cloth to be used as tinder. A fire steel and some wood shavings lit the fire in under a minute. Maybe half. That was good fun. I reckon I have to replenish the charred cloth soon, though. It’s crazy how great that works. I’m absolutely amazed.

We cut back the thorny brushes for hours and eventually winched out some heavy fallen trees. That was really cool to see this powerful winch in action. Absolutely effortless. It was also a complete one man show. We couldn’t do anything and just watch. There is no chance that we could have moved the tree trunks up the steep hill with just man power. Well, a few dozen people might have made it with great struggle.

Next time we have to cut them into smaller pieces and split them into firewood or keep some for contruction. I will see whether I can safe some to cut some boards from. A sawmill would be really cool to have. :-)

Image

https://lyse.isobeef.org/plaetzlestag-2024-11-23/

​ Read More
In-reply-to » Time to rotate three months into archive feeds again.

@bender@twtxt.net My made-up rule is to keep at least three full months in the main feed and when rotating, I create one feed per month.

@doesnm@doesnm.p.psf.lt There is no real recommendation I think. But if you hit half a MiB or so, it might be worth considering to rotate in order to keep the network traffic low. People with bad connectivitiy might appreciate it. I want to implement HTTP range requests in my client rewrite at some point in time (but first, it has to become kinda usable, though).

​ Read More

@movq@www.uninformativ.de I’m all in on paper. In fact I noted down a todo item today on a physical sheet of paper when I was on the phone with a workmate. It then occurred to me that I could have just written it in a scratch file.

The parchment, on the other hand, might be a bit wasteful for just temporary ideas that are not perfectly layed out yet.

​ Read More

@movq@www.uninformativ.de Yeah, the Swiss and C++ programmers use apostrophes. :-) My grandpa had an electronic desk calculator that also used some kind of apostrophes as the thousands separator on its cool display. Maybe it consisted of Nixie tubes, can’t remember anymore.

I think non-breaking spaces are preferred nowadays to avoid the confusion.

​ Read More
In-reply-to » @sorenpeter Section 7 on emojis: Exactly that, it's an avatar for text interfaces. The metadata name needs tweaking, but that's a cool idea. If I implemented this in my client, I'd make the text avatar overridable by the user, though. Otherwise I'd probably only see boxes for everbody in my terminal. :-D

@bender@twtxt.net Fair point, could be. I probably have to implement it first or create some kind of a mockup to spare me the effort of some feature that I rip out again. :-)

​ Read More
​ Read More
In-reply-to » @eapl.me here are my replies (somewhat similar to Lyse's and James')

@sorenpeter@darch.dk Section 7 on emojis: Exactly that, it’s an avatar for text interfaces. The metadata name needs tweaking, but that’s a cool idea. If I implemented this in my client, I’d make the text avatar overridable by the user, though. Otherwise I’d probably only see boxes for everbody in my terminal. :-D

​ Read More

Thank you, @eapl.me@eapl.me! No need to apologize in the introduction, all good. :-)

Section 3: I’m a bit on the fence regarding documenting the HTTP caching headers. It’s a very general HTTP thing, so there is nothing special about them for twtxt. No need for the Twtxt Specification to actually redo it. But on the other hand, a short hint could certainly help client developers and feed authors. Maybe it’s thanks to my distro’s Ngninx maintainer, but I did not configure anything for the Last-Modified and ETag headers to be included in the response, the web server just already did it automatically.

The more that I think about it while typing this reply, the more I think your recommendation suggestion is actually really great. It will definitely beneficial for client developers. In almost all client implementation cases I’d say one has to actually do something specifically in the code to send the If-Modified-Since and/or If-None-Match request headers. There is no magic that will do it automatically, as one has to combine data from the last response with the new request.

But I also came across feeds that serve zero response headers that make caching possible at all. So, an explicit recommendation enables feed authors to check their server setups. Yeah, let’s absolutely do this! :-)

Regarding section 4 about feed discovery: Yeah, non-HTTP transport protocols are an issue as they do not have User-Agent headers. How exactly do you envision the discovery_url to work, though? I wouldn’t limit the transports to HTTP(S) in the Twtxt Specification, though. It’s up to the client to decide which protocols it wants to support.

Since I currently rely on buckket’s twtxt client to fetch the feeds, I can only follow http(s):// (and file://) feeds. But in tt2 I will certainly add some gopher:// and gemini:// at some point in time.

Some time ago, @movq@www.uninformativ.de found out that some Gopher/Gemini users prefer to just get an e-mail from people following them: https://twtxt.net/twt/dikni6q So, it might not even be something to be solved as there is no problem in the first place.

Section 5 on protocol support: You’re right, announcing the different transports in the url metadata would certainly help. :-)

Section 7 on emojis: Your idea of TUI/CLI avatars is really intriguing I have to say. Maybe I will pick this up in tt2 some day. :-)

​ Read More
In-reply-to » Hey @eapl.me, your feed is broken. All U+2028 got transformed into newlines.

Perfect, @eapl.me@eapl.me, it’s fixed again. In fact this editor seems to support the Unicode line separator character all too well, otherwise it would not have replaced it in the first place. :-D Time to switch to a more unintelligent editor. ;-)

​ Read More

Righto, @eapl.me@eapl.me, ta for the writeup. Here we go. :-)

Metadata on individual twts are too much for me. I do like the simplicity of the current spec. But I understand where you’re coming from.

Numbering twts in a feed is basically the attempt of generating message IDs. It’s an interesting idea, but I reckon it is not even needed. I’d simply use location based addressing (feed URL + ‘#’ + timestamp) instead of content addressing. If one really wanted to, one could hash the feed URL and timestamp, but the raw form would actually improve disoverability and would not even require a richer client. But the majority of twtxt users in the last poll wanted to stick with content addressing.

yarnd actually sends If-Modified-Since request headers. Not only can I observe heaps of 304 responses for yarnds in my access log, but in Cache.FetchFeeds(
) we can actually see If-Modified-Since being deployed when the feed has been retrieved with a Last-Modified response header before: https://git.mills.io/yarnsocial/yarn/src/commit/98eee5124ae425deb825fb5f8788a0773ec5bdd0/internal/cache.go#L1278

Turns out etags with If-None-Match are only supported when yarnd serves avatars (https://git.mills.io/yarnsocial/yarn/src/commit/98eee5124ae425deb825fb5f8788a0773ec5bdd0/internal/handlers.go#L158) and media uploads (https://git.mills.io/yarnsocial/yarn/src/commit/98eee5124ae425deb825fb5f8788a0773ec5bdd0/internal/media_handlers.go#L71). However, it ignores possible etags when fetching feeds.

I don’t understand how the discovery URLs should work to replace the User-Agent header in HTTP(S) requests. Do you mind to elaborate?

Different protocols are basically just a client thing.

I reckon it’s best to just avoid mixing several languages in one feed in the first place. Personally, I find it okay to occasionally write messages in other languages, but if that happens on a more regularly basis, I’d definitely create a different feed for other languages.

Isn’t the emoji thing “just” a client feature? So, feed do not even have to state any emojis. As a user I’d configure my client to use a certain symbol for feed ABC. Currently, I can do a similar thing in tt where I assign colors to feeds. On the other hand, what if a user wants to control what symbol should be displayed, similar to the feed’s nick? Hmm. But still, my terminal font doesn’t even render most of emojis. So, Unicode boxes everywhere. This makes me think it should actually be a only client feature.

​ Read More

@prologic@twtxt.net Yeah, the principle of data economy. :-)

Btw. if you blindly run the command again in a few days, your query might match new feeds that are not included in today’s list. Hence, some accounts might be dropped without a warning. But then, they probably don’t care.

​ Read More