I hope not, @bender@twtxt.net! I havenāt checked, but Iād reckon it to be at most a single digit MiB number. How wrong am I?
@nff@www.noizhardware.com Nice! Yeah, itās all about having fun. :-) The simplicity got me hooked. Happy hacking!
@off_grid_living@twtxt.net No right click thing, but in the terminal:
convert -strip -quality 70 -resize 300x original.jpg resized.jpg
āoriginal.jpgā being the filename of the input file and āresized.jpgā the filename of the output. You can play around with the width, ā300xā means 300 pixels wide and the height is determined automatically to still remain in the same ratio. The quality is how much to compress it. The closer to 0 the value gets, the worse the result, but also smaller in file size. More towards 100 and the quality improves together with a larger file size.
You have to install the package āimagemagickā for this to work, I believe.
@off_grid_living@twtxt.net Oh, Iām ready for my retirement, too. :-D Still have some decades to go, unfortunately.
@off_grid_living@twtxt.net You could try starting it in the terminal in order to spot errors. Just open the GNOME Terminal or something like that and then type in ākolourpaintā and hit Enter.
@nff@www.noizhardware.com I do! :-) Btw. line 65 in your feed is broken.
Thanks, @falsifian@www.falsifian.org! Iāll definitely start with the latter one then. Letās see how far I make it. :-)
@falsifian@www.falsifian.org Phew, okay. So, it took a few months to grow that big. I feared that it could have been just a week or so. Yeah, insulation always is a good idea.
@falsifian@www.falsifian.org Hahaha, thatās sick, I love it! :-D I envy you a bit. On the other hand, I have to admit Iām glad that I donāt have to chisel down giant blocks of ice from the house.
@falsifian@www.falsifian.org Mate, what an amazing video, holy cow! :-D We only get complete jokes of icicles compared to what you had there ealier today. Itās a giant wall. For how many days did that grow on your roof?
@falsifian@www.falsifian.org Oh, thatās neat! Interesting how āobviouslyā isnāt all that obvious at all, even to the contrary. I reckon I have to read up on that subject on the weekend. :-)
I like how Ianās and your photo complement each other, winter and summer join forces for something special. :-)
@falsifian@www.falsifian.org Wooooaaaahhh! That is BY FAR the biggest icicle Iāve ever seen. Really cool! :-) How long did it take to melt in your sink? The video download is still dripping in, looking forward to that.
twtxt
, the microblogging for hackers and friends...
@eapl.me@eapl.me I couldnāt care less about ActivityPub, but twtxt is the thing for hackers by design. Thatās the appealing part for me, personally. I actually do enjoy that not everybody and their dogs are here. :-)
@thecanine@twtxt.net I agree!
@movq@www.uninformativ.de @prologic@twtxt.net I donāt know, I donāt see this happening all that often. Very rarely. The problem I encounter much more often is that tech folks are blindly adopting every new hype without thinking the slightest bit what the consequences might be.
But maybe that also means Iām one of these ātold you soā guys. Not sure.
@prologic@twtxt.net That boycott didnāt last very long, eh!?
Yeah, sounds like another hype train arriving at the station.
tt
rewrite in Go and quickly implemented a stack widget for tview. The builtin Pages is similar but way too complicated for my use case. I would have to specify a mandatory name and some additional options for each page. Also, it allows me to randomly jump around between pages using names, but only gives me direct access the first, however, not the last page. Weird. I don't wanna remember names. All I really need is a classic stack. You open a new fullscreen dialog and maybe another one on top of that. Closing the upper most brings you back to the previous one and so on.
@doesnm@doesnm.p.psf.lt Iāll let you know once it reaches a point where it might be barely usable by someone else than myself. There are long ways to go, though. Right now, you donāt wanna even look at it. :-)
Iām continuing my tt
rewrite in Go and quickly implemented a stack widget for tview. The builtin Pages is similar but way too complicated for my use case. I would have to specify a mandatory name and some additional options for each page. Also, it allows me to randomly jump around between pages using names, but only gives me direct access the first, however, not the last page. Weird. I donāt wanna remember names. All I really need is a classic stack. You open a new fullscreen dialog and maybe another one on top of that. Closing the upper most brings you back to the previous one and so on.
The very first dialog I added is viewing the raw message text. Unlike in @arne@uplegger.euās TwtxtReader, Iām not able to include the original timestamp, though. I donāt have it in its original form in the database. :-/
Next up is a URL view.
@movq@www.uninformativ.de Thatās what I immediately thought as well. :-D @eapl.me@eapl.me Unfortunately, no fancy buttons. What does your model do?
When washing the dishes at the scouts I cut my hand open on the ladle. That piece of shit has a terrible burr.
@prologic@twtxt.net Of course you donāt notice it when yarnd only shows at most the last n messages of a feed. As an example, check out mckinleyās message from 2023-01-09T22:42:37Z. It has ā[Scheduled][Scheduled][Scheduled]ā⦠in it. This text in square brackets is repeated numerous times. If you search his feed for closing square bracket followed by an opening square bracket (][
) you will find a bunch more of these. It goes without question he never typed that in his feed. My client saves each twt hash Iāve explicitly marked read. A few days ago, I got plenty of apparently years old, yet suddenly unread messages. Each and every single one of them containing this repeated bracketed text thing. The only conclusion is that something messed up the feed again.
@movq@www.uninformativ.de Ja, vƶllig behƤmmert. Schade, vertane Chance für einen āDochā-Knopf.
Boah, jetzt mal ernsthaft, was ist denn das für ein Dialog bittesehr!?
Wer hat sich zu dieser Meldung diese Knopfauswahl überlegt und dann auch noch die Icons dazu ausgedacht? Und warum hatās das Zertifikat überhaupt schon wieder zerlegt? Und wieso kommt der Dialog direkt wieder in ner Endlosschleife hoch, wenn ich abbreche? Komplettversagen nach Strich und Faden an allen Enden. Allen. Grrr, so viel Hass! Ich schalt besser die Büchse aus.
@prologic@twtxt.net Tolerant yes, but in the right places. This is just encouraging people to not properly care. The extreme end is HTML where parsers basically accept any input. Iām not a fan of that. Whatever.
@prologic@twtxt.net The issue is that all bracketed text in the entire feed has been duplicated again two days ago. The bug is not fixed. Or itās a new one.
@movq@www.uninformativ.de I can relate to that. :-/
@andros@twtxt.andros.dev I suggest to not touch it and work on a different project instead. :-D
No, in all seriousness, thatās a tough one. Try to figure out the requirements and write tests to cover them. In my experience, if there is no good documention, tests might also be lacking. It goes without saying that you have to understand the code segments first before you can begin to refactor them. Commit even earlier and more often than usual, this will help you bisecting potentially introduced bugs later on. Basically baby steps.
But it also depends on the amount of refactoring required. Maybe just scrap it entirely and start from scratch. This might not be feasible due to e.g. the overall project size, though.
@andros@twtxt.andros.dev Iām all for elegant solutions. I prefer when the computer helps me to really achieve my goal and solve it completely, not where I still have to manually filter a list by hand. Anyway. :-)
@eapl.me@eapl.me Yeah, you need some kind of storage for that. But chances are that thereās already a cache in place. Ideally, the client remembers etags or last modified timestamps in order to reduce unnecessary network traffic when fetching feeds over HTTP(S).
A newsreader without read flags would be totally useless to me. But I also do not subscribe to fire hose feeds, so maybe thatās a different story with these. I donāt know.
To me, filtering read messages out and only showing new messages is the obvious solution. No need for notifications in my opinion.
There are different approaches with read flags. Personally, I like to explicitly mark messages read or unread. This way, I can think about something and easily come back later to reply. Of course, marking messages read could also happen automatically. All decent mail clients Iāve used in my life offered even more advanced features, like delayed automatic marking.
All I can say is that Iām super happy with that for years. It works absolutely great for me. The only downside is that I see heaps of new, despite years old messages when a bug causes a feed to be incorrectly updated (https://twtxt.net/twt/tnsuifa). ;-)
Hahahaha, this is brilliant! :ā-D https://denmarkification.com/
Exactly, @bender@twtxt.net, just like yours and prologicās, too. :-( Subsequent Brackets Considered Harmfulā¢.
@eapl.me@eapl.me Read flags are so simple, yet powerful in my opinion. I really donāt understand why this is not a thing in most twtxt clients. Itās completely natural in e-mail programs and feed readers, but it hasnāt made the jump over to this domain.
@mckinley@twtxt.net Yeah, all this JS and HTMX garbage messes up a lot of things which used to work better in the earlier days.
@prologic@twtxt.net @xuu@txt.sour.is There:
Just search for ][
in https://twtxt.net/user/mckinley/twtxt.txt and youāll see.
@movq@www.uninformativ.de @prologic@twtxt.net @bmallred@staystrong.run @andros@twtxt.andros.dev Thank you all! I donāt have emacs installed, so Iāll try lagrange and see. According to my shell history, I must have played around with amfora ages ago.
@xuu@txt.sour.is People should just fix their feeds. :-)
@movq@www.uninformativ.de Yeah, maybe. What browsers are you using again for these two?
I should really fix my calender rendering. A two day event only pops up in the first day, but not in the second. When extended to three days, it correctly shows up in all three days. Meh.
@mckinley@twtxt.net And there is the bracketed text duplication bug again⦠Actually with lots of twts. Did you edit a twt? Do you remember? /cc @prologic@twtxt.net
robots.txt
file. only noticed it because the OpenAI bot was hitting me with a lot of nonsensical requests. here is the list from last month:
@bmallred@staystrong.run Surprisingly, my
User-agent: *
Disallow: /
seems to work. Or maybe those bastards change their user agent and claim to be someone nice. In any case, I just added a bunch of
location = /robots.txt {
add_header Content-Type text/plain;
return 200 "User-agent: *\nDisallow: /\n";
}
in my nginx config. No need for any bot to visit, crawl and index most of my sites.
@movq@www.uninformativ.de Photographic memory, eh?
@movq@www.uninformativ.de I also thought that I have a new Linux friend the other day. But it was just a fake KDE look from Redmond. :-(
@jost@jost.sdfeu.org Yeah, this AI crap is a big reason not to blog.
@movq@www.uninformativ.de So they say. :-D
Iām not a huge fan of docker. Sorry for the poor screen grab quality, but this is the funniest analogy for āno dockerā vs ādockerā Iāve come across: https://lyse.isobeef.org/tmp/no-docker-vs-docker-analogy.png :-D
Well, thatās another bug: The search https://twtxt.net/search?q=%22LOOOOL%2C+great+programming+tutorial+music%22 yields the wrong hash. It should have been poyndha instead.
@thecanine@twtxt.net Lol⦠I just donāt change my default profile pictures. (Well, only when my teammates ask me to.)
@doesnm@doesnm.p.psf.lt Haha, thatās great! :-D
They fixed it. :-D https://www.youtube.com/watch?v=A8b7HFUXPqk