Let me introduce you to the much superior version 4 instead: https://lyse.isobeef.org/tmp/twxm4.xml
@thecanine@twtxt.net And this is exactly why there are quirks modes in browsersâŠ
Iâm actually glad I donât have to deal with all this web shit and work with compilers that hit me in the face when I do something illegal. :-)
Eberbach is nowhere near Bad Wimpfen in comparison, but still has a nice historic old town: https://lyse.isobeef.org/eberbach-2025-03-29/
Bad Wimpfen has a pretty cool old town with timber framed houses. Looks really beautiful: https://lyse.isobeef.org/bad-wimpfen-2025-03-28/
@thecanine@twtxt.net I found it! This looks like colored easter eggs when squinting.
@kat@yarn.girlonthemoon.xyz They all just wanted to be friends with a cool gal like you. ;-) Itâs sad that putting things openly on the internet just waits to be raided by script kiddies, bots or spammers eventually.
@movq@www.uninformativ.de Yeah, like nearly all of them. There is the so called Bannwald, where it typically is not allowed to log, but thereâs only one in my entire county and I havenât even visted it. I should change that. https://de.wikipedia.org/wiki/Bannwald
@movq@www.uninformativ.de Hahaha, geil! :-D
@movq@www.uninformativ.de Haha, thatâs cool! :-D
@movq@www.uninformativ.de Thatâs really great! I canât tell the difference to the original. :-)
This time, I brought my cam along. We checked out a piece of ex-forest theyâve cut down. It looks terrible now. :-( At least the spruce resin smell was nice. https://lyse.isobeef.org/waldspaziergang-2025-03-27/
@eapl.me@eapl.me According to an update of the article, others have suggested the same.
Your explanation seems fitting. I just donât get why people donât use feed readers anymore. Anyway.
@xuu@txt.sour.is Yeah, it will be delayed. Oh well. Thatâs just the way it is. :-)
@movq@www.uninformativ.de Hahaha, that filename! :-D 100 times better than I could ever play.
@xuu@txt.sour.is If the unread counter becomes negative, wouldnât that mean I have that many more read messages? :-D
@bender@twtxt.net Youâre spot on, itâs important to not introduce classical bugs!
@movq@www.uninformativ.de Oh dear. :-( Have they fixed it?
@prologic@twtxt.net @movq@www.uninformativ.de I had a t-shirt with this one or the other decade ago. :-)
âUnread messages: -1â: Well, classic off by one error. I gotta have to hunt that down.
@movq@www.uninformativ.de Thatâs not very retrocomputing!
@eapl.me@eapl.me Interesting! Two points stood right out to me:
Why the hell are e-mail newsletters considered a valid option in the first place? Just offer an Atom feed and be done with it! Especially for a blog of this very type. This doesnât even involve a third party service. Although, in addition he also links to Feedburner, what the fuck!? No e-mail address or the like is needed and subject to being disclosed.
When these spam mailers want to prevent resubscribing, then for fuckâs sake, why donât they use a hash of the e-mail address (I saw that in yarnd) for that purpose? Storing the e-mail address in clear text after unsubscribing is illegal in my book.
@movq@www.uninformativ.de I see, fair point, yeah.
about:compat
in Firefox.
@movq@www.uninformativ.de Yikes! I didnât know about about:compat
. Crazy!
@xuu Wow, thatâs a giant graveyard. In my new database I have 16,428 messages as of now. Archive feed support is not yet available, so itâs just the sum of all the 36 main feeds.
There are 82.108 read statuses, but only 24.421 messages in the cache. In contrast to the cache with the messages, the read statuses are never cleaned up when a feed was unsubscribed from. And the read statuses also contain old style hashes, before we settled on the what we have today. Still a huge difference. Hmm.
tt
reimplementation that I already followed with the old Python tt
. Previously, I just had a few feeds for testing purposes in my new config. While transfering, I "dropped" heaps of feeds that appeared to be inactive.
Thanks, @movq@www.uninformativ.de!
My backing SQLite database with indices is 8.7 MiB in size right now.
The twtxt
cache is 7.6 MiB, it uses Pythonâs pickle
module. And next to it there is a 16.0 MiB second database with all the read statuses for the old tt
. Wow, super inefficient, it shouldnât contain anything else, itâs a giant, pickled {"$hash": {"read": True/False}, âŠ}
. What the heck, why is it so big?! O_o
@movq@www.uninformativ.de You could also just use a tiling window manager. :-) As a bonus, it doesnât waste dead space, the window utilizes the entire screen. To also get rid of panels and stuff, put the window in fullscreen mode.
tt
reimplementation that I already followed with the old Python tt
. Previously, I just had a few feeds for testing purposes in my new config. While transfering, I "dropped" heaps of feeds that appeared to be inactive.
If I didnât mess this up, 61 feeds reduced down to 36.
I now subscribed to most feeds in my Go tt
reimplementation that I already followed with the old Python tt
. Previously, I just had a few feeds for testing purposes in my new config. While transfering, I âdroppedâ heaps of feeds that appeared to be inactive.
This might motivate me to actually âfinishâ the new client, so that it could become my daily driver. No need to use the old software stack any longer. Letâs see how bad this goes.
@movq@www.uninformativ.de Yeah, most of the graphical applications are actually KDE programs:
- KMail â e-mail client
- Okular â PDF viewer
- Gwenview â image viewer
- Dolphin â file browser
- KWallet â password manager (I want to check out
pass
one day. The most annoying thing is that when I copy a password, it says that the password has been modified and asks me whether I want to save the changes. I never do, because the password is still the same. I donât get it.)
- KPatience â card game
- Kdenlive â video editor
- Kleopatra â certificate manager
Qt:
- VLC â video player
- Psi â Jabber client (I happily used Kopete in the past, but that is not supported anymore or so. I donât remember.)
- sqlitebrowser â SQLite browser
Gtk:
- Firefox â web browser
- Quod Libet â music player (I should look for a better alternative. Canât remember why I had to move away from Amarok, was it dead? There was a fork Clementine or so, but I had to drop that for some unknown reason, too.)
- Audacity â audio editor
- GIMP â image editor
These are the things that are open right now or that I could think of. Most other stuff I actually do in the terminal.
In the pastâą, I used the Python KDE4 bindings. That was really nice. I could pass most stuff directly in the constructor and didnât have to call gazillions of setters improving the experience significantly. If I ever wanted to do GUI programming again, Iâd definitely go that route. There are also great Qt bindings for Python if one wanted to avoid the KDE stuff on top. The vast majority I do for myself, though, is either CLI or maybe TUI. A few web shit things, but no GUIs anymore. :-)
Oh, itâs called âunsubscribeâ.
@movq@www.uninformativ.de Oh, right, a type would be good to have! :-D
@movq@www.uninformativ.de Where can I join your club? Although, most software I use is decentish in that regard.
I just noted today that JetBrains improv^Wcompletely fucked up their new commit dialog. Thereâs no diff anymore where I would also be able to select which changes to stage. I guess from now on Iâm going to exclusively commit from only the shell. No bloody git integration anymore. >:-( This is so useless now, unbelievable.
@kat@yarn.girlonthemoon.xyz Pointers can be a bit tricky. I know it took me also quite some time to wrap my head around them. Let my try to explain. Itâs a pretty simple, yet very powerful concept with many facets to it.
A pointer is an indirection. At a lower level, when you have some chunk of memory, you can have some actual values sitting in there, ready for direct use. A pointer, on the other hand, points to some other location where to look for the values oneâs actually after. Following that pointer is also called dereferencing the pointer.
I canât come up with a good real-world example, so this poor comparison has to do. Itâs a bit like you have a book (the real value that is being pointed to) and an ISBN referencing that book (the pointer). So, instead of sending you all these many pages from that book, I could give you just a small tag containing the ISBN. With that small piece of information, youâre able to locate the book. Probably a copy of that book and thatâs where this analogy falls apart.
In contrast to that flawed comparision, itâs actually the other way around. Many different pointers can point to the same value. But there are many books (values) and just one ISBN (pointer).
The pointerâs target might actually be another pointer. You typically then would follow both of them. There are no limits on how long your pointer chains can become.
One important property of pointers is that they can also point into nothingness, signalling a dead end. This is typically called a null pointer. Following such a null pointer calls for big trouble, it typically crashes your program. Hence, you must never follow any null pointer.
Pointers are important for example in linked lists, trees or graphs. Letâs look at a doubly linked list. One entry could be a triple consisting of (actual value, pointer to next entry, pointer to previous entry).
_______________________
/ ________\_______________
â â | \
+---+---+---+ +---+---+-|-+ +---+---+-|-+
| 7 | n | x | | 23| n | p | | 42| x | p |
+---+-|-+---+ +---+-|-+---+ +---+---+---+
| â | â
\_______/ \_______/
The âxâ indicates a null pointer. So, the first element of the doubly linked list with value 7 does not have any reference to a previous element. The same is true for the next element pointer in the last element with value 42.
In the middle element with value 23, both pointers to the next (labeled ânâ) and previous (labeled âpâ) elements are pointing to the respective elements.
You can also see that the middle element is pointed to by two pointers. By the ânextâ pointer in the first element and the âpreviousâ pointer in the last element.
Thatâs it for now. There are heaps ;-) more things to tell about pointers. But it might help you a tiny bit.
@andros@twtxt.andros.dev @prologic@twtxt.net Exactly. The screenshots of the last few days show it in action. But I do not consider it ready for the world yet. @doesnm@doesnm.p.psf.lt appears to have a high pain tolerance, though. :-)
@andros@twtxt.andros.dev You use your real name as login name, too?
@prologic@twtxt.net I see this with the scouts. Luckily, not at work. But at work, Iâm surrounded by techies.
@movq@www.uninformativ.de Oh my goodness! Iâm so glad that I donât have to deal with that in my family. But yeah, I guess youâre onto something with your theory. This article is also quite horrific. O_o
@movq@www.uninformativ.de Wooaah, that is cool! \o/
Hahaha, a bird is singing really load and it sounds almost exactly like a car alarm. Well, itâs probably the other way around, the car alarm was modeled after the birdcall. :-)
@eapl.me@eapl.me I looked at the first few puzzles and they are pretty cool so far! I havenât actually implemented any of them, but Iâm fairly certain about how Iâd solve them properly. I went through some linked reference articles yesterday, theyâre also really good. I will recommend this to some workmates. :-)
Itâs extremely surprising to me that younger non-technical people just type in their full name (properly cased first and last name with a space in between) for a technical username in account registration or login forms. Iâve seen that happening several times in the past few years. The field name is âBenutzernameâ in German, literally âusernameâ. Even adding a placeholder text to signal that they could simply use their nickname in lowercase did not change anything at all. Well, one person used at least an e-mail address.
This wasnât the case six, seven years ago, everybody had some ârealâ username. Even non-techies. It looks like some âcommon knowledgeâ is getting lost. Strange. Very weird. It trips me every time I see it.
Have you experienced something similar?
@doesnm@doesnm.p.psf.lt Heck yeah! Worky, worky! \o/
Ctrl+Left
to jump a word left, I get 1;5D
in my tt2 message text. My TERM
is set to rxvt-unicode-256color
. In tt
, it works just fine. When I change to TERM=xterm-256color
, it also works in tt2
. I have to read up on that. Maybe even try to capture these sequences and rewrite them.
@movq@www.uninformativ.de Hahaha, that name is certainly fitting! :-D
Yeah, I should revert that and try to figure out which programs misbehaved. But thatâs something for future Lyse. 8-) Right now, I just redefine TERM
in my Makefile when the USER
happens to be me.
Ctrl+Left
to jump a word left, I get 1;5D
in my tt2 message text. My TERM
is set to rxvt-unicode-256color
. In tt
, it works just fine. When I change to TERM=xterm-256color
, it also works in tt2
. I have to read up on that. Maybe even try to capture these sequences and rewrite them.
Well, some time ago I put this in my ~/.Xdefaults:
URxvt.keysym.Control-Up: \033[1;5Aâš URxvt.keysym.Control-Down: \033[1;5B
URxvt.keysym.Control-Left: \033[1;5Dâš URxvt.keysym.Control-Right: \033[1;5C
Probably to behave more like XTerm and fix a few other issues I had with other programs. But, it turns out, tcell expects the original sequence: https://github.com/gdamore/tcell/blob/main/terminfo/r/rxvt/term.go#L487
Hmm.
Hmmm, when I Ctrl+Left
to jump a word left, I get 1;5D
in my tt2 message text. My TERM
is set to rxvt-unicode-256color
. In tt
, it works just fine. When I change to TERM=xterm-256color
, it also works in tt2
. I have to read up on that. Maybe even try to capture these sequences and rewrite them.
@david@collantes.us Tada, the reply context is now also shown above. Itâs slowly coming together and reaching a state where I can actually use this as my daily driver I think. :-)
@david@collantes.us Thanks, yes, absolutely! ;-)
I now notice that I should also show the original message(s) to which I reply. That was super useful in the original tt
. But one after the other. The mentions are now automatically filled in. \o/
Perfect!
I now also implemented basic replying by hitting a
as in answering. Whatâs missing is automatically adding mentions in the message text template. Thatâs gonna be a bit more tricky, though.
tt
.) Now, this is the second attempt in tt2
.
Righto, now with added basic subject support. Hopefully!
(Back in tt
.) Well, it kinda worked. At least appending to the file. But my cache database got screwed up. I do not yet support replies, so the subject and and root hash columns have not been set at all, resulting in a message that is just not shown at all. I gotta do something about that next. The good thing is, though, after simply fixing the two columns the message appeared on screen.
(The previous message was written with tt
.) Now, this is the second attempt in tt2
.
Letâs see!
Dang it, first attempt failed:
Somehow, my local feed cannot be opened to append to. I reckon, I have to resolve the tilde first:
@kat@yarn.girlonthemoon.xyz Allegedly, thereâs at least a CLI for that, yarnc
. I neither used nor looked at it, though.
@movq@www.uninformativ.de Oh for sure, I fully agree!
@eapl.me@eapl.me Cool!
Proposal 3 (https://git.mills.io/yarnsocial/twtxt.dev/issues/18#issuecomment-19215) has the âadvantageâ, that you do not have to âmentionâ the original author if the thread slightly diverges. It seems to be a thing here that conversations are typically very flat instead of trees. Hence, and despite being a tree hugger, I voted for 3 being my favorite one, then 2, 1 and finally 4.
All proposals still need more work to clarify the details and edge cases in my opinion before they can be implemented.
@kat@yarn.girlonthemoon.xyz Itâs there, but yarndâs markdown library probably thinks that itâs some broken HTML and swallows it, not sure.
@thecanine@twtxt.net Yeah, nobody will ever find that setting.
@movq@www.uninformativ.de ]:-> Ah, just that one line scrolls horizontally, not the entire screen.
@thecanine@twtxt.net It suits your site very well, but I find this font hard to read. In any case, keep on pixeling.
@movq@www.uninformativ.de Haha! Yeah, I really donât know if thatâs the best translation.
In the meantime, I tried to add English subtitles, so the international audience has a chance of enjoying some of them, too. There are a bunch of puns, so translations donât work at that great.
I went to an exhibition of my fine arts teacher who passed away last year. He was a pretty cool dude and good teacher. I reckon I had him in 7th and probably also 8th grade. His Schelme (imps) were very famous here in this county and presumably well beyond.
Unfortunately, picture frame glas doesnât mix all that great with a fairly dark light and my camera. So, sorry in adavance for the poor quality. Anyway, I photographed a few funny paintings. Watch out, it may contain saucy contents: https://lyse.isobeef.org/siegfried-wagner-farrenstall-2025-03-15/.
@movq@www.uninformativ.de Hahaha, nice! :-D I had to check the solution to get it. Itâs a good one.
Ich war auf der Ausstellung meines letztes Jahr verstorbenen BK-Lehrers. Er war ein ziemlich cooler Typ und guter Lehrer. Wenn ich mich recht erinnere, mĂŒsste ich ihn in der 7. und vermutlich auch 8. Klasse gehabt haben. Seine Schelme waren hier im Landkreis und vermutlich darĂŒber hinaus weit bekannt.
Bilderrahmenglas in Verbindung mit vergleichsweise dunkler Beleuchtung gibt leider keine gute Kombination mit meiner Kamera ab. Vorab entschuldige ich mich bereits fĂŒr die zu wĂŒnschen ĂŒbrig lassende QualitĂ€t. Nichtsdestotrotz habe ich ein paar witzige Bilder abfotografiert. Obacht, kann mitunter anzĂŒglichen Inhalt enthalten: https://lyse.isobeef.org/siegfried-wagner-farrenstall-2025-03-15/
Hahaha, ein Klassiker herrlich nachgespielt: https://www.youtube.com/watch?v=vkNuWG_J544 Unglaublich, kann man sich bei uns heutzutage ĂŒberhaupt nicht mehr vorstellen.
@eapl.me@eapl.me Yes, I believe so.
Thatâs cool, solar eclipse on the moon: https://www.flickr.com/photos/fireflyspace/54386246629/in/album-72177720313239766/
@movq@www.uninformativ.de @prologic@twtxt.net Dito. Even though I only had four day weeks and three days of weekend the last month, I feel very exhausted as well. Back to five days next week. :-(
@movq@www.uninformativ.de Thatâs cool! I just canât justify the amount of space it permanently takes. But it fits nicely with the other gauges you have. And with that in mind, it actually is super tiny.
@eapl.me@eapl.me Interesting, I wasnât aware that other parts of the world consider them to be a German thing :-)
@arne@uplegger.eu Das ist ein recht zuverlĂ€ssiger Wetterbericht. Wenn die Bauern mit ihren GĂŒllefĂ€ssern hier vorbeifahren, weiĂ ich sofort, dass Regen angekĂŒndigt ist. :-)
Ha, das Lied gefĂ€llt mir auĂerordentlich gut! \o/ Mit Abstand das beste GĂŒllelied. Ich kenn noch ein paar schwĂ€bische, aber die gehen lang nicht so ab wie dieses hier.
@eapl.me@eapl.me @bender@twtxt.net @prologic@twtxt.net Not including a photo was a stupid move, sorry. There you go:
This particular one is 95mm wide and 185mm high. Fairly compact.
I can only use it figure out distances to other dates and to do some basic calendar math. Iâm not able to actually schedule anything. But I grew up with a month calendar like you have there where all appointments of the entire family was recorded.
By far most of my paper use is drawing random stuff on scratch paper during meetings. :-D
@arne@uplegger.eu Ah, witzige Geschichte! Ich fĂŒrchte, der Eberhardt wird sich nun bei mir auch festsetzen. ;-)
I got a small desk calendar as advertising gift. It shows three months at once. Iâm using this thing since the beginning of this year and I have to say that it turned out to be super useful. Iâm happily surprised.
It sits on my desk next to my rightmost monitor. Iâve set it up so that I can see the last, current and next months. Each morning, I advance the âtoday windowâ or whatever its proper name is. This gives me a sense of what date we have today and which I will have forgotten half a minute later already. At most. However, itâs easily at hand by turning my head just a few degrees.
With the last month still showing, I had several occasions so far where a date in the past popped up in a meeting. I could easily tell when something happened, how long ago that was. Or how many days or weeks are left until we have to deliver something, etc.
In hindsight, this is absolutely no surprise at all. But I still find it fascinating. Iâm now actually wondering why I never had something like that before. How could I live without that thing? Sure, I pulled up a calendar on my computer, ncal -w3
or so. But I always hated the inverted ncal
output, necessary for showing week numbers, though. Having a paper calander right next to my screen at all times is sooooo much more handy.
So, do yourself a favor and think about whether such a desk calendar might be useful to you.
The only annoying thing is that the âtoday windowâ moves too easily. It slips down by its own. I reckon it wants me to regularly interact with it, so that I memorize the current date.
@andros@twtxt.andros.dev If something fits in a CSV file, it typically doesnât require a database. I agree with that. Depending on the application, more complicated queries might benefit from a database, though. I donât know awk very well, but I could imagine that grep, sed and cut reach their CSV processing limits rather quickly when you have to deal with escaped (multiline) fields.
I only very rarely have to deal with CSV files or databases in my day to day life. Maybe, these classic Unix tools offer some tricks Iâm not aware of. When I have some more complicated CSV input, I generally reach for Python.
@eapl.me@eapl.me @arne@uplegger.eu @andros@twtxt.andros.dev Thanks mates!
Hmmm, Eberhardt. Ist das eine plattdeutsche Sache? Dass ich den flinken Nagern so lang zuschauen konnte, war ein seltener GlĂŒcksfall. Normalerweise sind die nach fĂŒnf oder spĂ€testens zehn Minuten wieder aus dem Sichtfeld verschwunden.
@movq@www.uninformativ.de Yeah, horizontal scrolling is an invention right from the devil himself. :-D Itâs awful, I canât stand it.
I watched two squirrels this morning for about half an hour: https://lyse.isobeef.org/eichhoernchen-2025-03-11/ They were super crazy fast. Also, they bit off plenty of twigs and carried them around, not sure where they put them. Iâve never seen them do that before. Once more I realized that I need a better zoom.
Which photos would you remove?
@aelaraji@aelaraji.com I cannot tell you either. I donât know the difference. :-)
@aelaraji@aelaraji.com Thatâs nice, enjoy it while it lasts! Rain can be something wonderful. Stay safe.
@kat@yarn.girlonthemoon.xyz @prologic@twtxt.net When I make dev
on current master, I get a proper version. Same with make server
. Assuming you cloned the repo, do you have any (uncommited) changes? What does git status
tell you?
Of course, @bender@twtxt.net, anytime! As our number one bug finder, your service has to be rewarded. :-)
@prologic@twtxt.net We canât agree on this idea because that makes things even more complicated than it already is today. The beauty of twtxt is, you put one file on your server, done. One. Not five million. Granted, there might be archive feeds, so it might be already a bit more, but still faaaaaaar less than one file per message.
Also, you would need to host not your own hash files, but everybody elseâs as well you follow. Otherwise, what is that supposed to achieve? If people are already following my feed, they know what hashes I have, so this is to no use of them (unless they want to look up a message from an archive feed and donât process them). But the far more common scenario is that an unknown hash originates from a feed that they have not subscribed to.
Additionally, yarndâs URL schema would then also break, because https://twtxt.net/twt/<hash>
now becomes https://twtxt.net/user/prologic/<hash>
, https://twtxt.net/user/bender/<hash>
and so on. To me, that looks like you would only get hashes if they belonged to this particular user. Of course, you could define rules that if there is a /user/
part in the path, then use a different URL, but this complicates things even more.
Sorry, I donât like that idea.
We had a very sunny day, peaking at 19°C. This not only decoyed me out, but also plenty motorcycle terrorists. Eh fuckwits, nobody wants to listen to your bloody engine and exhaust noise, keep it quiet for fuckâs sake! Many of your rider collegues can manage it, too, so should you.
I had some sore muscles after yesterdayâs waste paper collection with the scouts. So, I only went for a short trip to my closest backyard mountain. Watching two rock climbers was interesting. Thatâs not something I see very often.
@prologic@twtxt.net Hahaha, I love that! :-D Something to laugh during these hard times. Hope youâre doing alright.
@arne@uplegger.eu GlĂŒckwunsch, das ist in der Tat doch mal eine erfreuliche Abwechslung. :-)
Thanks, @xuu, great explanation. In another project Iâve structured it exactly like you wrote. The mock storage over there extends the SQLite storage and provides mechanism to return errors and such for testing purposes:
- storage/ defines the interface
- sqlite/ implements the storage interface
- mock/ extends the SQLite implementation by some mocking capabilities and assertions
- sqlite/ implements the storage interface
Here, however, there are no storage subpackages. Itâs just storage
, thatâs it. Everything is in there. The only implementation so far is an SQLite backend that resides in storage
. My RAM storage is exactly that SQLite storage, but with :memory:
instead a backing file on disk. I do not have a mock storage (yet).
I have to think about it a bit more, but I probably have to do exactly that in my tt
rewrite, too. Sigh. I just have the feeling that in storage/sqlite/sqlite_test.go I cannot import storage/mock for the helper because storage/mock/mock.go imports and embeds the type from storage/sqlite. But Iâm too tired right now to think clearly.
@arne@uplegger.eu Hals- und Beinbruch! Die Bahn hat ja nur die vier Feinde: FrĂŒhling, Sommer, Herbst und Winter. Wurdest Du heute positiv ĂŒberrascht?
@prologic@twtxt.net You just have to stay in the center. Itâs supposed to be calm in there I heard. Just getting there is the tricky part. Good luck!
@movq@www.uninformativ.de âThermometer must not be installed near aircraft turbine exhaust.â
@xuu My layout looks like this:
- storage/
- storage.go: defines a
Storage
interface
- sqlite.go: implements the
Storage
interface
- sqlite_test.go: originally had a function to set up a test storage to test the SQLite storage implementation itself:
newRAMStorage(testing.T, $initialData) *Storage
- storage.go: defines a
- controller/
- feeds.go: uses a
Storage
- feeds_test.go: here I wanted to reuse the
newRAMStorage(âŠ)
function
- feeds.go: uses a
I then tried to relocate the newRAMStorage(âŠ)
into a
- teststorage/
- storage.go: moved here as
NewRAMStorage(âŠ)
- storage.go: moved here as
so that I could just reuse it from both
- storage/
- sqlite_test.go: uses
testutils.NewRAMStorage(âŠ)
- sqlite_test.go: uses
- controller/
- feeds_test.go: uses
testutils.NewRamStorage(âŠ)
- feeds_test.go: uses
But that results into an import cycle, because the teststorage
package imports storage
for storage.Storage
and the storage
package imports testutils
for testutils.NewRAMStorage(âŠ)
in its test. Iâm just screwed. For now, I duplicated it as newRAMStorage(âŠ)
in controller/feeds_test.go.
I could put NewRAMStorage(âŠ)
in storage/testutils.go, which could be guarded with //go:build testutils
. With go test -tags testutils âŠ
, in storage/sqlite_test.go could just use NewRAMStorage(âŠ)
directly and similarly in controller/feeds_test.go I could call storage.NewRamStorage(âŠ)
. But I donât know if I would consider this really elegant.
The more I think about it, the more appealing it sounds. Because I could then also use other test-related stuff across packages without introducing other dedicated test packages. Build some assertions, converters, types etc. directly into the same package, maybe even make them methods of types.
If I went that route, I might do the opposite with the build tag and make it something like !prod
instead of testing. Only when building the final binary, I would have to specify the tag to exclude all the non-prod stuff. Hmmm.
Dang it! I ran into import cycles with shared test utilities again. :-( Either I have to copy this function to set up an in-memory test storage across packages or I have to put it in the storage package itself and guard it with a build tag that is only used in tests (otherwise I end up with this function in my production binary as well). I donât like any of the alternatives. :-(
Thank you, @eapl.me@eapl.me, this is awesome! Iâm curious to see if we find some more advantages with the current approach. It seems there should be some more, but I can only think disadvantages right now. :-)
@prologic@twtxt.net Best wishes!
@movq@www.uninformativ.de Did you place it in the sun? We only got 15°C today.
@prologic@twtxt.net Damn! :-( Yeah, I wonât build that into my client. Not worth it for the many things that are still undetectable and the low frequency it happens.
@bmallred@staystrong.run Oh, I hear you! Itâs always after carefully proofreading and publishing that a typo suddenly pops up. :-) Not sure if amending your edit implementation is really worth it, but happy hacking in case you do.
@movq@www.uninformativ.de Luckily, theyâre not made of steel as I would not have made it home with such heavy weights. :-D
@movq@www.uninformativ.de Fuck! So there arenât any non-criminal printer vendors out there anymore. Very sad. I really donât understand why this is not highly illegal in the entire world.
And I just added a video clip of the woodpecker. As you can easily see from the shaking, it hammers so dang hard that the whole ground around the tree vibrates.
I went on a 5:30 hours long hike to my second backyard mountain. About 12km to get there and roughly 9km on the way back. It was super nice, sunny all day long, 12°C and luckily just a little bit of wind. Great scenery. I managed to capture one great spotted woodpecker hammering along. There was also a kestrel hovering over a meadow and then landing on a sports field light pole. At the castle ruin I could watch 10-12 gliding red kites (with the V-shaped tail) and other raptors, maybe bussards, I donât know, for about five minutes. That was fascinating. Unfortunately, my camera doesnât too well with moving targets.
86 more photos: https://lyse.isobeef.org/wanderung-auf-den-hohenrechberg-2025-03-03/