Ikea’s Big Smart Home Push Arrives With 21 New Matter Devices
The Scandinavian furniture giant has unveiled 21 new ultra-affordable Matter-over-Thread smart home devices across three launch segments: lighting, sensors, and control. With prices starting at just a few dollars, Ikea is pushing hard to replace its old Zigbee lineup and become a serious player in the Matter ecosystem. Forbes reports: Back to the 21 n … ⌘ Read more
Using AI to negotiate a $195k hospital bill down to $33k
Article URL: https://www.threads.com/@nthmonkey/post/DQVdAD1gHhw
Comments URL: https://news.ycombinator.com/item?id=45734582
Points: 517
# Comments: 391 ⌘ Read more
GTK2 about to be removed from the official Arch repos: https://lists.archlinux.org/archives/list/arch-dev-public@lists.archlinux.org/thread/2BDHYLEFSYQBDTMUOZT5J6AFTA5M3FO6/
It’ll probably all be dropped to the AUR, so I can build this myself, because I still have some stuff that depends on it (and will never receive further updates).
Silicon Labs SixG301 Series 3 SoCs Target Zigbee, Matter, and Thread Development
Silicon Labs has announced general availability of its new Series 3 platform, debuting with the SiMG301 and SiBG301 wireless SoCs. Built on a 22 nm process, the Series 3 family targets compute-intensive IoT applications that require higher security, integrated connectivity, and support for modern 2.4 GHz wireless protocols. Series 3 introduces a multi-core architecture that […] ⌘ Read more
Discussion Thread - Ask, Share, and Discuss Anything About Cats. ⌘ Read more
↳
In-reply-to
»
The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.
⤋ Read More
@zvava@twtxt.net My clients trusts the first url field it finds. If there is none, it uses the URL that I’m using for fetching the feed.
No validation, no logging.
In practice, I’ve not seen issues with people messing with this field. (What I do see, of course, is broken threads when people do legitimate edits that change the hash.)
I don’t see a way how anyone can impersonate anybody else this way. 🤔 Sure, you could use my URL in your url field, but then what? You will still show up as zvava in my client or, if you also change your nick field, as movq (zvava).
↳
In-reply-to
»
The original twt is unavailable. It may have been edited or deleted, or is from an unknown or muted feed.
⤋ Read More
@zvava@twtxt.net Yes, the specification defines the first url to be used for hashing. No matter if it points to a different feed or whatever. Just unsubscribe from malicious feeds and you’re done.
Since the first url is used for hashing, it must never change. Otherwise, it will break threading, as you already noticed. If your feed moves and you wanna keep the old messages in the same new feed, you still have to point to the old url location and keep that forever. But you can add more urls. As I said several times in the past, in hindsight, using the first url was a big mistake. It would have been much better, if the last encountered url were used for hashing onwards. This way, feed moves would be relatively straightforward. However, that ship has sailed. Luckily, feeds typically don’t relocate.
↳
In-reply-to
»
I would personally rather see something like this:
⤋ Read More
@alexonit@twtxt.alessandrocutolo.it Well we have to really use the same spec or threading doesn’t really work in a truly decentralized manner 😉
↳
In-reply-to
»
@bender Really? 🤔
⤋ Read More
@zvava@twtxt.net Going to have to hard disagree here I’m sorry. a) no-one reads the raw/plain twtxt.txt files, the only time you do is to debug something, or have a stick beak at the comments which most clients will strip out and ignore and b) I’m sorry you’ve completely lost me! I’m old enough to pre-date before Linux became popular, so I’m not sure what UNIX principles you think are being broken or violated by having a Twt Subject (Subject) whose contents is a cryptographic content-addressable hash of the “thing”™ you’re replying to and forming a chain of other replies (a thread).
I’m sorry, but the simplest thing to do is to make the smallest number of changes to the Spec as possible and all agree on a “Magic Date” for which our clients use the modified function(s).
↳
In-reply-to
»
I would personally rather see something like this:
⤋ Read More
@alexonit@twtxt.alessandrocutolo.it My problem is I don’t see a world where we don’t employ some form of cryptography to use as keys for threads in databases and other such things honestly. I’m not going to use url#timestamp as keys.
↳
In-reply-to
»
TNO Threading (draft):
Each origin feed numbers new threads
⤋ Read More
Each origin feed numbers new threads
(tno:N). Replies carry both (tno:N) and (ofeed:<origin-url>). Thread identity = (ofeed, tno).
@prologic@twtxt.net That’s a completely flat threading model (you can’t reply to replies). Is that intentional?
↳
In-reply-to
»
TNO Threading (draft):
Each origin feed numbers new threads
⤋ Read More
Each origin feed numbers new threads
(tno:N). Replies carry both (tno:N) and (ofeed:<origin-url>). Thread identity = (ofeed, tno).
This is possibly the only other threading model I can come up with for Twtxt that I think I can get behind.