deadfece

If it does have an issue, you host all of your own data and you own 100% of the URLs involved on the QR codes.

Idk about the drama, I just get stuff done and keep going.

Homebox seems to be a good way to make that happen, FWIW. I looked at it for when I was moving house and it had way more than I needed. But it does support the QR code printouts.

Oh I don't know, 2? or 3?

At least they gave us some notice, that’s much appreciated.

Seems like that was what they set out to prove.

Hopefully some of that can be reproduced in further studies.

If you’re just checking alignment or fit on FDM printing, sometimes I just print those specific layers 1mm high and see if I got it right. I also cut away the parts of the model I’m not trying to fix.

Just anything I can do to subdivide the problem space and iterate more quickly.

Since there’s some spool up time on printing (heating up and leveling) sometimes I also bracket parameters 5% on either side of my value and print 3 tests to see if those fit better or worse

If you access grepular outside of Iran, you get something even worse: their website.

Why use this over datasette’s `llm` ?

alias localports='ss -plunt'

In Oklahoma, they tried to market a bitcoin farm project as a datacenter. It received a lot of opposition due to the noise levels anticipated.

The graft team tried to get the state government to give tax graft to "datacenters" but didn't define what a DC was - which could mean the graft might go to bitcoin farms as well.

I noticed that the article does not really distinguish between any of these.

Please excuse my English, graft is not my first language.

Netgear did a switcharoo on me after the fact with my Nighthawk. When I got it, I was able to just open the app and manage it locally. I don't remember what it was but the thing I was after definitely worked a lot better from the app. Then they updated it and required you to make a Netgear account to manage your local device. I was able to trick it into thinking I was offline for a while, and I found that would let me log in locally, but eventually that quit working too. I uninstalled the app and then just managed it from Firefox mobile. Their web UI wasn't remotely good, but it worked. Luckily I didn't have to make a ton of changes to it from there on out, since I was just using it as an AP at that point. When I moved, I got a much better AP for the new place.

It makes me curious what that bar is for suspension. Our incident team has never been able to get any registrar to shut down any site for fraud or spam, even with copies of our investigations.

In my experience these web agents are relatively expensive to run and are very slow. Admittedly I don’t browse HN frequently but I’d be interested to read some of these agent abuse stories, if any stand out to you. (I’ve been googling for ai agent website abuse stories and not finding anything so far)

I always say something like "Let's make it work so well that it's completely boring. Let's build tomorrow's 'boring'."

I just use a bookmarklet for Archive.Today , it's easy enough.

https://gist.github.com/573/e5cf230a03c5d53f848b58c3ced0bc95

Solution building: I don't really see anything in that use case that would prevent it from using inotify/incron, so I would probably evaluate that side first.

This is not a good look, Matt.

Allow me to offer my opinion without reading the article:

I can and do pay for news, I just dislike the bait and switch with modals/popovers that much. Now that I can no longer block domains in my Google search results, I can't remove those paywalled sites from relevancy and it's hard to keep track of everyone who only lets you read the first paragraph and a half before sticking their hand out asking for $10.

ETA: I have now read the article and have no revisions to my statements.

I have to admit I wasn't familiar with IoC for appdev. I only knew of that initialism as "Indicators of Compromise" from infosec.

Ah, I thought we were having a discussion in good faith. Later!

That maintenance problem is sometimes also expensive in terms of service costs. Which is more of a tech debt problem than a cloud comparison, honestly, but they're often inseparable.

Extended support costs on old hardware and software are sometimes astronomical. Then you're paying all of that to get something that, compared to modern gear, performs like ass and just breaks all the time.

I've also had C-suites tell me I have two months to start a project and have all the gear live, but I find we are only allowed to order direct from the manufacturer, and our orders will take 90 days to get to our door. Oh boy. That scenario is difficult to put into terms of money. Sometimes having that one-hop instant supply chain into a cloud service is a huge business enabler, sometimes it's not.

The article honestly reads as if written by a very smart sysadmin with zero cloud experience.

1:1 lift and shift is always obscenely more expensive. In this case, if the author had been in charge of the migration, then yes, the services would have cost them dearly to operate in the cloud.

I'm sure if I was personally put in charge of moving some aspect of IT into an unfamiliar mode of operation, my inexperience there would make my approach insanely expensive as well.

That says nothing about the target, except that having undertrained and inexperienced staff in charge of its design and implementation is probably foolish from a financial perspective.

There are obviously thousands on thousands of scenarios where moving to commodity cloud is an absolute slam dunk in aspects that are important to the subject business.

Unfortunately we really get no insight into what the workload truly is in the article's comparison. There's no mention of solution aspects like app architecture, security, HA/DR, SLA, RTO/RPO, security or backups [1]. We only get what is plainly a tunnel-vision view of a comparison.

It's almost like the author doesn't make solutions for a living.

Maybe the author actually realizes their blind spot, and is secretly utilizing Cunningham's law to crowd-source a relatively free solution from the professionals and amateurs in the internet comments sections.

The good architects don't work for free. There's a reason why Troy Hunt's web services cost him vanishingly little to operate, and it's certainly not by running IaaS VMs 24x7x365.

[1] I mentioned security twice as part of an ongoing effort to make up for all the times CyberSec/Infosec teams have been forgotten in the planning process. =P

I've worked places where they had so many databases from M&A that half of their FTEs were wholly preoccupied all year with performing outstanding DB maintenance: fixing backups, doing storage management, patches, applying move/add/changes.

For them, managed DBMS was a life-changing event. As soon as they had RDS or even Azure SQL MI, they were begging the cloud team for more, so they could get their team back.

In some businesses, it's definitely not a big loss to lose agility by having a large portion of your team tangled up in infrastructure management, but for some businesses, that constraint is an impediment to their line of business. Some businesses are missing opportunities for want of infrastructure being able to move fast enough.

First off, why are you using Ansible/Packer against Windows Container images ? You wouldn't fault Linux Containers for being terrible to use with Packer/Ansible because you shouldn't be doing that.

You can build Linux containers just fine with Packer/Ansible. But to your point I already stated why I use Ansible and Packer for container images: "if you're already using those to configure VM images and Ansible to perform config mgmt on VMs"

I currently build a number of images with Packer and Ansible across Linux and Windows. I choose not to rewrite all of that from scratch in a crummy Dockerfile when I can just have Packer and Ansible make the images alongside everything else they're already making.

My main advice on Windows Containers is to avoid them at all costs.

A lot of the things that ran in Windows Nano Server worked even better in Linux containers, and a full Windows Server Core container is usually only necessary for .NET Framework, where you will need all of the luck in the world help you with that problem.

Packer and Ansible are also much harder to use for Windows Containers, so if you're already using those to configure VM images and Ansible to perform config mgmt on VMs, get ready for some headaches to make that work against Windows Containers.

I have used Ansible for my Windows desktop setup for several years now, and I haven't fought those things in it. It has been pretty straightforward as I'm mostly just installing software and pulling some configs and scripts down.

Oh god I've turned into an old crotchety unix guy.

That's kind of my take on it as well. I don't care what it is, I can make it work. If I couldn't make it work, I would be the wrong guy for my job.

At this point you could give me a FreeDOS machine and I'd be like "Well this initially looks super inconvenient, but I realize you won't be able to VOIP call me through the device, and it looks like I can get enough stuff installed to SSH to our dev environment. We're good."

Joke's on them, I'm from the dialup era and don't even notice.

I live in a smaller city outside of a metro. I can hear goats from a farm next door, but I have 5gbps symmetric fiber.

We have an ALDI here at least.