lyse @lyse.isobeef.org

Follow

Block / Report User

If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@lyse does not follow you (they may not see your replies!)

Recent Twts

Recent twts from lyse

(#4xx2kfq) @eaplmx@twtxt.net I forgot to mention that I like the HTTP status codes idea! I need to think about it a bit more, but that sounds very appealing. We just need to watch out that we don’t tie it too much to HTTP. I have no clue about Gopher or Gemini.


#lekfxla

(#ddmgxaq) @prologic@twtxt.net I’m happy to see a fix in yarnd. ;-) The thing is, though, there are still old broken data out there. You can’t fix them. At least not without breaking all sorts of conversations then. And I assume lots of people just don’t care about their old contents all that much as to bother fixing mention URLs.


#6gc4eva

(#nm5o2na) @mckinley@twtxt.net The idea is not to have a single source of truth. It’s definitely designed to have multiple databases operated by different people. That’s why all this synchronization exists. Granted, I haven’t put much thought into that so far.


#d6ar5aq

(#4xx2kfq) @eaplmx@twtxt.net The idea is to only provide mappings for wrong URLs and mark dead ones. So a single database for multiple protocols should do. No need to spin up a dedicated one for a different protocol. If a feed is available over multiple protocols or locations, there’s no need to insert any of them, if they work. Unless one wants to rewrite some URLs to some other canonical forms.


#7zafula

(#j4fqi3q) @eaplmx@twtxt.net So I have two personal main goals with this:

  1. In the long run fix producing broken mentions in yarnd. I reckon the yarnd client is the main source of all those broken mentions I’ve encountered so far. There might be others, too, but to me it looks like that’s the main bad guy. :-)
  2. Reduce 404 in my HTTP error logs. Yes, I could configure my web server to exclude some paths, but where’s the fun in that?

There are at least three specific reasons why a twtxt feed URL is wrong at some point in time. And there are probably much more.

  1. It never existed in the first place, because somebody screwed up the feed URL a mention, some other feed URL should have been used.
  2. The feed URL was valid before but it is now gone, the feed author decided to quit.
  3. The feed URL was valid before but the feed author decided to move the feed to somewhere else.

I’m not entirely sure what you mean with “two URLs have changes”. But the idea would be if URL A becomes wrong for any reason and a mapping to B is added and then later B points to C, A would also be updated to point to C directly.

The main consumers of such a database are search engines/crawlers and clients. Search engines could lookup a twtxt feed URL in this database and follow the mapping instead. Clients could use that DB to check before posting whether a mention should be corrected or use these mappings to fix broken mentions when displaying a twt.


#p4kxonq

I just spent a few hours thinking about the Twtxt Feed URL Normalization Database, that I suggested a few times already in the past weeks. It then occurred to me that a simple text file managed in a version control system would be enough to start out. No need to build a dedicated (web) interface just yet. So ignore all the reviewer, synchronization and REST API stuff for now. Any thoughts? Any feedback is very much appreciated.


#fh6ymua

(#wgjj5ma) @tkanos@twtxt.net Scouting is really great, yes! My best school mate introduced me to it some time at the end of school or beginning of uni, can’t remember. I was invited to the last two days of the scout group camp he had organized. All the folks welcomed me open-heartedly and after just an hour I felt like I was with mates I knew for several years. In fact, I just met them that day for the first time. It took me about another two years to finally hand in my registration. There was just too much else going on. Since I joined very late, I couldn’t be a rover (last youth section, age 16-21 here) anymore. I became a volunteer since I didn’t want to start right off as a leader without even knowing the basics. And then I just stuck with it ever since. :-)

I have to add, this conference was just for our leaders round table — that is leaders, volunteers and a bunch of rovers. No kids this time. But the week before we had the annual scout meeting on Saturday afternoon with the whole group, followed by a scout church service (scouting is affiliated to the church rather than the military in I suppose most of Europe). After that we had a bbq in the church yard for everybody to attend for free. I helped setting it up while most of us were in church. On Sunday we played games with all the kids, grilled stick bread on the fire and then older kids were “levelled up” to the next youth sections and got their new colored scarfs of their new troops.

German report of that weekend: https://dpsg-salach.de/2022/bericht-vom-stammeswochenende/


#3wdnwoa

(#wgjj5ma) @prologic@twtxt.net @tkanos@twtxt.net I’m a volunteer not a leader, so I don’t have a group of kids, but I help out at most events. Our yearly conference was good fun. We went through a few topics, scheduled most events for next year and assigned organizers. Later, we went on an excursion to nearby Schloss Weißenstein where we got a guided tour through the palace and saw super amazing microscopic shots of all sorts of things. The tour guide’s dad was a pioneer on microscopic photography. The absolute highlight at the end was watching some kind of glue crystalizing live. Highly entertaining science art. I’ll be back some day, that’s for sure.

In order to get to the KreuzberghĂĽtte that we rented for the weekend, we split up into two groups and went for a scavenger hunt. It took both teams a bit longer than we anticipated, but they all made it. On the way back we discovered that one group solved one quizz completely and utterly wrong, but still managed to find the final solution with the next coordinates. They parked a few meters ahead than what we had planned and found something completely different, that still perfectly matched the vaguge description on their note.

For dinner on Friday we cooked Linsen mit Spätzle at the hut. When we wanted to roast onions a gas smell suddenly was in the air. So we quickly shut down the gas stove and checked for leaks, but couldn’t find any. Next attempt and the gas smell was back again. We knew the group before us broke one of the two pit toilets, reported the hand water pump in the kitchen to be broken (worked flawless after priming, though), didn’t turn off the main gas tap, left a filthy baking tray behind, didn’t close a window shutter, so we figured maybe that’s also why the stove was cactus. Hence we decided to get our own gas cooking equipment from our material store. Luckily, we stayed regionally, so about one and a half hours to two later we were back in business. When finally dressing the salad we noticed, that the olive oil with truffle was the cause for the gas smell. Never use this kind of oil for browing onion, kids! Unless you wanna have a good story to tell (and delay your meal).


#qbmgdha

I noticed some unnecessary horizontal rules being rendered at the bottom of twts in the conversation view lately with yarnd’s new design change. They can be seen at least when not being logged in. Not sure if it is the same experience with an active user session. I reckon there will be fork buttons then, so in that case they would be fine, indeed.

In fact, these lines are implemented as border-top CSS properties of twt-nav-classed <nav> containers. But the <nav>s are empty, so I would expect them not being there in the first place. Empty navigation doesn’t make much sense to me.

In any case, keep up the good work! :-)


#j5l4mla

(#wgwmt4q) @tkanos@twtxt.net Cool! I like your disclaimer in the readme. :-D A few things caught my eye while scrolling through the code, the ones I remember:

  1. The protocol switch in lines 141ff could make use of else if.
  2. There’s a superfluous space in the progress bar in line 155.
  3. The User-Agent header contains a { which I reckon is a typo. Also, I reckon the URL and nick should be swapped, in case you wanted to stick to this discoverability format.
  4. The feed discovery regex assumes that filenames always are twtxt.txt which will miss a few feeds, such as @anth@a.9srv.net’s and @hxii@0xff.nu’s. Parsing mentions would be more accurate. And then also parse all mentions from a twt, not just the first one.
  5. If you’re still bored, adding support for archived feeds would be a thing. :-)

Anyways, nice work!


#5illcya

(#wzwth7a) @mckinley@twtxt.net My client parses the mention and just shows the URL. Since I don’t follow that feed, it is rendered white on red just like any other feed I don’t follow. My markdown support is very limited, inline code is unknown to tt, so the mentions put in code blocks are just treated as regular mentions. And then you can see, that you mentioned me incorrectly. :-P


#rxezbja

Boy, it was fricking cold with the wind today. Can’t believe that just three weeks ago I was sweating like a pig. But the rain clouds were pretty nice. Only my camera struggled very much with these lighing conditions. Basically half of the images totally blurred.

The common kestrel on the nature reserve sign didn’t see me coming, so I managed to sneak in up to about ten meters before it took off quickly.


#cpqwwha