@kiwu@twtxt.net Lately… A native mobile app for Salty.im 😅

👋 Looking for other interested folks to continue to evolve the development of Salty.im 🙏 I’ve been hard™ at work on the v2 branch and @doesnm.p.psf.lt@doesnm.p.psf.lt has been incredibly helpful so far. Be great ot have a few more folks to join us, some of the v2 highlights include:

• Double Ratchet by default.
  
• Group Chat (sender/client fan-out for now)
  
• Much better TUI with background agent.
  
• Mobile App coming soon™ (iOS in progress, Android next, same codebase)

@bender@twtxt.net Whwn do i see you start to use Salty IM more? 😅

Some pretty pics to illustrate the much improved reference Salty.im client, salty-chat.

Built a new refreshed landing page for Salty IM https://salty.im/ 🥳

Ich hab es jetzt endlich geschafft, diese alte Podcastdatei anzuhören, die ich auf meiner Platte fand. Omega-Tau 293 über Wasserstraßen und im Speziellen den Neckar. Total interessant. Ich bin bisher noch nie über diese Serie gestolpert und habe keine Ahnung, wie ich überhaupt zu der Datei kam. Leider ist der Podcast mittlerweile eingestellt, das TLS-Zertifikat der Website die Tage abgelaufen und die Folgenseite tot, aber die Audiodatei gibt’s noch: https://traffic.libsyn.com/secure/omegataupodcast/omegatau-393-wasserstrassen.mp3

@arne@uplegger.eu @movq@www.uninformativ.de Der reine Spielzeugladen im Nachbarort hat auch schon vor Jahren dicht gemacht. Online gibt’s das halt alles deutlich günstiger.

@arne@uplegger.eu Wer mir mit Werbung im Buch kommt, hat verschissen. 😂 Hatte ich kürzlich auch (in einem Roman von 2025), da wurde immer wieder sehr auffällig eine bestimmte Lokalität erwähnt. Ganz am Ende hab’ ich dann gesehen, dass auf den letzten paar Seiten diese Lokalität nochmal explizit einen „Flyer“ platziert hatte, das war also durchaus ein Werbedeal.

Nervt stark. Ich hab’ schon für das Buch gezahlt, da will ich nicht noch „angeworben“ werden. Dann mach’ lieber das Buch leicht teurer oder setz’ einen Spendenaufruf rein, wenn die Finanzen so knapp sind. 🤔

A KGB spy and a CIA agent meet up in a bar for a friendly drink

I have to admit, Im always so impressed by Soviet propaganda. You really know how to get people worked up,” the CIA agent says.

“Thank you,” the KGB says. “We do our best but truly, its nothing compared to American propaganda. Your people believe everything your state media tells them.

The CIA agent drops his drink in shock and disgust. Thank you friend, but you must be confused… Theres no propaganda in America.

im just a poor frontend developer qwq

@prologic@twtxt.net I too, self-host various services on a VPS (and considering buying a mini PC to keep at home instead).

I use most of it as a hosting platform for personal use only and as a remote development environment (I do share a couple of tools with a friend though).

But given the costant risks of DDoS, hacking, bots, etc. I keep any of my public facing resources purely static and on separate hosting providers (without lock-ins of course).

Lately, I began using homebrew PWAs with CouchDB as a sync database, this way I get a fantastic local-first experience and also have total control of my data, that also sync in a locally hosted backup instance in real-time.

Also, I was already aware of Salty.im, but what I’m thinking is a more feature complete solution that even my family can use quickly, Delta.chat with the new chatmail provider (self-hostable) might be the solution for my needs.

But I’m still thinking if it’s worth the trouble. I might just drop everything and only use safe channels to speak with them (free 24/7 family tech-support is easy to manage 😆).

Also, I’ll be waiting for the day you’ll share with us your story, I’m pretty curious about it!

@alexonit@twtxt.alessandrocutolo.it Yes well I’m pretty big on self-hosting. I’ve even tried to start a small business/company around it (but that’s another story for another day!) – Meanwhile I would encourage you to have a look at the work we’ve done in Salty.im 👌

@prologic@twtxt.net to clarify the i meant the ability to parse feeds using unix command line utilities, as a prinicpal of twtxtv1’s design. im not sure how feasible it is to build a simple feed reader out of common scripting utilities when hashing is in play, and;

i concede, it does make a lot of sense to fix up the hashing spec rather than completely supplant it at this point, just thinking about what the rewrite would be like is dreadful in and of itself x.x

@prologic@twtxt.net to clarify: i meant the ability to parse feeds using unix command line utilities, as a principal of twtxtv1’s design. im not sure how feasible it is to build a simple feed reader out of common scripting utilities when hashing is in play, and;

i concede, it does make a lot of sense to fix up the hashing spec rather than completely supplant it at this point, just thinking about what the rewrite would be like is dreadful in and of itself x.x

@prologic@twtxt.net the simplest thing to do is to completely forgo hashing anything because we are communicating using plain text files right now :3 while i agree hashes are incredibly helpful in the backend im not sure it has a place outside of it, it basically eliminates two core design principals of twtxt (human readability and integrating well with unix command line utilities) and makes new clients more difficult to build than it should be

@lyse@lyse.isobeef.org i dont mind if the hash is not backward compatible but im not sure if this is the right way to proceed because the added complexity dealing with two hash versions isnt justified

regular end users wont care to understand how twt hashes are formed, they just want to use twtxt! so i guess i could work in protecting users from themselves by disallowing post edits on old posts or posts with replies, but i’m not fond of this either really. if they want to break a thread, they can just delete the post (though i’ve noticed yarn handling post deletes dubiously…)

on activitypub i do genuinely find myself looking through several month or even year old posts sometimes and deciding to edit/reword them a little to be slightly less confusing, this should be trivial to handle on twtxt which is an infinitely simpler specification

im unable to figure out why bbycll is not generating posts hashes for @lyse@lyse.isobeef.org’s feed correctly (or at least different from the ones generated by yarn)

i’m pretty sure the timezone is stripped off the offset correctly (2025-09-14T12:45:00+02:00 → 2025-09-14T12:45:00Z) though messing with how the hash is generated i can’t get it to make one that matches…but all other hashes for all other feeds seem to be correct? does yarn use a different canonical url for lyse internally? is there a bug in the libraries im using? bwehhh

@prologic@twtxt.net im unsure how i feel about the hash v2 proposal, given it is completely backward incompatible with hash v1 it doesn’t really solve any of the problems with it. it only delays collisions, and still fragments threads on post edits

i skimmed through discussions under other the proposals — i agree humans are very bad at keeping the integrity of the web in tact, but hashes in done in this way make it impossible even for systems to rebuild threads if any post edits have occurred prior to their deployment

@bender@twtxt.net just a heads up im thinking of rewriting the database schema with hash v2 in mind >.<

we are now parsing and recursively fetching remote feeds somewhat successfully, gotta work on the media proxy and markdown way more, so so many fucky edgecases….my friend’s feed with like four posts parsed correctly so i tried this account’s feed and well now im not going to bed on time

edit: remaking demo video

we are now parsing and recursively fetching remote feeds somewhat successfully, gotta work on the media proxy and markdown way more, so so many fucky edgecases….my friend’s feed with like four posts parsed correctly so i tried this account’s feed and well now im not going to bed on time

im a 1000x developer

@lyse@lyse.isobeef.org retwts are a discovery feature! on federated platforms with no algorithm where you only ever see posts from accounts you explicitly follow, the element of “hey look at this!” helps users to find other accounts they might like organically

i agree quoting and replying forum-style is generally a much better way of doing things even though im a heathen and i revel in the dark patterns inspired by quote posts but when you have nothing to add and you just want to share a twt with your followers it’d be good to have a standardized way of linking to twt

at first i dismissed the idea of likes on twtxt as not sensible…like at all — then i considered they could just be published in a metadata field (though that field could get really unruly after a while)

retwts are plausible, as “RE: https://example.com/twtxt.txt#abcdefg”, the hash could even be the original timestamp from the feed to make it human readable/writable, though im extremely wary of clogging up timelines

i thought quote twts could be done extremely sensibly, by interpreting a mention+hash at the end of the twt differently to when placed at the beginning — but the twt subject extension requires it be at the beginning, so the clean fallback to a normal reply i originally imagined is out of the question — it could still be possible (reusing the retwt format, just like twitter!) but i’m not convinced it’s worth it at that point

is any of this in the spirit of twtxt? no, not in the slightest, lmao

@lyse@lyse.isobeef.org Ja, eine kleine Inventur vorab kann auch nicht schaden. Der Bestand an Erdankern, Heringen und Gaskartuschen ist durch mich die Tage schon wieder aufgestockt worden.
Wo das Gas bleibt weiß ich. Warum die Befestigungen immer weniger werden, obwohl wir durchzählen (!), ist mir unbekannt. Vielleicht sind wir im Zahlenraum von 1 bis 20 einfach nur noch sehr unsicher. 🤓

@arne@uplegger.eu Au, Zelturlaub klingt klasse! Bei mir ist es auch bald so weit, freu mich schon. Dank der Ausrüstungsüberprüfung im Materiallager haben wir demletzt festgestellt, dass gleich zwei Spinnen (so Metallketten, an denen die Jurtendächer hochgezogen werden) fehlen. Ein Probeaufbau – und sei es nur unter Laborbedingungen – lohnt sich in jedem Fall. Improvisieren zu können ist zwar von Vorteil, aber wenn es sich vermeiden lässt, fängt der Urlaub gleich ein wenig entspannter an. :-)

Heute im Support-Kanal: Schrödingers Laptop

… der Laptop fährt weder runter noch hoch …

Having some fun with SIRDS this morning.

What you should see: https://movq.de/v/dae785e733/disp.png

And the tutorial I used for my C program: https://www.ime.usp.br/~otuyama/stereogram/basic/index.html

@oloke@nghia.im can’t blame them for naming fumo before i figure out what fumo is

@nghialele@nghia.im Man, I wish I could watch Formula 1 on a regular basis again, but it has become expensive as fuck here. 🫤

@oloke@nghia.im the servers.guru is in my want to try list for a while, recently seen chunkserve want to throw dealz, might grab some haha

@oloke@nghia.im it’s extravm, im trying new provider (for me)

@oloke@nghia.im it’s nghia.lt

@oloke@nghia.im i’m reading about this Garage today, will watch this one for sure, promising, since those folks look like familiar with YunoHost ecosystem and French things

also found another things called Riak

https://docs.riak.com/riak/cs/2.1.1.1.html

@nghialele@nghia.im SAME HERE LOL i’m so pissed

@nghialele@nghia.im it’s great to see another Yarnd pod in the wild. Welcome!

@nghialele@nghia.im hello there nice to meet you! your site protection thing is super funny with the touhou theme lol

testing with a new meme

Zum Entsetzen aller Beteiligten, wie auch umstehender Personen und einiger schamfreier Gaffer, welche sich an jenem tosenden Unheil zu ergötzen vermochten, folgte nun des Wochensortiments schrecklichste Geißel: 𝕯𝖊𝖗 𝕸𝖔𝖓𝖙𝖆𝖌.

Und es sollten sich die Wolken teilen, um über ihnen nimmer endende Irrungen und Wirrungen an bovinem Fäkal und fremdgetriebener Lethargie zu erbrechen, auf dass sie zu erkennen gezwungen wären, welche Urkraft der irrealen Zusammenkunft letztlich Herrschaft über sie darstellen sollte: 𝕯𝖆𝖘 𝕭𝖎𝖑𝖉𝖙𝖊𝖑𝖊𝖋𝖔𝖓.

So zogen sie alsbald hin, zu tun wie ihnen geheißen, wohlgleich sie – diesem Schauerspiel trotzend – Trost suchten im einzigen ihnen sicher geglaubten Elixir, das dem Abgrund unter ihnen gleichend tiefschwarz glitzernd Erlösung oder mithin als Mindestmaß Linderung versprach, lag jenes doch in unmittelbarer Nähe befindlich hoffnungsschürend bereit:

K̸͓͙͖̥͗͛ä̷̯̼̤͔̈́f̵̧̿̋͒̈f̷̫̝̖̾̓c̸̛͔̀ḣ̶̳͋̓͊ë̷̫̟́͜͝͝n̵̨̳̬̒?̴̩̈́̄ ☕

Ich bin sehr spät dran, aber ich wollte noch eine Kleinigkeit im Blogpost ausprobieren. Nun denn, hier ist mein erster Beitrag zu den #blogwochen2025 https://maurice-renck.de/de/blog/2025/warum-bloggen-wir-eigentlich-immer-noch

So viele Fehler in einem Text … Guckt da denn niemand mal drüber? https://harburg-aktuell.de/news/polizei-feuerwehr/elfj%C3%A4hriger-verungl%C3%BCckt-neim-klettern-in-ruine-im-binnenhafen.html

In dieser Woche ist ein kleiner Home-Server bei uns eingezogen.
Meinen fakeTuner für das Sagem Küchenradio habe ich schon dorthin portiert. Gerade spiele ich mit icecast2 und ezstream herum. Die MP3-Sammlung ist bereits im Küchenradio angekommen. Jetzt fehlt nur noch ein kleines Webinterface für die einfache Steuerung.

@doesnm.p.psf.lt@doesnm.p.psf.lt It was always intended to have both Yarn.social and Salty.im integrate together. Yes. This includes having a set of specifications that anyone can write clients to.

@eapl.me@eapl.me This is one of my concerns too. The moment you post publicly ciphertext, you open yourself up for future attacks on the ciphertext, which you really want to avoid if you can. If you have a read of the Salty.im Spec you’ll note we went to great lengths to protect the user’s privacy as well as their identity and make it incredibly hard to guess at inboxes. It’s still a WIP, but I’d love to see it progressed even further – I truly feel strongly about a purely decentralised messaging ecosystem 👌

I do think integrating things like Salty.im might actually be a good idea. I can also see a future where we integrate other things like todo.txt and calendar.txt. I’d even love to see decentralised forms of “plain text” voting too.

@andros@twtxt.andros.dev i think salty.im integration would be great but i still don’t know how it possible

https://salty.im/

Puh, eine Woche Städteurlaub in Dublin. Das schafft - vor allem die Leber! 🍻🥃
Viele Eindrücke, Gegensätze und wunderbare Menschen.
Jetzt heißt es wieder: Im Alltag ankommen.

Why I’m No Longer Talking to Architects About Microservices
Comments ⌘ Read more

Why I’m Boycotting AI
Comments ⌘ Read more