Searching txt.sour.is

Twts matching #17
Sort by: Newest, Oldest, Most Relevant
golem-de
feeds.twtxt.net
 (41w ago)

(g+) Arbeit: Wann ist der richtige Zeitpunkt zur ProjektĂŒbergabe?
Bei Herzensprojekten fĂ€llt der Abschied oft schwer. Trotzdem ist eine Übergabe zum richtigen Zeitpunkt wichtig - fĂŒr Entwickler und fĂŒr das Projekt. Ein Ratgebertext von Jakob Rufus Klimkait ( Arbeit, CRM)

Image

⌘ Read more

​ Read More
golem-de
feeds.twtxt.net
 (41w ago)

PrÀventive Fahndung mit PrismX: Der Radikalisierung per KI zuvorkommen
Das KI-Tool PrismX eines indischen Studenten analysiert Postings in sozialen Medien und erstellt eine RisikoeinschĂ€tzung fĂŒr die Radikalisierung einer Person. Ein Bericht von Lars Lubienetzki ( Tools, KI)

Image

⌘ Read more

​ Read More
golem-de
feeds.twtxt.net
 (41w ago)

(g+) Der vernetzte Arbeitsplatz: Wie MCP die Arbeit mit KI-Agenten verÀndert
MCP ist ein bemerkenswertes Protokoll, das die Schnittstelle zwischen verschiedenen KI-Modellen standardisiert: Wir erklÀren, wie man es sinnvoll nutzen kann. Ein Praxistest von Markus Kammermeier ( KI, API)

Image

⌘ Read more

​ Read More
lyse
lyse.isobeef.org
 (41w ago)
↳ In-reply-to » @itsericwoodward @bender this is vaguely concerning...does yarn refresh feeds every minute or two? or is there some special "notify twtxt.net to refresh my feed" that i don't know about

@zvava@twtxt.net yarnd fetches the feeds roughly every ten minutes:

grep twtxt.net www/logs/twtxt.log | cut -d ' ' -f1 | tail -n 20
2025-10-04T07:00:45+02:00
2025-10-04T07:10:26+02:00
2025-10-04T07:22:43+02:00
2025-10-04T07:30:45+02:00
2025-10-04T07:40:48+02:00
2025-10-04T07:52:59+02:00
2025-10-04T08:00:07+02:00
2025-10-04T08:13:33+02:00
2025-10-04T08:23:13+02:00
2025-10-04T08:31:22+02:00
2025-10-04T08:41:29+02:00
2025-10-04T08:53:25+02:00
2025-10-04T09:03:31+02:00
2025-10-04T09:11:42+02:00
2025-10-04T09:23:11+02:00
2025-10-04T09:29:49+02:00
2025-10-04T09:36:17+02:00
2025-10-04T09:46:33+02:00
2025-10-04T09:58:40+02:00
2025-10-04T10:06:54+02:00

I suspect that the timing was just right. Or wrong, depending on how you’re looking at it. ;-)

​ Read More
macrumors
feeds.twtxt.net
 (41w ago)

Best Apple Deals of the Week: Apple Watch SE 2 Hits Ultra Low $179 Price, Plus Early Prime Day Deals
We’re gearing up for big Prime Day deals over the next few days, and this week saw multiple early Prime Day discounts arriving for iPhone 17 cases, the second generation Apple Watch SE, and more.

Image

_Note: MacRumors is an affiliate partner with some of these vendors. When you click a link and make a purch 
 ⌘ Read more

​ Read More
lwn-net
feeds.twtxt.net
 (41w ago)

[$] LWN.net Weekly Edition for October 2, 2025
Inside this week’s LWN.net Weekly Edition:

  • Front: Fedora and AI; Linting kernel Rust; openSUSE Leap 16; mmap() file operation; 6.17 statistics; dirlock.

  • Briefs: Bcachefs removal; Alpine /usr merge; F-Droid; Fedora AI policy; OpenSUSE Leap 16; PostgreSQL 18; Radicle 1.5.0; Quotes; 


  • Announcements: Newsletters, conferences, security updates, patches, and more. ⌘ Read more

​ Read More
bender
twtxt.net
 (41w ago)

@aelaraji@aelaraji.com, I mean to follow up here on the brief exchange we had on irc.mills.io, but I forgot. Never too late, so here it goes:

18:16 <aelaraji> quark 🙏 much appreciated but it won't be necessary, since there isn't much to miss out on in most of  where I hang out, so I could just disconnect and spare everyone else the noise 
18:17 *** aelaraji (aelaraji@776014f5a3edd32f1ed19658b7b85c8c655945b0feacaedd92fe60e61a3c0ae2) has quit (/ME goes "yeeeeet..!")
18:18 <quark> No noise for me. 
18:18 <quark> It’s all good. 
18:18 <quark> What would IRC be without on/offs?
18:19 <quark> Preeeety boring!
18:19 <quark> Ah, he was gone. 
18:19 <quark> Well, I will twtxt this to him.  LOL.

​ Read More
os-x-daily
feeds.twtxt.net
 (42w ago)

iOS 26.0.1 Update Released to Fix Various iPhone 17 Issues, & Blank Screen Icons
Apple has released the first update for iOS 26.0.1, which includes a handful of bug fixes specifically aimed at the new iPhone 17 lineup, as well as addressing an issue for all devices where Home Screen icons can appear blank after using various Liquid Glass customization settings, and another issue where VoiceOver might disable itself 
 [Read More](https://osxdaily.com/2 
 ⌘ Read more

​ Read More
linux_gizmos
feeds.twtxt.net
 (42w ago)

DietPi September 2025 Update Brings Faster Backups and Roon Server Early Access
The September 20th release of DietPi v9.17 introduces smaller and more efficient system images, faster backups with reduced disk usage, and a new toggle for Roon Server’s early access builds. The update also addresses SPI bootloader flashing issues on Rockchip devices, improves Raspberry Pi sound card handling, and includes multiple bug fixes across tools and [
] ⌘ Read more

​ Read More
lyse
lyse.isobeef.org
 (43w ago)
↳ In-reply-to » is there consensus on what characters should(n't) be allowed in nicks? i remember reading somewhere whitespace should not be allowed, but i don't see it in the spec on twtxt.dev — in fact, are there any other resources on twtxt extensions outside of twtxt.dev?

@zvava@twtxt.net @movq@www.uninformativ.de I’m not entirely sure about the spaces, but maybe they were omitted to simplify parsing of mentions in the form of @<nick url>. If the next token after the @<nick does not look like a URL, it’s not a mention but regular text. This is just wild guessing, though.

Looking at the regex and tests in the original twtxt reference implementation seems to confirm that theory in the sense as it relies on whitespace as the delimiter:

Image

Another thing about nicks is that the original twtxt reference implementation converts nicks to all lowercase:

Image

You probably know this already, the original twtxt file format specification can be found here: https://twtxt.readthedocs.io/en/latest/user/twtxtfile.html

As for extensions, I don’t know of anything outside of twtxt.dev that has actually been (partially) implemented. However, there is also the issue tracker of the official reference implementation. You might wanna dig through that. For example, there is an alternative suggestions of multiline messages: https://github.com/buckket/twtxt/issues/157

​ Read More
hashtable
feeds.twtxt.net
 (43w ago)

20 ans !
Eh oui, cela fait 20 ans dĂ©jà ! C’est en septembre 2005 que ce blog vit le jour, recueil de notes et de remarques sur une actualitĂ© dĂ©jĂ  assez liberticide Ă  l’époque. Petit-Ă -petit, les notes sont devenues plus longues, les billets plus construits, illustrĂ©s, puis relayĂ©s au fil des annĂ©es par diffĂ©rents supports numĂ©riques. De quelques [
] ⌘ Read more

​ Read More
lyse
lyse.isobeef.org
 (45w ago)
↳ In-reply-to » i went to a rilo kiley concert the other day and it was so special to me... i teared up at some of the songs but when "a better son/daughter" came on, i full on cried. what an amazing experience.

@kat@yarn.girlonthemoon.xyz Ten stories or more are already very tall in my books. Not sure at which height I would start calling high rise buildings sky scrapers, but Wikipedia suggests around 150 meters, depending on region.

Oh, I just found

Image

and this really does not look all that high. I thought that this would be at least 50 or 100 meters up. I was completely wrong. :-D

​ Read More
movq
www.uninformativ.de
 (1y ago)

Saw this on Mastodon:

https://racingbunny.com/@mookie/114718466149264471

18 rules of Software Engineering

  1. You will regret complexity when on-call
  2. Stop falling in love with your own code
  3. Everything is a trade-off. There’s no “best” 3. Every line of code you write is a liability 4. Document your decisions and designs
  4. Everyone hates code they didn’t write
  5. Don’t use unnecessary dependencies
  6. Coding standards prevent arguments
  7. Write meaningful commit messages
  8. Don’t ever stop learning new things
  9. Code reviews spread knowledge
  10. Always build for maintainability
  11. Ask for help when you’re stuck
  12. Fix root causes, not symptoms
  13. Software is never completed
  14. Estimates are not promises
  15. Ship early, iterate often
  16. Keep. It. Simple.

Solid list, even though 14 is up for debate in my opinion: Software can be completed. You have a use case / problem, you solve that problem, done. Your software is completed now. There might still be bugs and they should be fixed – but this doesn’t “add” to the program. Don’t use “software is never done” as an excuse to keep adding and adding stuff to your code.

​ Read More