Searching We.Love.Privacy.Club

Twts matching #4
Sort by: Newest, Oldest, Most Relevant
docker_blog
feeds.twtxt.net
 (17w ago)

IBM Granite 4.0 Models Now Available on Docker Hub
Developers can now discover and run IBM’s latest open-source Granite 4.0 language models from the Docker Hub model catalog, and start building in minutes with Docker Model Runner. Granite 4.0 pairs strong, enterprise-ready performance with a lightweight footprint, so you can prototype locally and scale confidently. The Granite 4.0 family is designed for speed, flexibility,… ⌘ Read more

⤋ Read More
os-x-daily
feeds.twtxt.net
 (17w ago)

Deals: AirTags 4-pack for $65, M3 iPad Air from $449, & More
AirTags are super useful personal trackers with many uses from tracking a bag, purse, dog, cat, luggage, backpack, car keys, package, bike, car, or just about anything else you can imagine wanting to keep an eye on through the Find My network. Amazon is currently offering the AirTag 4-pack for just $65 ($16 per AirTag), … [Read More](https://osxdaily.com/2025/10/06/deals-airtags-4-pack-for-65-m3-ipad-air-from-449-m … ⌘ Read more

⤋ Read More
Kulpin_net
feeds.twtxt.net
 (18w ago)

5. Memoriálny volejbalový turnaj Aleksandra Zavaroša – Saleho
V sobotu 4. októbra sa v Kulpíne uskutočnil piaty ročník Memoriálneho volejbalového turnaja Aleksandra Zavaroša – Saleho, venovaný pamiatke mladého volejbalistu, ktorý tragicky zahynul v roku 2020. Podujatie zorganizoval Volejbalový klub Kulpín na znak úcty a spomienky na svojho bývalého spoluhráča. Deň sa začal tichou spomienkou na cintoríne v Kulpíne, kde sa členovia klubu, priatelia a rodina po … ⌘ Read more

⤋ Read More
cncf
feeds.twtxt.net
 (18w ago)

KubeCon + CloudNativeCon North America 2025 Co-Located Event Deep Dive: Kubernetes on Edge Day
The inaugural Edge Day launched as a co-located event at KubeCon + CloudNativeCon EU in 2022, recognizing that data at the edge is here to stay. Once called the ‘Internet of Things’ and later ‘Industry 4.0,’… ⌘ Read more

⤋ Read More
Phys_org
feeds.twtxt.net
 (18w ago)

Why some human GII.4 noroviruses are better than others at infecting cells
Human noroviruses, GII.4 strains in particular, are the chief drivers of acute viral gastroenteritis around the world, a condition for which there are no vaccines or antivirals. Understanding how these viruses enter cells in the gut, a first step toward developing an infection, can lead to effective therapeutics. ⌘ Read more

⤋ Read More
itsericwoodward
itsericwoodward.com
 (19w ago)
↳ In-reply-to » @itsericwoodward any news about this? I am, at the very least, curious!

@bender@twtxt.net Thanks for asking!

So, I’ve been working on 2 main twtxt-related projects.

The first is small Node / express application that serves up a twtxt file while allowing its owner to add twts to it (or edit it outright), and I’ve been testing it on my site since the night I made that post. It’s still very much an MVP, and I’ve been intermittently adding features, improving security, and streamlining the code, with an eye to release it after I get an MVP done of project #2 (the reader).

But that’s where I’ve been struggling. The idea seems simple enough - another Node / express app (this one with a Vite-powered front-end) that reads a public twtxt file, parses the “follow” list, grabs (and parses) those twtxt files, and then creates a river of twts out of the result. The pieces work fine in seclusion (and with dummy data), but I keep running into weird issues when reading real-live twtxt files, so some twts come through, while others get lost in the ether. I’ll figure it out eventually, but for now, I’ve been spending far more time than I anticipated just trying to get it to work end-to-end.

On top of it, the 2 projects wound up turning into 4 (so far), as I’ve been spinning out little libraries to use across both apps (like https://jsr.io/@itsericwoodward/fluent-dom-esm, and a forthcoming twtxt helper library).

In the end, I’m hoping to have project 1 (the editor) into beta by the end of October, and project 2 (the reader) into beta sometime after that, but we’ll see.

I hope this has satisfied your curiosity, but if you’d like to know more, please reach out!

⤋ Read More
docker_blog
feeds.twtxt.net
 (19w ago)

MCP Horror Stories: The Drive-By Localhost Breach
This is Part 4 of our MCP Horror Stories series, where we examine real-world security incidents that expose the devastating vulnerabilities in AI infrastructure and demonstrate how Docker MCP Gateway provides enterprise-grade protection against sophisticated attack vectors. The Model Context Protocol (MCP) has transformed how developers integrate AI agents with their development environments. Tools like… ⌘ Read more

⤋ Read More
lyse
lyse.isobeef.org
 (19w ago)
↳ In-reply-to » (#altkl2a) Here is just a small list of things™ that I'm aware will break, some quite badly, others in minor ways:

@prologic@twtxt.net I know we won’t ever convince each other of the other’s favorite addressing scheme. :-D But I wanna address (haha) your concerns:

  1. I don’t see any difference between the two schemes regarding link rot and migration. If the URL changes, both approaches are equally terrible as the feed URL is part of the hashed value and reference of some sort in the location-based scheme. It doesn’t matter.

  2. The same is true for duplication and forks. Even today, the “cannonical URL” has to be chosen to build the hash. That’s exactly the same with location-based addressing. Why would a mirror only duplicate stuff with location- but not content-based addressing? I really fail to see that. Also, who is using mirrors or relays anyway? I don’t know of any such software to be honest.

  3. If there is a spam feed, I just unfollow it. Done. Not a concern for me at all. Not the slightest bit. And the byte verification is THE source of all broken threads when the conversation start is edited. Yes, this can be viewed as a feature, but how many times was it actually a feature and not more behaving as an anti-feature in terms of user experience?

  4. I don’t get your argument. If the feed in question is offline, one can simply look in local caches and see if there is a message at that particular time, just like looking up a hash. Where’s the difference? Except that the lookup key is longer or compound or whatever depending on the cache format.

  5. Even a new hashing algorithm requires work on clients etc. It’s not that you get some backwards-compatibility for free. It just cannot be backwards-compatible in my opinion, no matter which approach we take. That’s why I believe some magic time for the switch causes the least amount of trouble. You leave the old world untouched and working.

If these are general concerns, I’m completely with you. But I don’t think that they only apply to location-based addressing. That’s how I interpreted your message. I could be wrong. Happy to read your explanations. :-)

⤋ Read More
docker_blog
feeds.twtxt.net
 (20w ago)

Silent Component Updates & Redesigned Update Experience
Following on from our previous initiative to improve how Docker Desktop delivers updates, we are excited to announce another major improvement to how Docker Desktop keeps your development tools up to date. Starting with Docker Desktop 4.46, we’re introducing automatic component updates and a completely redesigned update experience that puts your productivity first. Why We’re… ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (22w ago)

ProcessOne: Spotify’s Direct Messaging Gambit

Image

Last week, Spotify quietly launched direct messaging across its platform in selected areas, allowing users to share tracks and playlists through private conversations within the app. The feature was rolled out with mini … ⌘ Read more

⤋ Read More
movq
www.uninformativ.de
 (23w ago)

I’ve got a prototype of my hardcopy simulator going. I’m typing on the keyboard and the “display” goes to the printer:

https://movq.de/v/56feb53912/s.png

https://movq.de/v/235c1eabac/MVI_8810.MOV.mp4

The biiiiiiiiiig problem is that the print head and plastic cover make it impossible to see what’s currently being printed, because this is not a typewriter. This means: In order to see what I just entered, I have to feed the paper back and forth and back and forth … it’s not ideal.

I got that idea of moving back/forth from Drew DeVault, who – as it turned out – did something similar a few years back. (I tried hard to read as little as possible of his blog post, because figuring things out myself is more fun. But that could mean I missed a great idea here or there.)

But hey, at least this is running on my Pentium 133 on SuSE Linux 6.4, printer connected with a parallel cable. 😍

(Also, yes, you can see the printouts of earlier tests and, yes, I used ed(1) wrong at one point. 🤪 And ls insisted on using colors …)

⤋ Read More
movq
www.uninformativ.de
 (24w ago)
↳ In-reply-to » Bloody AI clowns:

Here’s an interesting thought/angle on this topic:

gemini://gemini.conman.org/boston/2025/08/21.1

A further check showed that all the network blocks are owned by one organization—Tencent [4]. I’m seriously thinking that the CCP (Chinese Communist Party) encourage this with maybe the hope of externalizing the cost of the Great Firewall [5] to the rest of the world.

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (24w ago)

The XMPP Standards Foundation: MongooseIM 6.4 - Simplified and Unified
MongooseIM is a scalable and efficient instant messaging server. It implements the open, proven, extensible and constantly evolving XMPP protocol, which is an excellent choice when it comes to instant messaging. To communicate with other XMPP entities, the server uses three main types of interfaces, listed in the table below.

XMPP InterfacePurposeConnection typeReworked in v … ⌘ Read more

⤋ Read More