Thank you. I stole that from Philip (I think) in Off To Be the Wizard by Scott Meyer. He was describing that book’s antagonist but I’ve taken it to describe people who casually break rules to get ahead.
And I think that’s kind of what they’re doing, flooding social media with stories of how they broke rules in ways that make me go “foul! That’s a foul! Why is the ref doing nothing? This breaks my brain and I have no idea how to respond to this!”
I hope they explain further. Honestly I don’t think the “oh crap I need to know if it’s good or bad right now!” camp is really going to care, but it still feels a little uncomfortable. (As opposed to the “this could be either way, I don’t have enough evidence to decide right now, and I’m ok with holding that uncertainty in my brain until new evidence moves my needle” camp)
Are forked builds possible with third party service references neutered?
I love this, and I’m definitely going to use it when describing enshittification to relatives. Kudos, genuinely.
Think of a Seedbox as a cloud service provider with convenience features focused on enabling piracy, by keeping the hardware in a jurisdiction that doesn’t care what you pirate and giving you one-click easy installation methods for apps that make piracy simple. But without going so far as “Thank you for your payment, download these specific media files here.”
You debatably have to be a techie. But by techie standards it’s very easy to use.
If you really hate piracy, I suppose you could pay for one for a month, get the identity of who you paid, and use one of the apps to host a shell script that listens on one of the few public ports you have access to, that answers every incoming connection with “this is a seed box operated by ABC, with cards payments accepted by LMNOP Inc in Athens, Greece.”
But the most common usage is running packaged software they let you run (like BT clients you can remote-control, sickchill, radarr, sonarr, Plex, etc.) or remote desktops or shells. Usually implemented as docker containers.
BBS software. Nerds always find a way. I guess if I have to be a sysop now…
I’ve been ranting about this a lot lately, but as the owner of mspencer.net (completely useless personal domain, but is 199 days older than wikipedia.org for what it’s worth)…
There is sort of a way to do that, but it’s still labor intensive so not a lot of people do it. Movements to investigate are homelab and selfhosted. Homelab equipment is old (extra power-hungry for the capability you get) or expensive. Self hosting requires a bunch of work to stand things up the way you want it.
Biggest barriers to self hosting - or hosting through your nearest nerdy relative - are the following:
Free ad-supported offerings (with the privacy and terms and conditions impacts you describe) are better and easier, so they out compete DIY options. If a nerdy family member offers to host forums and chat for your community club or whatever, the common response isn’t gratitude, it’s “That’s stupid, I’ll just use Facebook.” Without that need and attention, volunteer projects get way fewer eyeballs and volunteers are way less motivated.
Security is difficult to figure out. Project volunteers have enough on their plate just helping users get their stuff working at all. Helping novice users secure their installations is so much extra work.
Many volunteers feel taken advantage of if they produce something that could help companies make money better, when they don’t share any of the money they make through donations or support arrangements. Similarly, many open source projects get taken over by for-profit companies who diminish efforts to make their open source offerings easier to use for free. (They want companies to buy support contracts, even if it means frustrating use by private individuals without kilobucks to spare.)
Married, we both work from home, and we’re in an apartment.
First, all of my weird stuff is not between her work and living room pcs and the internet. Cable modem connects to normal consumer router (openwrt) with four lan ports. Two of those are directly connected to her machines (requiring a 150-ish foot cable for one), and two connect to my stuff. All of my stuff can be down and she still has internet.
Second, no rack mount servers with loud fans, mid tower cases only. Through command line tools I’ve found some of these are in fact capable of a lot of fan noise, but this never happens in normal operation so she’s fine with it.
Separately I’d say, have a plan for what she will need if something happens to you. Precious memories, backups, your utility and service accounts, etc. should remain accessible to her if you’re gone and everything is powered off - but not accessible to a burglar. Ideally label and structure things so a future internet installer can ignore your stuff and set her up with normal consumer internet after your business internet account is shut off.
Also keep in mind if you both switch over so every movie and show you watch only ever comes from Plex (which we both like), in an extended power outage situation all of your media will be inaccessible. It might be good to save a few emergency-entertainment shows to storage you can browse from your phone, usb or iXpand drive you can plug directly into your phone for example.
Advice from most to least certain: If you want very long standby time (a reliably perfect first print after literally months of inactivity) and you have the space for an ugly cube of a printer, laser is the only option. Ink tank printers have unexpected wear parts, like internal ink sponges.
Black and white laser is stupid simple. Color laser “prints” four times in series onto an intermediate transfer belt (ITB) and then puts that onto the paper, still super reliable but bulkier, and your prints get watermarked with yellow dots because FBI or something. I’d go color.
Toner lock-in is becoming more common, not just for HP. If your page count is going to be low, just pay full price for name brand toner. If you don’t want to do that, like your use case could involve printing a single page or entire binders of paper between months of inactivity, read on.
Start your printer research by shopping for cheap off brand toner, get a sense for what they’re selling the most of and what that’s compatible with, and see what printers they support.
Some aftermarket toner just works, out of the box, because the printer isn’t crazy locked down. Those cartridges have normal sounding instructions. Some aftermarket toner requires you to transplant a chip from a first party cartridge, and their instructions include this. Avoid those printers.
And consider used printers. I have a used HP LaserJet Pro MFP M477fdw that I love, but I would never ever buy another HP printer, especially not one made later than this one. Be very careful before buying any HP printer, especially one made in the past 6-8 years. Even wear items (like the ITB) have modules with firmware and compatibility requirements, and I’m worried I could be one replacement component away from suddenly having a locked down printer.
I’m not sure I follow. Why would a needle be reused? That’s never ok to do.
The pictured injector is single use. The weird workaround would never be ok’d by any doctor, and even if it was, a clean needle would be used to withdraw and administer medicine from the hypothetical medicine ampule for each dose. I’m not qualified to measure loose liquid medicine, and she’s on the second highest dose anyway.
A better design would be more like the pen used by the original senaglutide medication this is related to, ozempic. Screw on a disposable pen needle, dial your dosage on the twisty knob on the other end, inject, dispose of needle. But instead they deliberately designed this thing, with a latching device that starts squirting medicine with no way to stop it. If the user is not familiar with needles and jerks away, the needle comes back out but medicine is still squirting.
It’s a good medicine, except supply issues are making it difficult. My wife’s refill at the hospital pharmacy has been pending since end of February. It’s a weekly injection but her last dose was 15 days ago as of this morning.
Agreed. They are deliberately taking advantage of the fact that people don’t understand how autopilot is actually used in aircraft.
Sure, the most pedantic of us will point out that, with autopilot enabled, the pilot-flying is still in command of the aircraft and still responsible for the safe conduct of the flight. Pilots don’t** engage autopilot and then leave the cockpit unattended. They prepare for the next phase of flight, monitor their surroundings, prepare for top-of-descent, and to stay mentally ahead of the rapid-fire events and requirements for a safe approach and landing. Good pilots let the autopilot free them up for other tasks, while always preparing for the very real possibility that the autopilot will malfunction in the most lethal way possible at the worst possible moment.
Do non-pilots understand that? No. The parent poster is absolutely correct: Tesla is taking advantage of peoples’ misunderstanding, and then hiding behind pedantic truth about what a real autopilot is actually for.
** Occasionally pilots do, and many times something goes horribly wrong unexpectedly and they die. Smart, responsible pilots don’t. Further, sometimes pilots fail to manage their autopilot correctly, or use it without understanding how it can behave when something goes wrong. (RIP to aviation Youtuber TNFlygirl who had a fatal accident six days ago, suspected to be due to mismanagement of an unfamiliar autopilot system.)
It sounds like you’ve got enough familiarity with the whole development lifecycle, as applied to a smaller single-dev-sized project, that you’d be great as an SDE 2 at a larger company, ready within a few years to step up to Senior. There are companies with hundreds of developers who only rarely hire straight out of college, where your level of experience is exactly what they want.
(There are also companies with hundreds of developers who do hire straight out of college, and I’m not trying to disillusion recent grads.)
Ohhh I get you then. Instead of checking against an author’s key, and building a distributed web of trust between trusted authors, you build a system that requires everyone collaborate on one shared chain of signatures.