Hacker News new | past | comments | ask | show | jobs | submit | zxcvgm's comments login

Cool, looks like text highlighting is a new addition in 2.10. There aren't any examples in the demo site of this, but can it capture the highlighted text snippets and show them in the link details page? That would help me recall quickly why I saved the link, without opening the original link and re-reading the page. I haven't really seen this in other tools (or maybe I just haven't looked hard enough), except Memex.

> There aren't any examples in the demo site of this

This is because we haven't updated the demo to the latest version.

> but can it capture the highlighted text snippets and show them in the link details page?

That's a good idea that we might implement later, but at the moment you can only highlight the links[1].

[1]: https://blog.linkwarden.app/releases/2.10#%EF%B8%8F-text-hig...


> “…can it capture the highlighted text snippets and show them in the link details page.”

Essentially a quote with attribution.


Well, WhatsApp backups claim they are E2E encrypted, but there’s a flow that uses their HSM for the encryption key, which still feels like some escrow system.

https://engineering.fb.com/2021/09/10/security/whatsapp-e2ee...


True but you can choose to store the key completely yourself. That fixes a big backdoor that's been around for ages.

The biggest problem remaining to me is that you don't chat alone. You're always chatting with one or more people. Right now there's no way of knowing how they handle their backups and thus the complete history of your chats with them.

It's the same thing as trying to avoid big tech reading your emails by setting up your own mailserver. Technically you can do it but in practice it's pointless because 95% of your emails go to users of Microsoft or Google anyway these days.


I have the same thoughts about the approach, and I'm actually working (on the back burner) a similar thing. It's a harman kardon "smart" speaker with a similar design where the brains are on a separate daughterboard and that's now fried.

I've already figured out the control signals and have designed a new daugterboard with an ESP32 to drive the I2S output. I just need to figure out how to downmix the audio to mono and to DSP the L/R channels into tweeter/bass outputs, or to find some code already out there that does this. Any help/pointers here would be appreciated!


One thing you might find helpful is to prototype things with GNU Radio and a GRC flowgraph. I'm not sure that would be useful for running on the ESP32, but you could at least tinker around with signal processing tactics that you could implement on it.


I’m surprised HuJSON wasn’t mentioned in the list. Tailscale uses it for their config files. I did a hacky workaround by preprocessing my JSON config with regex, but found HuJSON later.

https://github.com/tailscale/hujson


Yeah. That's what I came here to say too.

Previously when their Yubikey 4's were found to be suceptible to the ROCA vulnerability [0], they issued replacements [1] for any customers who had affected devices. I had a few of those devices and they were replaced for free.

I guess that's a disadvantage of having a non-upgradable firmware. They can't fix these devices that are already out in the field.

[0] https://en.wikipedia.org/wiki/ROCA_vulnerability

[1] https://support.yubico.com/hc/en-us/articles/360021803580-In...


As I understand it, the ROCA vulnerability is "the secrets generated by a YubiKey may be susceptible to classic cryptographic breaks", something along the level of "the cipher is inherently weak."

This vulnerability, meanwhile, appears to be in the class of "if someone has physical access to your hardware token, and has access to some specialized (expensive) hardware to do side-channel analysis, they might be able to do side-channel on your hardware token." But if someone has physical access to the hardware token... I mean, at that point, most people would consider it compromised anyways and wouldn't expect security guarantees from that point.


Yes: the keys the Y4 tokens generated were susceptible to attacks; here, it's the device itself.


When I initially watched the demo video, I was wondering how the devices might locate each other. I thought it was using ultra wide band (UWB) like iPhones but now I see it’s just GPS. I’m not sure how many of these events are indoors vs outdoors, but it definitely won’t work indoors. Wonder how they might try to make it work indoors if there’s no additional hardware onboard.


A device can't locate other devices via GPS (GNSS apparently, which includes GPS and other systems); it can only locate itself. GNSS is only a receiver; there's no way to transmit unless you have a satellite. [0]

Having located itself, the device has to transmit its ___location to other Totem Compasses via other means. It says it uses 2.4 GHz spectrum and some stripped down, low-latency protocol (why does low-latency matter here?).

[0] I can setup a local cellular transmitter; has anyone tried setting up a GPS transmitter and hack it to send other useful information besides PNT? Yes, I know you can send misleading PNT info; I'm talking about doing something useful.


I think the Luckfox Pico series is the lowest cost ARM-based board you can buy (that runs Linux) at the moment. Even the Pi Zero is $10. Prior to this, it was a board based on the Allwinner F1C100, but I don't think anyone made and sold a dev board except for a DIY business card [0].

[0] https://www.thirtythreeforty.net/posts/2019/12/my-business-c...


Doesn't look like it, but the author uses the Go SSH agent library [1] which _does_ have some example code there and looks pretty straightforward, based on what was described in the post.

[1] https://pkg.go.dev/golang.org/x/crypto/ssh/agent


It is indeed very straightforward. I did a quick check and I use this exact library for my "coarse-grained Debian diff" program, `meikkalainen` [1], and I was able to get it up and working mostly how I wanted within the same morning I started it. Very straightforward, even for a guy who doesn't spend a lot of time in the Goverse.

[1]: https://github.com/hiAndrewQuinn/meikkalainen/tree/main


I remember when Dell was the first to introduce [1] these Compression Attached Memory Modules in their laptops in an attempt to move away from soldered-on RAM. Glad this is now being more widely adopted and standardized.

[1] https://www.pcworld.com/article/693366/dell-defends-its-cont...


> The first iteration, known as CAMM, was an in-house project at Dell, with the first DDR5-equipped CAMM modules installed in Dell Precision 7000 series laptops. And thankfully, after doing the initial R&D to make the tech a reality, Dell didn’t gatekeep. Their engineers believed that the project had such a good chance at becoming the next widespread memory standard that instead of keeping it proprietary, they went the other way and opened it up for standardization.


Trying to make it a standard is one of the least surprising things about it. You want accessories/components in your product to be as commodity as possible to drive costs down.


This sounds like what Roku had patented, except it injects ads when it detects that a HDMI-connected device has paused: https://www.theregister.com/2024/04/17/roku_tv_ad_patent/


Thought HDMI was secure to the screen.


Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: