* 185325d - (HEAD -> master) edge: Ban Alibaba (38 seconds ago) <James Mills>

fark me 🤦‍♂️ Alibaba, CN has been hitting my Gopher proxy quite hard as well. Fuck’n hell! 🔥

* 8a77b64 - (HEAD -> master) edge: Ban Google's ASN (21 seconds ago) <James Mills>

It would appear that Google’s web crawlers are ignoring the robots.txt that I have on https://git.mills.io/robots.txt with content:

User-agent: *
Disallow: /

Evidence attached (see screenshots): – I think its the the Small Web community band together and file a class action suit(s) against Microsoft.com Google.com and any other assholes out there (OpenAI?) that violate our rights and ignore requests to be “polite” on the web. Thoughts? 💭

I got promoted today to try using Passkeys on Github.com. Fine 😅 I did that, but I discovered that when you use your Passkey to login, Chrome prompts you for your device’s password (i.e: The password you use to login to your macOS Desktop). Is that intentional? Kind of defeats the point no? I mean sure, now there’s no Password being transmitted, stored or presented to Github.com but still, all an attacker has to do is somehow be on my device and know my login password to my device right? Is that better or worse? 🤔

Our stupid fucking 🤬 cat 🐱 keeps pissing 🚽 everywhere in our house 🏠

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.

Radxa Expands SBC Lineup with ROCK 5T Featuring Dual 2.5GbE and Dual M.2 Slots
Radxa has introduced a Mini-ITX single-board computer designed for both consumer and industrial applications. Built around the Rockchip RK3588(J) processor, this SBC provides a broad set of interfaces, high-speed connectivity, and advanced multimedia capabilities. Unlike the ROCK 5B and ROCK 5B+, which use the same processor, the ROCK 5T is also designed for industrial applications

@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?

#qotd

Image

My Life in Weeks
Article URL: https://weeks.ginatrapani.org/

Comments URL: https://news.ycombinator.com/item?id=43061498

Points: 503

# Comments: 140 ⌘ Read more

Vaaman is a $180 reconfigurable board with an Efinix Trion T120 FPGA and Rockchip RK3399
The Vaaman is a reconfigurable edge computing platform, first seen in 2023. The CrowdSupply campaign has finally launched, offering a system that combines the flexibility of an FPGA with the processing power of a six-core ARM processor. Designed for real-time processing and hardware acceleration, Vaaman integrates an Efinix Trion T120 FPGA with 112k logic elements […\ … ⌘ Read more

You have a microwave oven at home, right?

You can type 3 and 0 for 30 seconds, 100 for a minute (shown as 1:00), or 200 for two minutes (2:00).

What would happen if you type 777 and Start?
A) Nothing
B) Self-destruction
C) Will run for 7 minutes and 77 seconds (boring!)

What about 7777 ?

hey! It’s looking nice

@lyse@lyse.isobeef.org Ouch 🤕

@sorenpeter@darch.dk Nice 😊

Added support for uploading images to to #Timeline

Image

When washing the dishes at the scouts I cut my hand open on the ladle. That piece of shit has a terrible burr.

DILDO was here.

On my blog: Free Culture Book Club — Cairn Wardens Guide, part 1 https://john.colagioia.net/blog/2025/02/15/cairn-2.html #freeculture #bookclub

@lyse@lyse.isobeef.org Bur I can’t think of what’s changed to cause this? 🧐

What exact feeds are we talking about that uses spaces instead of tabs or the T’s in timestamp?

Yes, it looks like some users are not lucky to be Dildo agents here …

@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.

is the whole chat about dildos? D:

Does Dildo browser support the DICT protocol?

@movq@www.uninformativ.de Hahahaha 🤣

@aelaraji@aelaraji.com “replies” 🤣

@lyse@lyse.isobeef.org Duplicates again where two days ago? I don’t see this anywhere (unless I’m blind!)

@lyse@lyse.isobeef.org Agree. I’m not sure we should lax the timestamp format at all IMO. What @xuu@txt.sour.is has found is kind of nuts haha 😆 However I do think we should relax the \t separator between <timestamp> and <content>. Let users use any valid whitespace here that isn’t a newline or carriage return.

I think the author is a bit out of their depth here. A linear feed isn’t quite what the author seems to be modelling in their view of the problems they observe and describe. A linear feed has a beginning and an end. You can (ideally client-side) sort it by Date, or by Subject like we do with our Twtxt clients. A Tree-structure isn’t what the author thinks either, this is more the structure that forms after you introducing some kind of “threading model”. The main problem with any kind of information system that tries to figure out algorithmically what you want to “see” is that type of interface has no start and no end. SO you end up with a “scroll of doom”.

Y’all crack me up.

it’s ok, you can confess to us, we don’t know your identity!

The article discusses the challenges posed by linear social media feeds, which often lead to disengagement and difficulty in prioritizing content from friends due to constant scrolling. The author proposes an alternative approach using a daily feed structure per day, which organizes posts by date, allowing for easier prioritization and reducing mindless scrolling.

Key Points:

1. Linear Feed Problem: Linear feeds present a long list of posts without prioritization, forcing users to scroll endlessly to catch up on friends’ content. This can lead to addiction and disengagement.

2. Proposed Alternative (Tree Structure): The daily feed structure organizes posts by day, enabling users to prioritize updates from friends who post infrequently while reducing scrolling effort.

3. Mastodon Experience: The author’s experience with Mastodon highlighted its effectiveness in allowing content prioritization and managing social media usage without dependency on algorithms.

4. Challenges and Considerations:

   • Implementation Challenges: Creating a daily feed system involves organizing content effectively and ensuring users can prioritize posts.
     
   • Platform Support: Current platforms may not have APIs conducive to such changes, making it difficult to implement without significant technical changes.
     
   • Engagement Metrics: The impact on engagement metrics needs to be considered, as traditional metrics might be misinterpreted in a tree structure.
     

5. Potential Applications Beyond Social Media: This approach could empower users by giving control over content consumption and aiding in balancing social media use without overwhelming them with information.

6. Future Directions: The author hopes for improvements in alternative platforms’ feed systems and engagement metrics, potentially through more interactive content models or changes in APIs.

In conclusion, the article emphasizes the importance of providing users with control over their content consumption, moving away from linear feed

What exactly is a linear feed? 🤔

We were wrong about GPUs
Article URL: https://fly.io/blog/wrong-about-gpu/

Comments URL: https://news.ycombinator.com/item?id=43053844

Points: 509

# Comments: 328 ⌘ Read more

On my blog: Toots 🦣 from 02/10 to 02/14 https://john.colagioia.net/blog/2025/02/14/week.html #linkdump #socialmedia #quotes #week

On my blog: Toots 🦣 from 02/10 to 02/14 https://john.colagioia.net/blog/2025/02/14/week.html #linkdump #socialmedia #quotes #week

This year for #ilovefs I also want to thank @lenovous@lenovous for selling Laptops with GNU/Linux in Portugal!

@eapl.me@eapl.me I like this idea. Another option would be to show a limited number of posts, with an option to see the omitted ones by user. Either way, I wonder how well that works with threading.

@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!?

Image

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.

Now I just have to remember to tag people in replays ✍

… And, HOLLY!! infinite scrolling is real!! 👀

@movq@www.uninformativ.de I can relate to that. :-/

I just did and things are working wonderfully well now and I’m in love with how profile views are layed out! 👌 Thank you!

ok, sounds like a ‘large’ project to me.
Is it more an API (more oriented to developers), more oriented to UI/UX/Frontend? Perhaps both?

I’d go with prologic’s advice of measuring and prioritizing. Perhaps you have a budget or at least something like “let’s see how far can we reach in 6 months”, and possibly you won’t finish in the time you have (just guessing).

Something that has helped me was defining “Why do you we want to refactor this project?”.
Could it be to make it compile on newer versions, or making it easier to grow and scale, or perhaps they are trying to sell that product to another company. Every reason has a different path, IMO.

Thanks @prologic@twtxt.net @eapl_en@eapl.me @lyse@lyse.isobeef.org ! I take note

@aelaraji@aelaraji.com You can update the package 😀

I’ve learned that I can live without @kde@kde but I’m not able to live without #konsole, so… my first ❤️ of this year’s #ilovefs goes to the lovely Konsole and specially The Konsole Developers!

https://konsole.kde.org/

Image

@andros@twtxt.andros.dev My first point of advice is to stop everything and measure all the important critical user journeys. Design and Build Service Level Objectives for each and every part of the system you can find that any user cares about.

2024-08-04T11:24:34Z was the last occurrence of this.

@bender@twtxt.net @lyse@lyse.isobeef.org This bug was fixed back in September last year. But the brackets still appear in my current feed. is that what the issue is? 🤔

@lyse@lyse.isobeef.org @andros@twtxt.andros.dev Are we talking about yarnd here? Hmm? 🤔 I’ve thought about a “read flag” but I just haven’t bothered so far…

@johanbove@johanbove.info And what are the results so far? 🤔

The cache is only suppose to be for 120s though, but I reckon the caching layer is just stupid? 🤔 (and maybe buggy)?

I need to understand how the caching is at play here at the edge. I hit CTRL+R on @mckinley@twtxt.net’s OP to get the right subject reply after poking at the underlying HTML elements on the page.

@bender@twtxt.net To be fair, I do this in my “spare time” 😅

@mckinley@twtxt.net Ahh. I think this is some kind of weird caching issue at my edge! 😱

(Updated) NanoKVM-USB: 4K HDMI Loopback, USB 3.0, and Integrated Keyboard/Mouse Control
This month, Sipeed unveiled the NanoKVM-USB, described as a compact and low-cost device designed to simplify the operation and management of multiple systems. The Sipeed Wiki pages indicate that this device eliminates the need for dedicated keyboards, mice, or monitors. It allows users to perform operations graphically through the Chrome browser on a single computer,

M5Stack ASR Unit with CI 03T for Offline Voice Recognition in Smart Devices for $7.50
M5Stack recently launched the ASR Unit, which is an offline voice recognition module incorporating the CI-03T AI offline voice module. It is designed for applications that require speech recognition, voiceprint detection, and voice enhancement without relying on cloud-based processing. The product page for the CI-03T is in Chinese, but it describes the module as a

I can’t. I use Windows 3.11 and do not use the Dildo browser …

@mckinley@twtxt.net I’m worried we’re really approaching a point where we need to adapt the hashing algorithm and expand the no. of bits. Is it at all possible something else is going on here though? 🤞

@lyse@lyse.isobeef.org True, but we should also consider building tolerant “systems” 😉

@algorave.dk@algorave.dk Hello 👋

The project is a POC (Proof of Concept) that went into production and the company has customers who are using it. The developers had been working for several years, without testing, structure, isolation and so on. The company hired me to transform the project into a real product. There are in my hands 422 python files to transform that they beg me a refactore, architecture and testing. Every developer’s bad dream.
My first step is to read and understand the tree because there are apps inside other apps call each other. I am very determined to work on a new repository.

Anyone can push updates to the doge.gov website
Article URL: https://www.404media.co/anyone-can-push-updates-to-the-doge-gov-website-2/

Comments URL: https://news.ycombinator.com/item?id=43045835

Points: 503

# Comments: 348 ⌘ Read more

Thanks you very much! I have fixed it. 🙌

Learn SQL by solving crimes. I want to highlight it as a teacher and a developer, it’s extremely well done.
https://www.sqlnoir.com/
#sql

#Clima: “A UE ateou o fogo e não pode esperar que outros países sejam os bombeiros”

(WWF quer mais da UE)

Excertos:

“As falhas que a UE tem vindo a cometer, alegam os autores do relatório, prejudicam os esforços de descarbonização e, denunciam ainda, incluem “subsídios aos combustíveis fósseis, licenças gratuitas para poluir para a indústria pesada ao abrigo do regime comunitário de comércio de licenças de emissão, a isenção de impostos para a aviação comercial

On my blog: Real Life in Star Trek, Aquiel https://john.colagioia.net/blog/2025/02/13/aquiel.html #scifi #startrek #closereading

1st thought… Run!

Well, I’ve heard you have plenty of experience with Unit Testing and TDD. Perhaps designing a few tests before refactoring?

I’ve heard of Snapshot testing, but have never tried it: https://github.com/spatie/phpunit-snapshot-assertions

Also, what kind of refactor are you trying to do?

@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). ;-)

Have you ever had to refactor a project that was not documented? Any suggestions?

HTMX is fine! You can add dynamic sections with a simple endpoint. It is better that JavaScript.

I think it is not easy to implement, you need a database. Timeline is an elegant solution: read and sort.

Privacy Pass Authentication for Kagi Search
Article URL: https://blog.kagi.com/kagi-privacy-pass

Comments URL: https://news.ycombinator.com/item?id=43040521

Points: 501

# Comments: 184 ⌘ Read more

that’s a fair point.

Perhaps, since Twitter in 2006 never implemented read flags, every derivative microblogging system never saw that as an expected feature. This is curious because Twitter started with SMS, where on our phones we can mark messages as read or unread.
I think it all comes from the difference between reading an email (directed to you) vs. reading public posts (like a blog or a ‘wall,’ where you don’t mark posts as read). It’s not necessary to mark it as ‘read’, you just jump over it.

Reading microblogging posts in an email program is not common, I think, and I haven’t really used it, so I cannot say how it works, and whether it would be better for me or not.
However, I’ve used Thunderbird as a feed reader, and I understand the advantages when reading blog posts.

About read flags being simple, well… we just had a discussion this morning about how tracking read messages would require a lot of rethinking for clients such as timeline where no state is stored. Even considering some kind of ‘notification of unread messages or mentions’ is not expected for those minimalist client, so it’s an interesting compromise to think about.

Hahahaha, this is brilliant! :‘-D https://denmarkification.com/

Exactly, @bender@twtxt.net, just like yours and prologic’s, too. :-( Subsequent Brackets Considered Harmful™.

Testing the limits of our new 5G internet connection at home with pushing 1.5GB docker images into the cloud a bunch of times day…

MINIX NGC-NR660 Mini PC with High-Speed 2.5GbE Networking and Triple Display Support
MINIX has recently launched the NGC-NR660, a compact yet powerful Mini PC featuring an AMD Ryzen 5 6600H processor and AMD Radeon 660M graphics. Designed for multitasking, gaming, and productivity, this system supports triple display output, 8K Ultra HD resolution, and dual 2.5GbE RJ45 ports for high-speed wired connectivity. The NGC-NR660 is equipped with 16GB

@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.

Linear feeds are a dark pattern - A proposal for Mastodon
https://tilde.town/~dzwdz/blog/feeds.html

I’ve polished the CSS style a bit, you can try it here: https://eapl.me/treed/