schizo @ schizo @forum.uncomfortable.business

Posts

6

Comments

1,240

Joined

1 yr. ago

It's because of updates and who owns the support.

The postgres project makes the postgres container, the pict-rs project makes the pict-rs container, and so on.

When you make a monolithic container you're now responsible for keeping your shit and everyone else's updated, patched, and secured.

I don't blame any dev for not wanting to own all that mess, and thus, you end up with seperate containers for each service.

Time to rename the blue shell to The Shell of Equity, I guess?

Or if you prefer to be a lot more cynical, he Old Yeller'd it, but he burned it's equity to get himself elected Co-President, and is worth like a hundred billion dollars more than he was before he did that.

So really, it was a Very Wise and bigly Smart business move.

I'm in the same boat, with a Quest 2.

My plan is to use it until it's no longer working, and then replace it with something from someone else, assuming civilization still exists by then and my desire for higher-resolution Beat Saber is still a concern and not scavenging for food, or fighting the raiders or whatever the hell.

I don't get the 'oh throw it out and buy a thing that's not from that bad company!' responses: that's the same dumb shit that led to people breaking beer and burning Nikes, which I can assure you nobody gives a shit about as they already have your money.

As I'm not a subject of the British Empire, I went and read what that law does and wow, is that a flaming pile of shit.

They basically said anyone who has a thing online that allows "user to user" communications is now subject to all sorts of bullshit, which includes social media companies, but also catches your blog because it has a comment section because they didn't even remotely try to carve out an exception for an individual doing a thing.

Can't imagine this'll do anything other than make people who can bail on the UK to do so (hosting is pretty fungible, and it's not like you can't host elsewhere that's still close enough to the UK to be fine) and screw with UK citizens and residents access to and ability to provide online shit.

you may see your mom

I hope not. I've got a strict no-zombies policy, and I'm certainly not violating it for her.

Those both have a Ring 0 component, which is essentially presented as required for the crap to even work.

The argument being that you have to have that level of access for the anti-cheat software to be able to actually be able to do it's thing, since if you just ran it with a normal user's permission, it'd be subject to numerous ways you could have a cheat tool simply bypass it.

They're probably not wrong about that, but doesn't mean that we should have to essentially install a rootkit on our hardware to play online games.

You kinda missed the most important detail: they're competing with the mid-range (and yes, a 4060 is the midrange) for substantially less money than the competition wants.

I know game nerd types don't care about that, but if you're trying to build a $500 gaming system, Intel just dropped the most compelling gpu on the market and, yes, while there's an upcoming generation, the 60-series cards don't come out immediately, and when they do, I doubt they're going to be competing on price.

Intel really does have a six month to a year window here to buy market share with a sufficiently performant, properly priced, and by all accounts good product.

Might have been unclear; I listen basically exclusively to spoken word stuff. Podcasts, audobooks, "raido" plays, etc.

The Airpods actually sound remarkably good and clear (and ANC helps a lot with ensuring clarity anywhere even slightly noisy) with voices, so for my uses, they sound perfectly fine.

I have a pile of Chi-Fi earbuds that absolutely destroy them in sound quality for music, but it's very much a 99.9% of the time it's not music situation.

Head to the lemmy github and subscribe to the releases email and you'll get one when a new version is out.

(And, unlike SOME projects I'm subbed to, they don't do anything that generates a ton of spam, so it really is just one-email-per-release.)

The best way I've heard that described is that for the Bambu stuff, you spend your time fiddling with the thing you want to print, not your printer.

I love my p1p (and it's several thousand hours and 100kg of filament into ownership and all I've had to do is clean the bedplate and replace a nozzle), and really wish there was anyone who was making an open-source printer that's as reliable and fiddle-free as this thing has been.

I'd probably go with getting the ISP equipment into the dumbest mode possible, and putting your own router in it's place, so option #2?

I know nothing about eero stuff, but can you maybe also put it into a mode that has it doing wifi-only, and no routing/bridging/whatever?

Then you can just leave the ISP router in place, and just use them for wifi (and probably turn off the wifi on the ISP router, while you're in there).

I've become a fan of staying one version behind for a month or two, unless there's a security issue that is involved in which case I'll patch.

I like it when someone who isn't me finds out the catastrophic breaking issues and has to do the cleanup, and I'll wait for the fixed version. :P

And if you fried your food in lard like God intended, this wouldn't have happened.

(Also screw things that need phone apps to function and especially screw phone apps that then ask for every permission they possibly can hoping people just spam 'fine whatever, i just want to make dinner' as the response.)

(/s, kidding, etc.)

Something that's made shockingly unclear, for anyone who might be interested: you only need to have subscribed for a single month to have all the subscriber gated stuff unlocked.

I don't really know how that's a viable business model, but pay $14 or whatever, get all the expansions and inventory and whatnot unlocked, and then don't worry about it until there's another expansion you want.

They really do.

The sound great, and the ANC is great, but the "official" battery life for a brand new one (which these are not) is "up to 4.5 hours" with ANC on, and 5 without it.

It ends up being 2-3 charge cycles basically every day, plus a full recharge of the charging case.

They do, however, work amazingly well if you're in the Apple ecosystem; for example they'll swap between my iPad and Mac Mini if audio starts on one or the other.

But for actually sitting down with something and listening to a thing, I'd rather just plug in some headphones (via the lovely USB-C dongle) and not have to think about if the stupid things are going to die before I'm ready to stop listening.

(Disclaimer: I'm also a weirdo who doesn't carry a smartphone, and still uses an iPod for listening to stuff outside of the house, so feel free to roll your eyes and disregard my obviously bad opinions :P )

My complaint has always been that the stupid things need to endlessly be recharged.

I've got some AirPod Pros and they're great... for about 4 hours.

Then you're stopping what you're doing, recharging for half an hour, and then you're good for uh, another 3 hours because that wasn't a full charge.

And after the 2nd or 3rd time you've done that, your case is dead and you get to throw everything on a charger for a couple of hours.

Ooooooooor I can put in my wired headphones, and not give a shit about any of that, because that's not how those work at all.

I suppose most people don't spend most of their day listening to podcasts and audiobooks and thus 4 hours is fine, but good lord is it annoying as crap.

Heh, I started another playthrough last night myself.

Never really gone through the Republic storylines, so I guess I've got a bit of game time ahead of me.....

You mean "Fuck you, getting my full bonus" right?

Then the correct answer is 'the one you won't screw up', honestly.

I'm a KISS proponent with security for most things, and uh, the more complicated it gets the more likely you are to either screw up unintentionally, or get annoyed at it, and do something dumb on purpose, even though you totally were going to fix it later.

Pick the one that makes sense, is easy for you to deploy and maintain, and won't end up being so much of a hinderance you start making edge-case exceptions because those are the things that will 100% bite you in the ass later.

Seen so many people turn off a firewall or enable port forwarding or set a weak password or change permissions to something too permissive and just end up getting owned that have otherwise sane, if maybe over-complicated, security designs and do actually know what they're doing, but just getting burned by wandering off from standards because what they implemented originally ends up being a pain to deal with in day-to-day use.

So yeah, figure out your concerns, figure out what you're willing to tolerate in terms of inconvenience and maintenance, and then make sure you don't ever deviate from there without stopping and taking a good look at what you're doing, what could happen if you do it, and coming up with a worst-case scenario first.