I agree. finding good writings on architecture is hard to find. I used to read architecture reviews over on the high scalability blog. i suspect the reason why is that the arch is how the big tech companies can build moats around their bases. I know in AWS world it only goes as far as how to nickle and dime you to death.

I have the books but they don’t grow much more past interview level.

@bender@twtxt.net Sorry to disappoint (again): https://blogs.nasa.gov/planetarydefense/2025/02/24/latest-calculations-conclude-asteroid-2024-yr4-now-poses-no-significant-threat-to-earth-in-2032-and-beyond/

@falsifian@www.falsifian.org Neat, I got the principle, so mission accomplished. :-)

I have configured my vim to use a tab width of four. So, I noticed that especially https://www.falsifian.org/blog/2021/06/04/catalytic/reachability_with_stack.cc (but also partially the other C++ file) mixes tabs and spaces for indentation. :-)

Chromium Ozone/Wayland: the last mile stretch
Lets start with some context, the project consists of implementing, shipping and maintaining native Wayland support in the Chromium project. Our team at Igalia has been leading the effort since it was first merged upstream back in 2016. For more historical context, there are a few blog posts and this amazing talk, by my colleagues Antonio Gomes and Max Ihlenfeldt, presented at last year’s Web Engines Hackfest. Especially due to the Lacros pr … ⌘ Read more

@lyse@lyse.isobeef.org I am a big fan of “obvious” math facts that turn out to be wrong. If you want to understand how reusing space actually works, you are mostly stuck reading complexity theory papers right now. Ian wrote a good survey: https://iuuk.mff.cuni.cz/~iwmertz/papers/m23.reusing_space.pdf . It’s written for complexity theorists, but some of will make sense to programmers comfortable with math. Alternatively, I wrote an essay a few years ago explaining one technique, with (math-loving) programmers as the intended audience: https://www.falsifian.org/blog/2021/06/04/catalytic/ .

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.

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/

@jost@jost.sdfeu.org Yeah, this AI crap is a big reason not to blog.

@andros@twtxt.andros.dev The article is a good reminder of the true blogging mindset. But let’s try to think beyond. 2 ideas: (1) writing “forces clarity, structures your thoughts, sharpens your perspective”. But it also generates thoughts in the sense of Heinrich von Kleist (1805). (2) You’re writing for “the future you, one right person, one day” but you are also writing for the AI. The idea of AI as an audience.

Excellent article where you reflect on why it is important to write in your blog, even knowing that nobody will read it.
https://andysblog.uk/why-blog-if-nobody-reads-it/
At least this article does.

https://lime360.bearblog.dev/never-blogged-in-a-while-i-guess/

https://lime360.bearblog.dev/never-blogged-in-a-while-i-guess/

https://lime360.bearblog.dev/never-blogged-in-a-while-i-guess/

email threats with hidden text salting https://blog.talosintelligence.com/seasoning-email-threats-with-hidden-text-salting/

Neil’s blog https://neilzone.co.uk/

Neil’s blog

Terrorism and Evil: https://blogs.cardiff.ac.uk/openfordebate/terrorism-and-evil/

this is epic https://lmnt.me/blog/how-to-make-a-damn-website.html

@kat@yarn.girlonthemoon.xyz i’m reading this and i already have a gts server that i could secure with this but i’m thinking it’d be best for most of my public sites https://ovelny.sh/blog/a-complete-guide-for-your-gotosocial-server/

Enabling and Configuring Threat Intelligence and Detections https://www.leveleffect.com/blog/home-lab-enabling-and-configuring-threat-intelligence-and-detections

Unmasking the hidden gems of Void Linux https://animeshz.github.io/site/blogs/void-linux.html

I would like to share my lastest article about #twtxt on my blog: https://programadorwebvalencia.com/twtxt-la-red-social-en-texto-plano-descentralizada-y-minimalista/ . Attention! It is a Spanish

@prologic@twtxt.net Yes! then there was this fun breaker of an article but hey, I ain’t doing it for security 😆 so I’ll just keep on keeping on.

Moin @arne@uplegger.eu, herzlich willkommen! Ich bin gerade auf https://uplegger.eu/blog/popelfinger gestoßen und war sofort sehr begeistert. :-D Mal sehen, ob ich die anderen an einem der Feiertage davon überzeugt bekomme, das mal auszuprobieren. :-)

Das Spiel der 20 Felder: Die möglichen Regeln des 4.600 Jahre alten Spiels mit einem Entwurf für einen modernen Spielplan.

after thinking and researching about it, yep, I agree that WebFinger is a good idea.

For example reading here: https://bsky.social/about/blog/4-28-2023-domain-handle-tutorial
I wasn’t considering some scenarios, like multiple accounts for a single domain (See ‘How can I set and manage multiple subdomain handles?’ in the link above)

@lyse@lyse.isobeef.org Mostly small and simple stuff, like cable management, headphone rests, pill dispensers (that I didn’t end up using), … The most elaborate thing I made was that contraption for my keyboard, which is a bit hard to explain right now, so here’s some photos:

I didn’t end up using that, either. 🥴

In general, I print very little. So little that some of my supplies have simply gone bad, like that “3D LAC” (sprayable glue).

@aelaraji@aelaraji.com Yeah, I saw that when googling the issue. I’m on Linux, there are no DLLs to swap. I could use an older version indeed. 🤔 Let’s see if I can find some better alternative first. (Let’s face it, Blender is hard to use.)

although the only #Go things I’m running in there are a WriteFreely blog and the Saltyd #SaltyIM broker … each running in separate #FreeBSD #jail, those are still running the 14.1-Release (at the moment) anyways.

Behold … “Marginalia” ! My new favorite search engine!! And I have @mattof to thank for this find. Here’s their Blog post about it since I don’t think I could do a better job describing what it is. but, tl;dr: it’s a #smallweb focused search engine.

I’m angry, I see too many blog I followed removing their RSS/atom feed. Why???

@prologic@twtxt.net i think we talked about it before blogs were removed

Regarding the blog post itself, there’s nothing of any substance here except an acknowledgment of open network(s) being a good thing.

This is so neat.

https://emilyliu.me/blog/open-network

When yarn used to have blogs I thought something like this would be a great feature. Having the blog comments tied to a twtxt subject for the blog post.

@eapl.me@eapl.me here are my replies (somewhat similar to Lyse’s and James’)

1. Metadata in twts: Key=value is too complicated for non-hackers and hard to write by hand. So if there is a need then we should just use #NSFS or the alt-text file in markdown image syntax ![NSFW](url.to/image.jpg) if something is NSFW

2. IDs besides datetime. When you edit a twt then you should preserve the datetime if location-based addressing should have any advantages over content-based addressing. If you change the timestamp the its a new post. Just like any other blog cms.

3. Caching, Yes all good ideas, but that is more a task for the clients not the serving of the twtxt.txt files.

4. Discovery: User-agent for discovery can become better. I’m working on a wrapper script in PHP, so you don’t need to go to Apaches log-files to see who fetches your feed. But for other Gemini and gopher you need to relay on something else. That could be using my webmentions for twtxt suggestion, or simply defining an email metadata field for letting a person know you follow their feed. Interesting read about why WebMetions might be a bad idea. Twtxt being much simple that a full featured IndieWeb sites, then a lot of the concerns does not apply here. But that’s the issue with any open inbox. This is hard to solve without some form of (centralized or community) spam moderation.

5. Support more protocols besides http/s. Yes why not, if we can make clients that merge or diffident between the same feed server by multiples URLs

6. Languages: If the need is big then make a separate feed. I don’t mind seeing stuff in other langues as it is low. You got translating tool if you need to know whats going on. And again when there is a need for easier switching between posting to several feeds, then it’s about building clients with a UI that makes it easy. No something that should takes up space in the format/protocol.

7. Emojis: I’m not sure what this is about. Do you want to use emojis as avatar in CLI clients or it just about rendering emojis?

Apparently, when faculty use AI to create assignments, it’s a “productivity gain.” But when students use AI to complete assignments, it’s “cheating.” (https://opencontent.org/blog/archives/7508)

https://blog.terminal.pink/

Windows Endpoint Forensics Readiness Booster https://profero.io/blog/microsoft-windows-endpoint-forensics-readiness-booster

RDP artifacts | https://www.magnetforensics.com/blog/rdp-artifacts-in-incident-response/

Huh. I had long forgotten about text fragment URLs. Seems relevant for linking to discussions around linking to individual twtxt posts. https://alfy.blog/2024/10/19/linking-directly-to-web-page-content.html

Practical IR Active Directory | https://hardenedlinux.org/blog/2024-10-13-container-hardening-process/

Hardening containers | https://hardenedlinux.org/blog/2024-10-13-container-hardening-process/

@galegovski@vaporhole.xyz eu me referia ao blog, na página inicial do blog tem um resumo das postagens completas, geralmente o primeiro parágrafo.

Installing Devuan 3.1 and Migrating to Ceres | https://starbreaker.org/blog/tech/installing-devuan-31-migrating-ceres/index.html

Valeu pelo feedback @orahcio@vaporhole.xyz ! Você está falando do link na página inicial mesmo, ou no /blog? Na página inicial foi na unha mesmo.

@galegovski@vaporhole.xyz o blog tá show, bom saber do keepassxc (uso atualmente o pass). Você usa alguma ferramenta em específico pra deixar o início das postagens na página inicial?

@3r1c@3r1c.net I think I’m gonna like that blog. 😅 https://unixdigest.com/articles/is-the-madness-ever-going-to-end.html

MEU BLOG: https://www.galegovski.com/blog/

@3r1c@3r1c.net Woa! I love this blog’s format! _ it’s just perfect for reading from terminal…

No, json is overhead. I love twtxt for simplicity where blog is just text file and not several json files where fields are repeated…

flakes arent real https://jade.fyi/blog/flakes-arent-real/