zekica
zekica on Hacker News
What do you mean globally accessible? All the devices on my network have global IPv6 addresses for the last 5 years - since my ISP enabled IPv6 but none of them are accessible unless I configure it.
It's not just that the ISP will lower their costs for CGNAT, the users will also get a much better experience.
Trusted computing is fine and even good only if the owner (the person/company that bought the device) is in control, but it's not the world we live in.
xdg already provides "portals" and "XDG Intents" that implement most of what android does. Flatpak implements most of the sandboxing you have on android. It doesn't have feature parity but IMO it doesn't need to. CGroups and systemd-user can prevent apps from running in the background.
It's not Broadcom so it is supportable by OpenWrt. It runs Qualcomm IPQ5332 SoC which recently got supported in upstream linux ath12k drivers... There are a few patches to make it work and the only blocking issue is with the Realtek switch connected to the LAN ports.
N95 was not "meager" for it's time - it was faster than the first iPhone.
Mainly because Microsoft wants to have "connected standby": the CPU is running in a low power mode (not powered off like "old" S3 sleep), can be turned on periodically and can turn on other devices even when the computer is "sleeping".
My Zen2 based Lenovo laptop has 6-7 hours of battery when doing basic tasks in both Windows and Linux, but sleep on Linux lasts a week while on Windows it's empty in 24 hours.
This post is everything wrong with the world today. Installing software should not be gate-kept.
Who's to say that some current or future government in the US wouldn't use the data to prosecute dissent guaranteed by the constitution?
And it can fail in great ways. Last example: I asked claude for a non-trivial backup and recovery script using restic. I gave it the whole restic repo and it still made up parameters that don't exist in the code (but exist in a pull request that's been sitting not merged for 10+ months).
I think this is a snap issue.
And they are the only real solution. Demand fitting production is never going to work unless we give up all the autonomy.
SNI routing is such a bad way to do what should be L3 problem that people implemented PROXY protocol to send information about user's endpoint address without doing MITM.
All desktop/mobile OSes today use "Stable privacy addresses" for inbound traffic (only if you are hosting something long-term) and "Temporary addresses" for outbound traffic and P2P (video/voice calls, muliplayer games...) that change quickly (old ones are still assigned to not break long-lived connections but are not used for new ones).
You can do fc00::/7 in addition to public addresses so your lights don't have public address while your phone does.
And the worst part about CGNAT is that you have two bad solutions:
Either EIM/EIF (preferably with hairpinning) where you can practically do direct connections but you have to limit users to a really low number of "connections" breaking power users.
Or EDM/EDF where users have a higher number of "connections" but it's completely impossible to do direct connections (at least not in any video/voice calling system).
Trivially easy do direct connections between devices (if desired), no issues when creating VPNs between networks using private ranges.
What would be the disadvantage?
Temporary addresses are used by any Linux distro using NetworkManager (all desktop ones). For server distros, it can differ.
.docx and .xlsx are also just zip files with XML and attachments. The bad thing is that the XML is Word's internal document structure serialized and behavior for some values is only defined in Microsoft's code.
Even gcc's -O0 will do the bitshift, but even dividing with 5 on x86_64 will not do idiv:
imul rdx, rdx, 1717986919
shr rdx, 32
sar edx
sar eax, 31
sub edx, eax
mov eax, edx
Minor nitpick: dynamic memory allocation is not used when processing packets, but is when adding/removing clients via netlink.
Yes, VLAN isolation prevents this - devices in different VLANs use different GMK keys even when connected to the same network.
This only works for one SSID. Even then, one thing that can mitigate this is using Private-PSK/Dynamic-PSK on WPA2, or using EAP/Radius VLAN property.
On WPA3/SAE this is more complicated: the standard supports password identifiers but no device I know of supports selecting an alternate password aside from wpa_supplicant on linux.
You can't think all the way about refining your prompt for LLMs as they are probabilistic. Your re-prompts are just retrying until you hit a jackpot - refining only works to increase the chance to get what you want.
When making them deterministic (setting the temperature to 0), LLMs (even new ones) get stuck in loops for longer streams of output tokens. The only way to make sure you get the same output twice is to use the same temperature and the same seed for the RNG used, and most frontier models don't have a way for you to set the RNG seed.
Only if that authenticator/password manager app is not end-to-end encrypted.
Both. LGPL doesn't distinguish between commercial and non-commercial use.
They have different goals:
GrapheneOS wants to make a FOSS Android with the security model that makes it hard for any bad party to break into the phone.
LineageOS wants to make a FOSS Android that respects user's privacy first and foremost - it implements security as best as it can but the level of security protections differs on different supported devices.
Good news is that if you have a boot passphrase, it's security is somewhat close to GrapheneOS - differing in that third parties with local access to the device can still brute-force their access whereas with GrapheneOS they can't - unless they have access to hardware level attacks.
Interesting... I rarely form words in my inner thinking, instead I make a plan with abstract concepts (some of them have words associated, some don't). Maybe because I am multilingual?
Multiple local networks while still using SLAAC.
Yeah, Kate is great. New versions integrate nicely with LSPs and while not as fast as Vim it's faster than VSCode and most gnome based code editors.