If you haven't seen it, you might enjoy Benn Jordan's video of "saving" a PNG to a bird:
https://www.youtube.com/watch?v=hCQCP-5g5bo
(Besides the hook-y title, some interesting info on the acoustics of bird songs with some cross-over into tech.)
3,447 karma · joined October 9, 2011
If you haven't seen it, you might enjoy Benn Jordan's video of "saving" a PNG to a bird:
https://www.youtube.com/watch?v=hCQCP-5g5bo
(Besides the hook-y title, some interesting info on the acoustics of bird songs with some cross-over into tech.)
Depending what precisely you mean by the second one, you may not even need an AM/support for that.
They won't help me use the platform, but they will still address issues with the platform. If you run into bugs, things not behaving how they're documented, or something that simply isn't exposed/available to customers they seem to be pretty good about getting it resolved regardless of your spend or support level.
(On my personal account with minimal spend, no AM, and no support... I've had engineers from the relevant teams email me directly after submitting a ticket for issues.)
So yeah, "if you know what you're doing" you probably don't even need the paid-for support.
I thought it was retaliation for Canada not doing enough to stop their 20-odd kilogram contribution to the 4 tons of fentanyl smuggled in every year? [0]
(Which is to say I agree with you. Just trying to support your point that the reasoning has been so completely all over the map that anybody trying to assign any real meaning seems delusional. At this point I think most people have entirely forgotten half the reasons that have been made up along the way.)
[0] https://www.whitehouse.gov/fact-sheets/2025/07/fact-sheet-pr...
I've driven summer tires, all season tires, winter tires, and studded winter tires in every season in Canada. (Yes, I live in Canada and own borderline-usless summer-only tires. Yes, I've tried driving them in snow.)
None of what you're saying lines up with my own experience, various YouTube videos on braking distances, or literally anything else I've ever seen anywhere.
Edit: And, well, to be clear... I've lived on the West coast of Canada where it's a bit more mild but you're in the mountains, in the middle where it hits -50, and in the East where it only hits -30 but snows like hell.
While I've also got enough other stuff running that my 15 min load average is at 4 and I've got 83% RAM used ignoring buffers/caches/otherwise.
I went and grabbed a random benchmarking tool and pointed it at it with 125 concurrent connections.
Sustained an average of 13914 reqs/s. Highest latency was 53.21ms.
If there are 10,000 people online at any given time hitting the API on average once every 3 seconds (which I believe are generous numbers), you'd only be around 3.3k reqs/s, or about 24% of what my laptop could serve even before any sort of caching, CDN, or anything else.
So... if a laptop can't serve that sort of request load, it sounds more like an indictment of the site's software than anything.
With anything else (books or stories, pictures or movies, etc) the ability to modify or extend the work was the default. Copyright was a carve-out in this.
With software it's actually the reverse--the ability to modify or extend the work is _not_ the default. It takes explicit action by the creator to make that reasonable without substantial effort in most cases. We're actually dealing with an entirely different situation here, and providing that exclusivity on top really does seem like a bad deal for society in a lot of ways.
Is there anything else that's covered by copyright that's in a similar sort of situation as software? Where the thing that's covered by copyright _isn't_ really modifiable to begin with?
Which is a lot of words to say--on the surface, yeah, I agree with you. Besides shorter terms, I think if you want that exclusivity from society you should be required to give something back in return... like the source code so everyone can benefit from and build off of your work after your period of exclusivity expires.
Our cordless, on the highest suction setting, is bordering on unusable. The effort to move it across carpet becomes quite high. Trying to roll it on an area rug tends to cause it to drag the rug around, and if you pick it up while on it will pull the rug up off the floor.
I have done some _very_ scientific testing here, vacuuming a section of carpet on the lowest section (doing lines where each pass half-overlapped the previous so each part of the carpet got touched once in each direction), emptying the vacuum, then going back over doing the same on high. Didn't see anything else come up. Shop vac didn't pull anything else out either that I could see.
I used to be in a similar boat of "these are a stupid class of product", but end of the day even if it takes eight passes my wife was going to use it anyway. The effort for her to set the time aside to drag around the heavier corded vacuum which is a substantial effort for her, etc, would be more than doing eight passes with a cordless. So got a good one and I'm sold on it now--it is quite convenient, and it does work.
Only thing I will say is the battery definitely can't do an entire carpeted house on a charge. We don't have that much carpet, so don't have any problem cleaning all the floors and a couple area and entry-way rugs on a charge.
I think I could build a pretty clean and stylish looking office out of it.
No laptop banging around, no PC to hide away, etc. Could throw this on a minimalist or partially glass desk with an (unfortunate) single cable up to a monitor on an arm for video and power, use wi-fi, and essentially have a fully functional workstation for most people seemingly out of nothing. No bulky AIO, no PC strapped to the back of the monitor, etc.
So I guess that's my guess.
Though my impression from the linked page is more "HP doesn't know who this is for either". There's not much in the way of clear messaging, lifestyle photos, or anything else.
Sorry you missed out on simple, effective preventative health measures because of this misunderstanding.
So you're proposing they could be in a situation where they can either:
1. Publish an untruthful blog post, relying on public data available from multiple parties, trying to somehow explain it all while avoiding talking about their involvement in a way that would get them in PR, legal or political hot water; or
2. Publish nothing.
And they chose #1?
The only way #1 makes any sense at all is if some greater consequence to not publishing was put in place. But that would be more something like "the US gov essentially forced Cloudflare to write this" than "Cloudflare was part of this".
Unless they were part of this, _and_ the government forced them to write a post saying they're _not_ part of it and...
For my money: this is something in the news making it a good marketing opportunity which is ultimately what the blog is--trying to market Cloudflare and the brand to technical crowds.
I could justify it a number of ways, but the honest answer is "expiring these is more work that just hasn't been needed yet". We hit a handful of bad actors, banned them, have heard no negative outcomes, and there's really little indication of the behaviour changing. Unless something shows up and changes the equation, right now it looks like "extra effort to invite the bad actors back to do bad things" and... my day is already busy enough.
For some people it's an ideological one--we don't want AI vacuuming up all of our content. For those, "is this an AI user?" is a useful question to answer. However it's a hard one.
For many the problem is simply "there are a class of users that are putting way too much load on the system and it's causing problems". Initially I was playing wack-a-mole with this and dealing with alerts firing on a regular basis because of Meta crawling our site very aggressively, not backing off when errors were returned, etc.
I looked at rate limiting but the work involved in distributed rate limiting versus the number of offenders involved made the effort look a little silly, so I moved towards a "nuke it from orbit" strategy:
Requests are bucketed by class C subnet (31.13.80.36 -> 31.13.80.x) and request rate is tracked over 30 minute windows. If the request rate over that window exceeds a very generous threshold I've only seen a few very obvious and poorly behaved crawlers exceed it fires an alert.
The alert kicks off a flow where we look up the ASN covering every IP in that range, look up every range associated with those ASNs, and throw an alert in Slack with a big red "Block" button attached. When approved, the entire ASN is blocked at the edge.
It's never triggered on anything we weren't willing to block (e.g., a local consumer ISP). We've dropped a handful of foreign providers, some "budget" VPS providers, some more reputable cloud providers, and Facebook. It didn't take long before the alerts stopped--both for high request rates and our application monitoring seeing excessive loads.
If anyone's interested in trying to implement something similar, there's a regularly updated database of ASN <-> IP ranges announced here: https://github.com/ipverse/asn-ip
Unless it's completely clear that it's not a gun, the reviewer is essentially always going to pull the alarm. The risk of a false alarm is going to be seen as minimal, while the risk of a false negative is catastrophic.
False alarm makes the news for now because it's novel, we all go "What the hell, guys?" and life goes on.
Nobody wants to end up sitting in front of a prosecutor, the media, etc explaining why they chose not to pull the alarm, when the AI _clearly_ identified the gun, and instead chose to let all those kids die.
Also very common with... most Canadians. We officially use an English closer to British English (Zed not zee, honour not honor) however geographically and culturally we're very close to the US.
At school you learn "X, Y, Zed". The toy you buy your toddler is made for the US and Canadian market and sings "X, Y, Zee" as does practically every show on TV. The dictionary says it's spelled "colour" but most of the books you read will spell it "color". Most people we communicate with are either from Canada or the US, so much of our personal communication is with US English.
But also there are a number of British shows that air here, so some particularly British phrases do sneak in to a lot of people's lexicon.
See a similar thing in the way we measure things.
We use celsius for temperature but most of our thermostats default to Fahrenheit and most cookbooks are primarily in imperial measures and units because they're from the US. The store sells everything in grams and kilograms, but most recipes are still in tablespoons/cups/etc.
Most things are sold in metric, but when you buy lumber it's sold in feet, and any construction site is going to be working primarily in feet and inches.
If anything I expect any AI-written content would be more consistent about this than I usually am.
You could... fix it?
All headlights can be aimed. Even the "auto-levelling" ones have adjustments. I'm sure there are some where it requires some dealer-only programming tool, but a lot still just have little knobs and things. If they don't go ask the dealer to do it.
I drove behind a friend and they told me after that my headlight was shining in their side mirror and blinding them. I put my car in the garage and spent 15 minutes with a screwdriver adjusting the aiming on the auto-leveling sealed LED headlight units so it was lower and wouldn't blind people.
Look at the HN karma system--you start with limited features, and as you show yourself a good user, you get more features (and also trust/standing with the community). "Resetting" your identity only ever loses you something.
Apply the same thing to a git host getting hammered or something--by default, users can't view the history online or something (can still clone), but as your identity establishes reputation (through positive interactions, or even just browsing in a non-bot-like manner), your reputation increases and you get rate-limited access or something.
This is essentially where a lot of spam ended up--it used to be that your mail was deliverable until you acted poorly, then your reputation was bad and your deliverability went down. Now it more closely resembles this--your reputation is bad until you send enough good mail and take enough good actions (DKIM/SPF, etc) to show yourself as good.
The issues really all stems from "resetting your identity gets you back in good standing". Once you take that out of the mix, you no longer need to worry much about limiting identities, tying them to the real world, ensuring they're persistent, or many of the other hard problems that come up.
I've got the FW16 and have been very happy with it, but the portability isn't great given the size. No regrets given it was and always will spend 90% of its time on a desk.
I've been considering the FW12 as something more like a souped up tablet I could toss around the house, do some quick sketching on, etc.
You define your data in the "pkl language", then it outputs it as yaml, json, xml, apple property list, or other formats.
You feed in something like:
apiVersion = "apps/v1"
kind = "Deployment"
metadata {
name = "my-deployment"
labels {
["app.kubernetes.io/name"] = "my-deployment"
["app.kubernetes.io/instance"] = "prod"
}
}
spec {
replicas = 3
template {
containers {
new {
name = "nginx"
}
new {
name = "backend"
}
}
}
}
And then you `pkl eval myfile.pkl -f yaml` and get back: apiVersion: apps/v1
kind: Deployment
metadata:
name: my-deployment
labels:
app.kubernetes.io/name: my-deployment
app.kubernetes.io/instance: prod
spec:
replicas: 3
template:
containers:
- name: nginx
- name: backend
The language supports templating (structurally, not textually), reuse/inheritance, typed properties with validation, and a bunch of other fun stuff.They also have built in package management, and have a generated package that provides resources for simplifying/validating most kubernetes objects and generating manifests.
There's even a relatively easy path to converting existing YAML/JSON into pkl. Or the option to read an external YAML file and include it/pull values from it/etc (as data, not as text) within your pkl so you don't need to rebuild everything from the ground up day 1.
Aaaaand there's bindings for a bunch of languages so you can read pkl directly as the config for your app if you want rather than doing a round trip through YAML.
Aaaaand there's a full LSP available. Or a vscode extension. Or a neovim extension. Or an intellij extension.
The documentation leaves a bit to be desired, and the user base seems to be fairly small so examples are not the easiest to come by... but as far as I've used it so far it's a pretty huge improvement over helm.
One currently sits on my Framework over the Framework logo. The edge of the Framework gear sticks out in the bite in the apple and the sticker is thin enough the black framework logo shows clearly through the white of the apple.
On first glance, it looks like "trying to make a cheap laptop look expensive". On second it's looks like doing a really bad job of it. Anyone who actually knows the brand at all or asked about it will know the truth... it's making an expensive laptop look like a different expensive laptop.
So I guess it's not just the absurdity of the sticker, but how you use 'em.
Finally figured hey, I might have this laptop more than a single upgrade cycle... it's worth burning a weird sticker or two.
I still try and buck the trend a little--instead of advertising technologies or something, my general goal is that, at first glance, nobody would question anything or think it looks unlike any other developer laptop, but that anyone paying attention will instead be met with a fractal of confusion. E.g., one on there is a "STOP, DROP, AND ROLL" fire safety sticker. In Quebecois French. From a small town volunteer fire department.
I consider it sort of a personal art project and have fun trying to collect up the most "wait, what?" stickers I can.
I don't say this to diminish anyone else's contribution or criticize the software, just to call out the absolutely herculean feat this one person accomplished.
I had really good luck with Seafile[0]. It's not a full groupware solution, just primarily a really good file syncing/Dropbox solution.
Upsides are everything worked reliably for me, it was much faster, does chunk-level deduplication and some other things, has native apps for everything, is supported by rclone, has a fuse mount option, supports mounting as a "virtual drive" on Windows, supports publicly sharing files, shared "drives", end-to-end encryption, and practically everything else I'd want out of "file syncing solution".
The only thing I didn't like about it is that it stores all of your data as, essentially, opaque chunks on disk that are pieced together using the data in the database. This is how it achieves the performance, deduplication, and other things I _liked_. However it made me a little nervous that I would have a tough time extracting my data if anything went horribly wrong. I took backups. Nothing ever went horribly wrong over 4 or 5 years of running it. I only stopped because I shelved a lot of my self-hosting for a bit.
Wise needed beneficial ownership documentation for my business account. Presumably this was part of the whole KYC/AML/etc dance.
There's no standard form I could find for this, document to get out of the government service portal, or anything else. I finally just fired up a word processor and put together a single page document:
To whom in may concern,
Below is an accounting of all individuals who, directly or indirectly,
through any contract, arrangement, understanding or otherwise own equity
interests in 12341234 CANADA LTD.
NAME DOB Ownership
nucleardog 1970-01-01 100%
I hereby certify that the above information is correct as of Dec 31, 2037.
Nucleardog
President
12341234 CANADA LTD
No notes. They accepted it immediately and the account opening moved forward. Like... wat? Why was I stressed about this?(I have since written myself many things things like this, e.g., salary verification letters. Always gives me a chuckle and feels like a weird superpower I've gained by paying the $250 or whatever to incorporate.)
If I were someone that set up forged accounts and stuff professionally this would've been absolutely _nothing_ to bypass. As someone legit doing this _once_ for _a_ business, it definitely took a lot more research and thought that it really should have.
Yeah, if the banks could provide a service similar to Wise I'd happily use a bank.
My bank wanted ~$800/mo in foreign exchange fees for what I'm doing. Wise charges me ~$100/mo. That's, what, 700% more fees? I'm saving $8.5k/yr.
Even if Wise imploded tomorrow and I lost the cash I have in there I'm pretty sure after this long I'm still ahead versus having used my bank all along.
And there are a lot of value-adds on top.
I can get a Visa card that lets me pay directly in the foreign currency instead of paying the exchange fee twice. This was a whole separate expensive/specialty product from my bank.
I can send electronic transfers (through Canada's Interac e-Transfer service) that exceed what a local bank will provide even to my business account and completely avoid the need for additional services/hacks/fees/etc. This is, apparently, "impossible and not supported by Interac" according to multiple banks I've talked to, the business rep, etc.
Long story short... I agree. Wise only exists because banks are kinda terrible at this. If the banks sucked less, few people would bother with the friction of the additional account.
Never even thought about the fact that different regions may have different colour standards. This explains some of the power cables I've torn apart over the years and the strange colours I found inside!
> When I trained as an industrial electrician they where different colors, they changed in 2006 so that just makes me feel old (used to be Red, Yellow, Blue with Black for Neutral).
Making a mental note of that one... a black neutral would be a nasty surprise coming from North America.
Jails provide the same sort of primitive as cgroups et al wrapped up into the concept of an OCI container, yes. But lack the entire ecosystem of tooling and services that go around those.
Saying jails are a meaningful alternative to containers completely misses most of the ways in which people actually _use_ containers. The experience as-is is closer to a lightweight VM or LXC than what people associate with containers.
I say this as the kind of stubborn person that invested the time to spin up a cluster of FreeBSD machines running Hashicorp's nomad as a task orchestrator to manage running jails published to my "repository" across the cluster and recreate the general "container" experience. So my experience may be out-of-date, but this isn't from a place of ignorance or lack of love for FreeBSD, but from a place of "I've managed a colossal pile of bash scripts to recreate the container experience with jails and, no, for the average person it's not fair to call it the same thing.".
What value is that person adding? I can fire up claude code/cursor/whatever myself and get the same result with less overhead. It's not a matter of "is AI valuable", it's a matter of "is this person adding value to the process". In the above case... no, none at all.
Last time I remember feeling like that was the day I unplugged a RB5009 and it... just kept running. Was standing there holding the power cable in my hand, clearly unplugged, and the router was sitting there still happily blinking away. Like, this clearly can't be possible but I'm staring right at it and it's happening.
Took me a minute, but eventually realized the Starlink box that provides power to the dish _also_ provides power on the local side for their provided router as well, and apparently it was happily powering mine now.
Cameras are on their own VLAN. Port isolation is enabled so they can't connect to each other. Only connectivity allowed to/from that VLAN is from the cameras to the router for NTP, and from the NVR to the cameras.
So if you plug in you can... check the current time on my router. Maybe see how many other cameras are on that segment? Likely not going to get very far given you're already caught on camera, an alert's been fired, and pretty soon I'm going to be making a call to the police.