@lyse@lyse.isobeef.org Danke! Ja, es gibt noch unzählige Stellschrauben an dem Ding. Deine Anmerkungen werde ich einarbeiten. Eine mobile Ansicht wär auch noch schön. Derzeit sitzt es auf dem Smartphone doch noch recht stramm.

@Unterhaltungen: Die von gestern zu verschlüsselten Nachrichten war ausschlaggebend für die Umsetzung. In “Timeline” und “Yarn” haben mich die Lösungsansätze bisher nicht überzeugt. Aber wir können ja alle etwas von einander lernen.

@arne@uplegger.eu Uuuuhhh, das fühlt sich klasse an, gute Arbeit mein Lieber! :-)

Besonders positiv hervorheben muss ich die Rohdatenansicht. Sowas hab ich mir auch schon in der Vergangenheit hin und wieder gewünscht. Wie toll es doch wär, direkt den Eintrag im Original zu sehen, ohne erst im Feed mühsam auf die Suche gehen zu müssen, was auch noch einen Wechsel auf den Browser oder den Editor erzwingt. Das werd ich mir definitiv auch einbauen. Insbesondere für die Entwicklung absolut hilfreich. Die Textarea könntest Du noch mit einem readonly-Attribut ausstatten.

Die Gesamtbaumansicht einer Unterhaltung gefällt mir ebenfalls. Davon bin ich ja ein großer Verfechter. Nicht nur die direkten Antworten zu sehen, sondern alle. Klar, bei tief verschachtelten Unterhaltungen und sehr langen Beiträgen verliert man da doch mal den Überblick, aber die kommen in der Praxis meiner Erfahrung nur selten vor.

Die zwei Elemente in der Fußzeile eines Beitrags würde ich auch noch versuchen in die Kopfzeile zu verschieben, dann wird die Darstellung insgesamt kompakter, gerade bei Unterhaltungen könnte das von Vorteil sein.

Weiter so!

@lyse@lyse.isobeef.org Du kannst selbst gern mal im TwtxtReader-Dummy herumklicken. Da ist natürlich alles auf meinen Feed eingestellt.
Bildschirmfotos wirken irgendwie nicht.

@arne@uplegger.eu Klingt gut, Du darfst uns gern mal ein paar Bildschirmfotos vom aktuellen Stand zeigen. :-) Die erste Aufnahme sah bereits recht aufgeräumt aus.

Ich müsste auch endlich mal an meinem Client weitermachen. Aber heut nimmer.

@arne@uplegger.eu Ahja, danke für die Erläuterung! Einrückungen waren meinem Parser tatsächlich egal, der dürfte einfach ein trim() angewendet haben, bevor sich die Zeile zur näheren Verarbeitung angesehen hat. :-D

@movq@www.uninformativ.de It says F=700, D=70 and RK=20. I have to research what magnification that translates to, a few days have passed since physics class. Your Celestron Ultima 100 looks much more high quality than this thing.

@movq@www.uninformativ.de Großartig! :-D

What about this nice new neofo - here’s some info about how to keep your hair scurf-free! - lk record?

#Videoclips used to be promotional tools, a way for an artist or band to promote their music. Now you cannot see one without being interrupted in the middle so the platform it was published on can serve you an ad promoting something else…

With politicians now finally realizing the perils of having main social media controlled by millionaires, perhaps now it is a good time to promote #fedigov again:

https://fedigov.eu/

Are you in touch with politicians? If so, you might want to send them this link!

Mastercard DNS error went unnoticed for years
Article URL: https://krebsonsecurity.com/2025/01/mastercard-dns-error-went-unnoticed-for-years/

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

Points: 500

# Comments: 151 ⌘ Read more

squirrel report: my tan-ear-tuffed friend has survived the -25 degree cold days, to my relief

Die Bastelei am TxtwtReader geht gut voran. Neben diversen Filtern und Ansichten werden Unterhaltungen nun schön strukturiert angezeigt. Jetzt müsste ich mich auch mal um das Verfassen von Einträgen kümmern. Wenn ich mit dem Projekt zufrieden bin, lasse ich es vielleicht auch auf die Welt los. #OpenSource

👋 Hello @empockelimi@txt.sour.is, welcome to txt.sour.is, a Yarn.social Pod! To get started you may want to check out the pod’s Discover feed to find users to follow and interact with. To follow new users, use the ⨁ Follow button on their profile page or use the Follow form and enter a Twtxt URL. You may also find other feeds of interest via Feeds. Welcome! 🤗

@aelaraji@aelaraji.com I’ve been noticing the same, so I opened an issue now (https://github.com/sorenpeter/timeline/issues/55) and then we will have to look into it.

Tang Console: Compact FPGA Platform for Development and Retro Gaming
Sipeed has recently launched the Tang Console, described as a compact FPGA platform designed for developers and hardware enthusiasts. It offers a flexible and portable solution for applications such as hardware prototyping and retro gaming system emulation. The device is available in two configurations. The 60K variant includes 60K LUTs, 468Kbit SSRAM, and 2Gb DDR3,

Toradex Adds SMARC iMX8M Plus and iMX95 to Its Embedded Portfolio
Toradex has introduced a new System on Module family to support projects requiring the SMARC standard. Featuring connectivity, advanced multimedia, and machine learning capabilities, the modules are compatible with Torizon Embedded Linux, offering long-term support and secure remote management. The SMARC iMX8M Plus incorporates four Arm Cortex-A53 cores at 1.6 GHz for general processing and

A celebração do Dia do #DomínioPúblico em #Portugal é já amanhã!

Na Biblioteca Nacional, com a @wikimediapt@wikimediapt e a @ansol@ansol, há programa para a manhã e a tarde, a participação é gratuita mas sujeita a inscrição que deve ser feita através do formulário!

https://wikimedia.pt/eventos/dia-do-dominio-publico-2025/

@prologic@twtxt.net I know! I know! 🤣 and it feels like I won’t be either, at least for a while … On the bright #Go side, I’m trying to switch everything (static web stuff and reverse-proxy) to #Caddy

@aelaraji@aelaraji.com Haha don’t ask me 🤣 I don’t do PHP 😆

May be no joke chronically ill…fascinating

Ross Ulbricht granted a full pardon
Article URL: https://twitter.com/Free_Ross/status/1881851923005165704

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

Points: 511

# Comments: 598 ⌘ Read more

Image

@lyse@lyse.isobeef.org Die meisten Hersteller von Internetradios (Sony, Denon, Marantz, …) binden einen externen Dienstleister (vTuner) fest(!) in ihre Geräte ein, damit die Nutzer sich durch eine große große Liste von weltweiten Internetradio-Stationen hören können.
Nun hat vTuner seit ca. 2020 sein Geschäftsmodell geändert. Man darf da nun für jedes Gerät (MAC-Adresse) bezahlen. Die Kosten steigen auch von $3 auf $7 pro Jahr. Die Hersteller zucken einfach mit den Schultern. Im schlimmsten Fall schaltet vTuner einfach die Domain ab und dann steht man da - wie bei mir: http://sagem.vtuner.com
Der XML-Parser von der alten Sagem-Huddel verlangt zeilenweise Einträge ohne Einzüge. Vielleicht standest Du mit Deinem Parser ja Pate!? 😉

@arne@uplegger.eu Hahaha, vor Dekaden hab ich auch mal einen „XML“-„Parser“ selbst gebaut. Der wollte dann pro Zeile entweder einen öffnenden oder einen schließenden Tag oder aber einen Wert haben. :-O Ganz übel, aber für den damaligen Anwendungsfall hat’s gelangt. War halt bloß kein XML. :-D

Was konkret war dann das Problem von dem zu sauberen XML in Deinem Fall? Und schön zu hören, dass Du das Gerät vor dem vorzeitigen Elektroschrotttod bewahrt bekommen hast. :-)

Zum Abschluss noch ne ganz doofe Frage, ganz offensichtlich hab ich von Radios keinen blassen Schimmer. Wieso muss denn das Ding überhaupt mit XML rumfuhrwerken? O_o

LECK MICH FETT!
Das Küchenradio (Sagem - My Dual Radio 700) gibt wieder Töne von sich! Der XML-Parser von dem Ding ist sowas von hinüber. Die “Fertiglösungen” YCast und YTuner haben ein zu ordentliches XML erstellt. Per Trial and Error habe ich dann die Formatierung gefunden, die die olle Kiste braucht. 🥳

@lyse@lyse.isobeef.org i trusted all pods yesterday and now when i pull it up they are all untrusted.

@xuu@txt.sour.is The Pod.LastSeen and Pod.LastUpdated fields are only ever updated in the Cache.DetectPodFromUserAgent(…) function as far as I can tell. This function is called in Cache.DetectClientFromRequest(…) and Cache.DetectClientFromResponse(…).

Cache.DetectClientFromRequest(…) is only invoked when the twtxt.txt is requested and looks at the User-Agent HTTP request header.

Cache.DetectClientFromResponse(…) is only called in Cache.FetchFeeds(…) and looks at the Powered-By HTTP response header. This header would be set in twtxt.txt HTTP responses from yarnd. A bunch of places invoke Cache.FetchFeeds(…), including a periodic job (UpdateFeedsJob.Run()). Maybe something is iffy around these locations.

@movq@www.uninformativ.de It’s an old, cheap Optus without any model information on it. It was maybe 180DM or so in a discounter 25, 30 years ago. Its main job is to collect dust, can’t even remember its last use. That must have been easily 15 years ago I reckon. Thus, absolutely no surprise. Maybe I’ll just take it apart and see what I can see as the week progresses.

did I just break something else? 😅🤣

@lyse@lyse.isobeef.org @prologic@twtxt.net 😆 There was something weird going on with my #Timeline instance, the text input box was visible even though I was logged out and I was able to twt from it … It has to do with cache because it wouldn’t disappear unless I whip my website’s cache from the browser.

Poke @sorenpeter@darch.dk and @eapl.me@eapl.me I have no Idea how to reproduce this.

I’m rather frozen after half an hour looking at Venus and Saturn through the telescope outside. I couldn’t see any rings around Saturn. Disappointing. It also appeared rather dark. The very bright Venus on the other hand told me that there is something growing inside the scope. :-( Or maybe there is dust.

@xuu@txt.sour.is I added some logging when a “dead” peer is removed as I suspect this to be a hot candidate for all the trouble. https://git.mills.io/yarnsocial/yarn/commit/21538951f9dc71b9366db6dbb784a8078096a4c8 Does this yield anything?

@aelaraji@aelaraji.com @prologic@twtxt.net Hmmm!

0-click deanonymization attack targeting Signal, Discord, other platforms
Article URL: https://gist.github.com/hackermondev/45a3cdfa52246f1d1201c1e8cdef6117

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

Points: 503

# Comments: 179 ⌘ Read more

It’s nice to see we’re all largely thinking along the same lines. e.g: Salty.im 😅

@eapl.me@eapl.me Yeah this is true. Previously RSA and AES were more common. These days Salsa and Chacha and Curve are fairly prevalent. For example all the Wireguard stuff uses Curve25519 / Ed25519 crypto. Signal uses very similar crypto too, but with some very nice double ratcheting 3DH.

@eapl.me@eapl.me I -think we’ve gotten use to it somewhat 🤣

a year ago I had a struggle to find documentation about it and now it seems there are more examples, cool!

I agree 🙂, although it’s easy to lose comments over time and are not so grouped by topic, it’s not so easy to vote or make a survey about it…

I prefer a forum for that 😊

here are a few ideas you might take into consideration when designing a secure IM https://developer.virgilsecurity.com/docs/e3kit/fundamentals/secure-instant-messaging/

Obviously if you’ve worked on something similar, you already know it, he

I made a draft of an “encrypted public messenger”, which was basically a Feed for an address derivate from the public ket, let’s say ‘abcd..eaea’

Anyone could check, “are there any messages for my address?” and you get a whole list of timestamps and encrypted stuff.

Inside the encrypted message is a signature from the sender. That way you ‘could’ block spam.

Only the owner of the private key could see who sent what, and so…

And even with that my concussion was that users expectations for a private IM might be far away from my experiment.

@doesnm@doesnm.p.psf.lt whilst technically true, expensive and unnecessary.

Again: if you can decrypt - it’s for you

It is not possible to remove it, otherwise you do not know that the message is for you. With that information you can’t decrypt.

@doesnm@doesnm.p.psf.lt I always do 👌

I updated the specification with base64, Curve25519 and more examples: https://github.com/tanrax/twtxt-direct-message-extension

Can you share summary after meeting?

@prologic@twtxt.net @lyse@lyse.isobeef.org First, please leave me your comments on the repository! Even if it’s just to give your opinion on what shouldn’t be included. The more variety, the better.

Second, I’m going to try to do tests with Elliptic keys and base64. Thanks for the advice @eapl@eapl.me

Finally, I’d like to give my opinion. Secure direct messages are a feature that ActivityPub and Mastodon don’t have, to give an example. By including it as an extension, we’re already taking a significant leap forward from the competition. Does it make sense to include it in a public feed? In fact, we’re already doing that. When we reply to a user, mentioning them at the beginning of the message, it’s already a direct message. The message is within a thread, perhaps breaking the conversation. Direct messages would help isolate conversations between 2 users, as well as keeping a thread cleaner and maintaining privacy. I insist, it’s optional, it doesn’t break compatibility with any client and implementing it isn’t complex. If you don’t like it, you’re free to not use it. If you don’t have a public key, no one can send you direct messages.

Keep breathing and stay cool.

👋👋 Reminders that this weekend our monthly Yarn.social online meetup. Who’s coming? 🤔 Some possible topics:

• Direct Messaging for Twtxt
  
• @prologic@twtxt.net ’s new EdgeGuard services 🤣
  
• What’s the weather like? 👍
  

Details:

• When: 25th Jan 2025 at 12:00PM UTC (midday)
  
• Where: https://meet.mills.io/call/Yarn.social

@eapl.me@eapl.me@eapl.me@eapl.me But we’re actively discussing on Twtxt 🤣

@eapl.me@eapl.me@eapl.me@eapl.me Agree with the base64 encoding 👌

While the US politicians and tech billionaires are going full-on fascist mode, here is a reminder that there are European alternatives for many well known digital and online services: https://european-alternatives.eu

@eapl.me@eapl.me@eapl.me@eapl.me actually it is easy 🤣 It’s now the standard for SSH keys 😆

Simplifying my online presence further by removing my Known site. Goodbye social.johanbove.info - it was sometimes a little fun.

@aelaraji@aelaraji.com Hmmm? 🤔

@xuu@txt.sour.is Is this because there’s a bug in persisting trusted peers? 🤔

@lyse@lyse.isobeef.org This is a good point.

@doesnm@doesnm.p.psf.lt That’s actually not true, because you’d have to know the target you’re interested in, in the first place. Inboxes in Salty.IM are deliberately shahed for this reason. So whilst you may know your own inbox address, etc, I (as an arbitrary bad actor) wouldn’t easily be able to guess (let alone brute force) my way to another inbox address of an interested party.

It’s ok for most encrypted protocols (In salty you can fetch other messages but can’t decrypt). Btw i think recipient can be removed so if someone seen message they tried to decypt, if can’t - its not message to you

hmmm? 🤔

I remember starting that one.. it was a bit gratuitous for me to get past the first few episodes.

and yes.. these all come with satisfying endings across multiple seasons.

my goto’s are the Expanse, the Magicians, XFiles, House, Umbrella Academy, Orphan Black, 12 Monkeys, the star treks (DS9 especially)

i have probably watched through them a half dozen times each. some more :D

It seems related to us poor single user pods not getting the trust to share twts.. which it seems to still untrust on restart for me.

@movq@www.uninformativ.de ^^

@movq, @prologic@twtxt.net when navigating to a Yarn. If the head twt is missing then the whole thread is not accessible. It only returns an error. so i have no way to view any of the replies within the thread other than the end twt.

UNIT DualMCU One with RP2040 for Real-Time and ESP32 for Wireless Connectivity.
The UNIT DualMCU One is a development board that combines the ESP32 and RP2040 microcontrollers. The ESP32 provides Wi-Fi and Bluetooth connectivity, while the RP2040 offers hardware control with flexible GPIO, supporting applications in IoT, robotics, and automation. The RP2040 features a dual-core ARM Cortex-M0+ processor running at 133 MHz, offering compatibility with Arduino UNO [… … ⌘ Read more

@xuu@txt.sour.is Can you elaborate in textual form for the poor vision impaired developer 🤣 🙏

Also guys if u ever need a new life philosophy. Connor Hawke from green arrow comics is your guy

Lowkey planning out a book (anthology. Maybe) of just playscripts in my Greek myth yuriverse. Thank u lord

Just threw this RSS feed into Newsboat. The titles suck, but I hope the content makes up for it. :-)

@movq@www.uninformativ.de Speaking of fog, a workmate showed me his view out of the window today and you couldn’t even see a hundred meters. Looked really nice! :-) We actually had a little bit of sun over here.

@movq@www.uninformativ.de Woah, that sun from satellite SDO is fucking sick! https://social.bund.de/system/media_attachments/files/113/859/065/836/106/300/original/95b43f7a0086476d.jpeg

I haven’t read the entire specification, but I think there is a fundamental design problem. Why would someone put an encrypted message on a public feed that is completely useless to everybody other than the one recipient? This doesn’t make sense to me. It of course depends on the threat model, but wouldn’t one also want to minimize the publicly visible metadata (who is communicating with whom and when) when privately messaging? I feel there are better ways to accomplish this. Sorry, if I miss the obvious use case, please let me know. :-)

Clouds are hiding the planets right now, but the sky was slightly on fire before: https://lyse.isobeef.org/abendhimmel-2025-01-20/

Image

This UX can be very frustrating.

another one would be to allow changing public keys over time (as it may be a good practice [0]). A syntax like the following could help to know what public key you used to encrypt the message, and which private key the client should use to decrypt it:

!<nick url> <encrypted_message> <public_key_hash_7_chars>

Also I’d remove support for storing the message as hex, only allowing base64 (more compact, aiming for a minimalistic spec, etc.)

[0] https://www.brandonchecketts.com/archives/its-2023-you-should-be-using-an-ed25519-ssh-key-and-other-current-best-practices

my first thought is that encrypting messages with Elliptic keys is not as easy as with RSA, although I tried doing something similar a few months ago with ECIES
https://github.com/eapl-gemugami/owl/blob/main/src/app/controller/ecies_demo.php

interesting idea. I’m not personally interested on having DM conversations on twtxt (for now), although I see the community could be interested in.

I’d suggest to enable the Discussion section in your Github repo to receive comments, as we did for timeline https://github.com/sorenpeter/timeline/discussions

#MaradoWeekly #WeeklyPlant Week 03

Image

DeepSeek-R1
Article URL: https://github.com/deepseek-ai/DeepSeek-R1

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

Points: 517

# Comments: 180 ⌘ Read more

On my blog: Developer Diary, Turkish Constitution of 1921 https://john.colagioia.net/blog/2025/01/20/turkiye.html #programming #project #devjournal

@andros@twtxt.andros.dev 🤩😍

I promise I will! It’s the next step 😄

It would also be great if you put up a PR against twtxt.dev 🙏