I read it as they'll invoice me up to $20. Not sure?
HN user
2bluesc
Embedded Linux Systems guy that likes to hack on bikes, drones, security, networking, and more
Did you have extra usage enabled before checking? Mine was disabled and I received the $20 credit.
TBH, it looks to me as a trick to enable extra usage by baiting me with $20 credit by toggling on the feature that lets me burn another $20 without realizing it.
Toggling it again to turn it off immediately after (which I assume most people will miss) seems to guard against this.
I believe Android Work profile[0] would have limited the damage to the work profile rather than also impact the personal profile on a personal device.
Does anyone know if this is correct?
Traditionally, I used Python for personal tools optimizing for quick coding and easy maintenance. These tools commonly feed UI elements like waybar, shell, and tmux, requiring frequent, fast calls.
My approach is evolving due to NixOS and home-manager with vibe coding to do the lifting. I increasing lean on vibe coding to handle simple details to safely write shell scripts (escaping strings, fml) and C/C++ apps. The complexity is minimized, allowing me to almost one-shot small utilities, and Nix handles long-term maintenance.
With NixOS, a simple C/C++ application can often replace a Python one. Nix manages reading the source, pulling dependencies, and effectively eliminating the overhead that used to favor scripting languages while marking marginal power savings during everyday use.
`HOSTALIASES` lets you alias hostnames, but not map hostnames to IPs.
Docs at `man gethostbyname`
You can use the linker to preload `nss_wrapper`[0] and overwrite anything using `nss`.
Here's an example:
> cat hosts
198.51.100.33 test.tld
2001:db8::33 test.tld
198.51.100.12 test4.tld
2001:db8::12 test6.tld
> LD_PRELOAD=/nix/store/sw2r0gpi9c9rsvqgvi4906yxh948ydsv-nss_wrapper-1.1.16/lib/libnss_wrapper.so NSS_WRAPPER_HOSTS=hosts getent ahosts test.tld
198.51.100.33 DGRAM test.tld
198.51.100.33 STREAM test.tld
2001:db8::33 DGRAM
2001:db8::33 STREAM
> LD_PRELOAD=/nix/store/sw2r0gpi9c9rsvqgvi4906yxh948ydsv-nss_wrapper-1.1.16/lib/libnss_wrapper.so NSS_WRAPPER_HOSTS=hosts getent ahosts test4.tld
198.51.100.12 DGRAM test4.tld
198.51.100.12 STREAM test4.tld
> LD_PRELOAD=/nix/store/sw2r0gpi9c9rsvqgvi4906yxh948ydsv-nss_wrapper-1.1.16/lib/libnss_wrapper.so NSS_WRAPPER_HOSTS=hosts getent ahosts test6.tld
2001:db8::12 DGRAM test6.tld
2001:db8::12 STREAM test6.tld
> LD_PRELOAD=/nix/store/sw2r0gpi9c9rsvqgvi4906yxh948ydsv-nss_wrapper-1.1.16/lib/libnss_wrapper.so NSS_WRAPPER_HOSTS=hosts curl -v test.tld
* Host test.tld:80 was resolved.
* IPv6: 2001:db8::33
* IPv4: 198.51.100.33
* Trying [2001:db8::33]:80...
* Trying 198.51.100.33:80...
[0] https://cwrap.org/nss_wrapper.htmlHere's a good YouTube overview from the developer
This looks like a great project!
I think you mean
yourname+servicename@gmail.com
From my experience, many (bad) websites consider "+" an invalid character and prevent you from using the address in this form.
Smart spammers can just strip the service name since it works the same for all Gmail users.
Really need dedicated addresses like Fastmail's Masked Addresses.
Closed User Group (CUG)?
Never heard of aws-lc before this, but now I'm looking for an excuse to use it.
Chipworks offers $50-250k to fully extract the eFUSE of one Intel i5 processor, so the eFUSE content is encrypted by a master key (called “global wrapping logic key” in the patent).
I wonder how readily things like this are known within the HW security community?
Elevated temps significantly impact the retention and are included in some datasheets by memory vendors, but often they are omitted and you need to request them.
Some earlier HN discussion here [0]
Switched to Technitium (from piHole via Docker on amd64 and manual dnsmasq before that) primarily for DNS over HTTPS and never looked back. Used it for DHCP and DNS.
For anyone wondering, this was written in 2019 and is no longer "new". I was confused by the following line since I recall this being available for sometime:
By using the newly introduced dm-writecache device mapper Linux kernel module
Looked for a publication date, but nothing anywhere on the page other then timestamps in the command output mentioning 2019. Wayback machine confirms this as well[0]
[0] https://web.archive.org/web/20191124065801/https://www.admin...
Where do you get that? Sounds like they improved performance over the previous "fixes":
Intel's internal tests show that the 0x12B update does not noticeably affect performance. Benchmarks and gaming tests, including popular titles like Cyberpunk 2077 and Shadow of the Tomb Raider, showed results within normal expected variations when compared to the earlier 0x125 update.
Perhaps "Dolt is Git for data" should really be "Dolt is Git for databases"
I loaded the page expecting to see some arbitrary binary data version control tool and was caught off guard by all the references to SQL.
On Google Pixel 8 (IDK about other Android phones) you can press the power button + volume up button to launch a pop-up menu with the following options: restart, power off, lockdown, emergency.
If you select lockdown you'll be required to use a pin or password to unlock the phone.
You're referring to a cloud-agnostic solution.
I actually mean that the service need not care if it's in the cloud or on-premise as opposed to whose cloud. Many of my services don't need to do anything in the cloud.
If you look at things like awesome-selfhosted[0] you'll see that this is the prevailing expectation of things describing themselves as "self-hosted".
[0] https://github.com/awesome-selfhosted/awesome-selfhosted
Embrasure is an open-source, self-hosted secrets management tool built on Amazon Web Services (AWS) for small teams seeking simplicity and security.
Was excited to hear about self-hosted secrets management, but expected "self-hosted" to mean I can host anywhere, but the depends specific AWS features.
Perhaps "unmanaged" is a more appropriate term.
Certainly the article doesn't hit on power, but if it is "faster" and uses the same amount of energy then it should do the same about work and consume less battery.
Unfortunately from the article it's hard to tell anything from power consumption other then the Snapdragon X Elite 8 has a roughly 28W "TDP" and that the Elite A has 80W "TDP" and is only slightly faster. Still, this doesn't translate to real world power usage.
I'd love to see a real world benchmark that measures actual power consumption of these chips.
I typically (mis)use class diagrams as block diagrams for system design and interconnects.
Self hosted Gitea + Markdown + Mermaid diagrams
This affects Windows only.
Really feel that should've made it to the title other it feels like click bait.
Yes, this is how I have been living for the last few months and have seen and used both offers when I can't move to another retailer.
I remember thinking this shutdown was inevitable when they launched it... And never used it.
Google has created a self fulfilling prophecy.
HTML version: https://history.nasa.gov/SP-287/sp287.htm
Missing from the list is the BeagleV-Fire for $150 which was released last week with:
* RISC-V CPU: 4x 64-bit RV64GC application cores & 1x 64-bit RV64IMAC monitor/boot core
* FPGA: 23K logic elements (4-input LUT + DFF), 68 Math blocks (18×18 MACC), and 4 SerDes lanes of 12.7 Gbps.
[0] https://www.beagleboard.org/blog/2023-11-02-beaglev-fire-ann...
This is a follow up and conclusion to the HN post about the discovery of this a few days ago here[0].
Upstream commit is here[1]
Glad to see it has been root caused and worked around in such short order.
[0] https://news.ycombinator.com/item?id=37812556
[1] https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/...
Interesting walk through in the linked video as he tried to troubleshoot this:
https://www.youtube.com/live/1UnoBfw6soI
Pretty shocking to see (extremely unlikely) non-malicious code work / not-work depending on a security mitigation setting.
Curious to see where this goes as to whether it's a kernel bug and nobody is paying attention to `mitigations=off` now or the unlikely outcome that it's an actual hardware bug where mitigations work around it and nobody has noticed.
Seems he had overclocked and maybe disabling the migation has revealed an instability in his setup that's otherwise stable (or at best marginal).