Ah, yes, it is!
@lyse@lyse.isobeef.org ššš @movq@www.uninformativ.deās is Atom?
<updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
This is also why @bender@twtxt.netās Notes feed was unaffected. Itās an RSS feed.
<updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
Aha, yesterdayās newly added support for LC_TIME to render localized timestamps also broke the feed parsing with my LANG=de_DE.UTF-8 and LC_CTYPE=de_DE.UTF-8 environment. :-)
Atom feeds make use of RFC 3339 timestamps. They are first converted into RFC 882 timestamp representation, which is the one that RSS feeds use. However, this conversion now results in localized RFC 882 timestamps, which cannot be parsed into Unix timestamp numbers via curl_getdate(ā¦). I bet that it doesnāt know about the localization at all and expects English month and weekday names. Looking at its docs, I reckon that function was selected because of its myriad of supported timestamp formats: https://curl.se/libcurl/c/curl_getdate.html RFC 3339 is not included, though, hence the transformation up front.
The intermediate Item objects in the parser domain use std::string for the timestamp representation. This isnāt all that silly, because Newsboat supports all sorts of different feed formats with different timestamp formats. These RFC 883 timestamps are centrally parsed into time_t.
Speaking of time: Itās time to go to bed after this late bug hunting fun. :-)
@lyse@lyse.isobeef.org maybe the time has come to dust off that https://lyse.isobeef.org/ page? ;-)
@lyse@lyse.isobeef.org maybe you both are the bots! :-D That asideāwhich may, or may not be true, LOLāI agree too.
@movq@www.uninformativ.de I really like your style of writing, btw. Itās much calmer and less aggressive then mine. :-) When I turned my bullet points into paragraphs, I got a bit mad in the process.
Sure, feel free to include anything you want. Regarding citing, this is where twtxt falls short in my opinion. Especially with feed rotation, classic links die quickly. Message hashes only help so much. Nobody outside the twtxt universe knows how to deal with them. So, not perfect for inclusion on a web page. Linking to a thread or message on some yarnd instance might be the more user-friendly option. But the disadvantage is that itās ājustā a mirror, not the primary or original source. In all reality, this could be considered splitting hairs, though.
I should have probably written a proper article. That would have given me time to review the result more carefully, too. ;-) Perhaps thatās something for the future. But honestly, Iām not sure if I really want to waste my time and energy on that subject. So many other fun or useless things come to mind right away that I could do instead. 8-)
So, yeah, do whatever feels best to you. I donāt mind being cited or linked, but I also donāt mind not to be cited or not to be linked to. :-D Not a helpful answer, I know. Sorry. ;-) But anyway, thanks for asking, mate! I do appreciate it.
To finish my thought, linking to my frontpage is probably also useless, since I deliberatly do not have a table of contents there. In fact, my entire frontpage is rather silly.
@movq@www.uninformativ.de Oh, I understand exactly what you mean. :-) I fully agree with you. And it also completely puzzles me why only so few people share our view.
<updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
On further examination, all the articles have the same timestamps. Whenever the feed was fetched. :-O
I might eventually post this on the Fediverse to get more feedback. (Or maybe not. Depends on my mood. š )
@lyse@lyse.isobeef.org (Do you want to be linked on that page? Do you want your name to be there at all? š¤)
@lyse@lyse.isobeef.org Thanks! There are a few points in there that Iāll add to my list.
Your very first point is obviously crucial. āWriting codeā is just the means to an end for many people and they donāt really care about it or like it, so they love AI. I had this in another draft (it refers to the other list I posted):
https://movq.de/v/614f14c3ef/ramble.txt
And this right here is so important:
simplicity is the real art and much harder to achieve.
Finding an elegant, simple solution is waaaaaaaaaaaaaaaaaay harder than anything else. And hereās the thing: I donāt get why nerds/techies donāt get ānerd-snipedā by this. A lot of people love building big stuff and then brag about being clever/competent because they were able to build that big thing ā but once you realize that this approach is the lazy one, shouldnāt you make finding the elegant solution your goal? Doesnāt that give you more bragging rights?
(Am I being clear? Do you understand what I mean? š )
noai.html page. Apart from the global updated field in my feeds (that one got changed), everything else should be stable, though.
@movq@www.uninformativ.de Thanks. I noticed the <updated> of the feed, too. But for some reason, some articles were suddenly marked as new.
On some YouTube feed <entry>s, I noticed updated <updated> fields showing todayās timestamps. But unless there is no <published>, the <updated> is not even considered. I verified that in the source code. Yet, all the affected articles in Newsboat show todayās timestamp, not the years old publication timestamp. I generate the YouTube feeds from the original feeds myself once a day, so I doubt that this is cause by some YouTube shenanigans.
Very weird, it doesnāt make any sense at all. What is going on here? O_o It doesnāt appear that I have duplicates in the database either.
@lyse@lyse.isobeef.org Uhhh, yes, I have one single script to build the website and I ran that while writing that noai.html page. Apart from the global updated field in my feeds (that one got changed), everything else should be stable, though.
Maybe this helps narrow things down? https://movq.de/v/a6b8a0d15f/feed.png
You didnāt change your Atom feed by any chance yesterday or today, @movq@www.uninformativ.de? Not only do I have a metric shitton of ānewā old items in my YouTube feeds, but also a bunch of your old articles are shown as new.
I fear that this is a Newsboat bug. I rebuilt it yesterday from master.
Of course, @movq@www.uninformativ.de! Most of my points are also included in your list.
First of all, programming is what I really do enjoy the most. So, it doesnāt make any sense at all to not do this anymore. āBut you could use your now free time to do something much cooler and more valuable!ā, others might reply. Fuck no, I donāt want to waste my time with other shit that doesnāt fulfill me, why on earth would I want to do that?
All this hallucination reduces quality badly. In my experience, itās also happening much more rapidly than I expected. Even though developers are still supposed to own and understand whatever has been generated under their name and even be responsible for that, the sad reality is that teammates often blindly trust the AI output. āBut I asked the AI and it told me that $this was impossibleā, āIāve no idea either, but the AI just generated itā are responses I get more often. What really makes my angry is when I point out a flaw and suggest an alternative and this is the reaction. It happened several times that just trying it out and seeing it clearly work to proof my point only took me half a minute, but people still did something handwavy else instead.
The learning effect is drastically reduced. The more time I spend on a topic, the better the odds that whatever I learned actually makes it over into long-term memory. Itās like if a collegue just says ādo it like thatā or āthis solves your problemā, but neither explains the why or how. Somehow, people are still convinced that itās a completely different story when you replace the human counterpart with a computer program in this equation.
Skills are unlearned. Itās like with automation in general, just much worse. You end up in a state where youāve no clue how anything works under the hood or how to actually find out important information that are needed to solve your problem. Youāre screwed when a process breaks out of the blue. Even though it can become also rather terrible, with classical automation youāre typically still be able to decipher how exactly the thing was supposed to do something.
The energy consumption is sooo high, I absolutely do not want to be a part in burning down our planet. Iām sure I find (and probably have long found without knowing) other ways to contribute to worsen our climate crisis.
The scraper part is already covered in detail in your list. :-)
Iām convinced that license and copyright violations are only played down or even refused entirely because companies want to make big money quickly. With the work of others of course. Their double standards are obvious, they still try to actively keep their own stuff secret and out of any training sets. At most for internal use only. Virtually noone in charge is interested in good long-term solutions. Short-term for the win, when disaster eventually strikes, the causers are long gone, the responsibilities in other hands.
Vendor lock-in is something that lots of folks are only realizing very slowly. Itās completely crazy to me. This drug dealer routine should be well-known by now. Itās fucking everywhere. Yet, people are always surprised when they found themselves caught in it.
Adding new AI stuff only increases complexity. But complexity is the enemy that everybody should fear and reduce as much as possible. Of course, this is not limited to AI at all. And everywhere I look around, people in charge looooove to make things way more complicated than they ever need to be. Yet, simplicity is the real art and much harder to achieve.
I donāt understand why we have to go back full force to the ambiguity of natural languages. This alone should be more than enough to realize what a stupid idea all that is. Linked to that is that the āinstruction setā is interpreted differently with newer model versions. I mean, is has to be. Why else would somebody want to upgrade in the first place than to get more Powerful⢠Featuresā¢?
Some people argue that with AI the democratization is empowered. However, in my view, the exact opposite is the case. Models are getting so large that you can basically not run them locally or even train them. So, you have to rely on whatever the vendor offers you and runs for you. In the end, this only gives the owners more power, the multi billionaires. Not exactly what I understand by democratization.
Finally, technology assessments are missing completely. Or they are faked such that mostly only the (questionable) benefits are listed. But all the negative impact is just ignored.
Letās keep some popcorn around for when this all explodes. :-)
Weāre currently at about 28-30°C, but the relative humidity is at a crazy low level of 20%. š³ This actually feels pretty nice. If it only were always like that ā¦
@arne@uplegger.eu @movq@www.uninformativ.de Typically, I use āIā. But also āoneā and, less common, āyouā.
@movq@www.uninformativ.de Yes, this is the tricky bit for sure.
Of course, they say that totally convinced. Until it eventually explodes in their faces and let others clean up after themselves.
@itsericwoordward@itsericwoodward.com @bender@twtxt.net @prologic@twtxt.net Hahaha, itās working fine in mine. But I cannot use spaces in the nickname. :-)
@bender@twtxt.net I have no idea. Probably busy with life yaāknow š Iām just as guilty myself.
@prologic@twtxt.net I have no doubts. Within that parsing thought, I wonder, where in the world is @xuu@txt.sour.is?
@itsericwoodward@itsericwoodward.com such a dĆ©jĆ vu! Breaking Yarnās parser used to be a daily routine. Now it doesnāt happen that often mostly because I have learned what it will cause it to break, and hold myself back. But it is finicky! š
@arne@uplegger.eu Lol, indeed, now that you mention it ⦠āYou canāt do that!ā āYou really should $foo.ā
LOL! You broke my link parser. š