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

There were 317 successful orbital launches in 2025 [0] and 229 so far this year [1]...

[0]: https://en.wikipedia.org/wiki/2025_in_spaceflight#Orbital_la...

[1]: https://en.wikipedia.org/wiki/2026_in_spaceflight#Orbital_la...

Edit: mistyped 317 as 313


> Campaigns already have strong limits.

The SC decided today that political parties can spend as much money as they want in coordination with candidates.


Do you expect this to result in much substantive change relative to before the ruling was made?


It really isn't. I mean, at a very basic addressing level, sure, IPv4 addresses and IPv6 addresses are just a sequence of octets. But at a network infrastructure level they are quite different, and IPv6 is (conceptually) designed for large-scale, hands-off deployments. See: SLAAC, NDP, DAD, GUA/ULA/link-local address scopes, unicast vs. multicast vs. anycast, etc.


> the term 'query' is already used to refer to http requests in general

In what circles is this the case? I sometimes colloquially refer to a GET request as a query, but definitely not so on a POST, PUT or DELETE.


I'm guessing the op is referring to https://en.wikipedia.org/wiki/Query_string


Thread is also IP(v6)-based. But in this context, Thread would go a fair ways toward solving stavros's concern, as it means security could be enforced on the Border Router(s), rather than each individual device.


Weirdly, the mitigation does not seem to work under WSL2 (at least in Ubuntu 24.04).

    Linux wsl2 6.6.87.2-microsoft-standard-WSL2 ...
`modprobe algif_aead` errors out, but if I run the POC, it succeeds.

Outside of WSL2, the mitigation does appear to work though.


It's possible that the WSL kernel has that code compiled-in rather than as a loadable module. If they ship the kernel config somewhere, you could verify with

  zgrep CRYPTO_USER_API_AEAD /proc/config.gz /boot/config-*
It should show =m if it's a loadable module, and =y if it's compiled in.


It's a loadable module:

    CONFIG_CRYPTO_USER_API_AEAD=m
Using bpftrace to watch calls to module_request, openat, etc., it looks like when the kernel calls modprobe, it doesn't even look at the disable-algif.conf file:

    [module_request] pid=3648 comm=python name=algif-aead
    [umh_setup] pid=3648 comm=python path=/sbin/modprobe argv0=/sbin/modprobe argv1=-q argv2=-- argv3=algif-aead argv4=
    [openat] pid=3688 file=/etc/ld.so.cache
    [openat] pid=3688 file=/lib/liblzma.so.5
    [openat] pid=3688 file=/lib/libz.so.1
    [openat] pid=3688 file=/lib/libgcc_s.so.1
    [openat] pid=3688 file=/lib/libc.so.6
    [openat] pid=3688 file=/etc/modprobe.d
    [openat] pid=3688 file=/lib/modprobe.d
    [openat] pid=3688 file=/lib/modprobe.d/dist-blacklist.conf
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.softdep
    [openat] pid=3688 file=/lib/modprobe.d/systemd.conf
    [openat] pid=3688 file=/etc/modprobe.d/usb.conf
    [openat] pid=3688 file=/proc/cmdline
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.dep.bin
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.alias.bin..
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.symbols.b..
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.builtin.a..
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/modules.builtin.b..
    [openat] pid=3688 file=/sys/module/algif_aead/initstate
    [openat] pid=3688 file=/sys/module/af_alg/initstate
    [openat] pid=3688 file=/sys/module/algif_aead/initstate
    [openat] pid=3688 file=/lib/modules/6.6.87.2-microsoft-standard-WSL2/kernel/crypto/alg..
    [finit_module] pid=3688 comm=modprobe fd=0 flags=0
    [module_load] pid=3688 comm=modprobe name=algif_aead
Restart WSL2, run the bpftrace, and try `sudo modprobe algif-aead`, and that shows it looking at (or I guess opening) other files in /etc/modprobe.d, including the new one.

The mystery is why.


In wsl, each distro you have runs in a container (with lot of permissions), you'd need to apply the modprobe change inside wsl "hypervisor" rootfs


The only way to solve this issue in WSL is to rebuild your kernel:

~ uname -r

6.18.20.3-microsoft-standard-WSL2+


> The branch itself gets created with the ticket number and everything follows from that, there's no extra effort.

Only problem there is the potential for a deeply-ingrained assumption that the Jira key being in the branch name is sufficient for the traceability between the Jira issue and commits to always exist. I've had to remind many people I work with that branch names are not forever, but commit messages are.

Hasn't quite succeeded in getting everyone to throw a Jira ID in somewhere in the changeset, but I try...


It sounds pretty simple to automate that away too: make it part of the merge hook to include the source branch name into the message.

We are engineers, everything is a problem waiting to be automated :)


Pebble Time 2 has a compass sensor and HRM. https://ericmigi.com/blog/pebble-time-2-design-reveal#final-...

Unless you specifically are after a barometer, in which case I don't think the PT2 has that.


I think most of the battery life improvement is the much more power-efficient SOCs available. The original Pebble used an STM32 processor and a TI Bluetooth chip, where nowadays having BLE integrated into the SOC is table stakes.


Did you get it in black like I did? My buttons also cracked practically right away (within a day), I suspect because the reinforcements were installed poorly (the buttons are VERY hard to press). It made the down button unusable.

But kudos to Eric and Claudio, they're shipping me a replacement (in white, which, as I understand it and as they said in their email, should be less susceptible to the issue, something about the white rubber versus black makes it less problematic). My only frustration was how quickly it failed, since I know it's a new-old-stock case.

Highly looking forward to the Time 2. I only stopped using my Pebble Time Steel when the battery life degraded to ~3 days (after about 6 years), used a Fossil Hybrid for a few years, now a Pixel watch. Measuring battery life in weeks will be a breath of fresh air :)


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

Search: