Hacker Newsnew | past | comments | ask | show | jobs | submit | alpn's commentslogin


Thanks! Macroexpanded:

I should have loved biology (2020) - https://news.ycombinator.com/item?id=40103590 - April 2024 (253 comments)

I should have loved biology - https://news.ycombinator.com/item?id=32035054 - July 2022 (271 comments)

I should have loved biology - https://news.ycombinator.com/item?id=25136422 - Nov 2020 (298 comments)


is there a way to pin comments like this up top? I've just spent 5min doing the same by hand, before scrolling all the way down to see this one


I'm sorry for the duplicated effort!

We don't pin those comments to the top because it would nudge the conversation in too meta a direction. It's better that they hover partway down the page.

What I do is ctrl+F 'ycombinator' on the thread before posting one, though of course that doesn't avoid race conditions.


"[..] a security bug identified by AI tools is subsequently independently discovered by a different researcher. This suggests that adversaries who do not report bugs to OSS projects are likely to be able to discover these bugs too. Given this, the OpenSSH team will, for now, be making more frequent releases to get bugfixes into users' hands more quickly rather than batching them until the next planned release."


Meanwhile Zig developers: not even a spell check fix using AI will get accepted


I'm working on https://wireplug.org:

wireplug lets you create mesh VPNs using standard WireGuard. Your wg config files stay almost the same, except you no longer have to specify an `Endpoint` for your peers. Instead, wireplug detects all your possible endpoints (including LAN) and coordinates them with your peers for you. It handles NAT traversal and works with the in-kernel WireGuard driver on Linux and OpenBSD. This lets you keep managing your own keys and network topology, while also maintaining connectivity when moving between networks.

Currently working on improving NAT traversal by adding support for PCP and NAT-PMP.


Is this similar to Netmaker's offering? Platform wrapper around wireguard protocol?


Sounds interesting. Tailscale without handing off key management?


Sounds very useful, will give it a try for sure!



I continue working on https://wireplug.org: A simple, free, and open source connectivity coordinator for WireGuard. Basically a way to keep WireGuard tunnels connected while moving between different access points. It handles (basic) NAT traversal and works with the in-kernel WireGuard driver on Linux and OpenBSD. You can find the technical details at https://wireplug.org


> 95% of the time the stuff with your sushi isn't wasabi

so unexpected that i had to look it up; turns out you're right: https://chefcoca.com/blogs/food-service-equipment-resources/...


For anyone wondering: AF_ALG is a Linux socket interface that exposes the kernel’s crypto API via file descriptors, using normal read(2)/write(2) calls for hashing and encryption.


I wonder can the kernel just remove it and distros put on a compatiability layer.


It's already a configurable option in the kernel which can be fully disabled by distros if they wanted to provide their own compatibility layer, or just not ship any software that has a hard dependency on it.


I always use only custom compiled kernels on my computers, where I enable only the configuration options that I really need.

So the options related to AF_ALG have always been disabled, because I have not encountered an application that needs them, among those that I use.

Unfortunately the Linux distributions must enable in their default configuration most options, because they cannot predict what their users will need.


here's the mailing list thread in case anyone is interested:

https://marc.info/?t=177377722400001&r=1&w=2


In case anyone else is wondering -

Neo:

  Height: 0.50 inch (1.27 cm)
  Width: 11.71 inches (29.75 cm)
  Depth: 8.12 inches (20.64 cm)
  Weight: 2.7 pounds (1.23 kg)
Air:

  Height: 0.44 inch (1.13 cm)
  Width: 11.97 inches (30.41 cm)
  Depth: 8.46 inches (21.5 cm)
  Weight: 2.7 pounds (1.23 kg)


It feels like they did everything they could so that the cheap MacBook with an iPhone CPU would not be lighter than the 1.5x more expensive MacBook with Apple Silicon


Thank you, from my cursory look of their comparison page, this is the information that was missing. But maybe that was a deliberate choice on Apple's part.


Nah it's on there.


Not OP, but I believe they are paraphrasing "First They Came…". https://en.wikipedia.org/wiki/First_They_Came


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

Search: