schizo @ schizo @forum.uncomfortable.business

Posts

11

Comments

1,437

Joined

1 yr. ago

Part of it is 'can the current license facilitate them doing a rug pull'. A LOT of the licenses on these new tech darlings are written in such a way that they absolutely can change the terms, close the source and/or dramatically restrict access, and you can go get fucked.

They use Contributor License Agreements to ensure they own all the rights, and whenever they feel it's advantageous for them, suddenly it's now under a new, more restrictive license because there's nothing in the old license that stops them from doing so.

I'm a big fan of actual, real, forced-to-stay-open licenses like the AGPL and very much against CLAs because those two stances are essential for what's open and useful staying open and useful.

Whatever this is licensed under is... not that.

I totally wanted this a bit ago, but couldn't justify it.

It just costs too much in relation to a Threadripper box, and doesn't have the same performance. For 5k you get... 4 cores, and while SMT4 is neat, it's not going to make up for, as an example, the 32 cores a 7970X (which ends up building out at about the same price) has.

It's kinda only useful if you're willing to spend a huge amount of money for okay but nothing special performance, need the more open platform aspect, or are doing POWER development.

If it was half the cost, it'd be twice as appealing, but, well, it's not.

Good news! .xyz is no longer the top malicious non-com/net/org domain.

It's uh, .top now. https://www.spamhaus.org/reputation-statistics/gtlds/domains/

Yeah, the Prescott P4s and the dual-core P4s were both extremely good at being space heaters while also being extremely bad at being a CPU.

The whole P4 era was a suckfest for Intel, and they didn't really shake the slow, hot, power hungry thing until Sandy Bridge (so basically 2000 to 2011 ish). And before anyone mentions them, Core/Core 2 were MUCH more performant and certainly better performance-per-watt than the X2/X4 Athlons, but still not particularly efficient in comparison to Sandy Bridge and later.

I'd also argue Bulldozer wasn't necessarily a bad uArch, but it just had a couple of poor design decisions that made sense historically but did not really work in practice, and had fucking awful timing going up against Sandy Bridge, which was fucking excellent.

Its all about monetization. YouTube is the only credible game in town and I'm not sure how you fix that.

The technical hurdles are largely solved: something like peertube is good enough, except there's no clear path to monetization and no clear path to growing an audience.

If the money problem and discoverability are solved then sure, I bet a lot of creators will happily leave googles services since its been an abusive relationship for some time for a lot of them.

It makes people who WANT to make creative content decide maybe they shouldn't, or they do things like disable subtitles so AI won't steal content via that means which is a usability issue.

If you know that your photos, stories, videos, and whatever else were going to be slurped up so someone else could make money on it, it makes sharing less attractive.

Because the techbros know that licensing is far more expensive than theft.

It'd cost so much money to license the content that the AI model they're trying to shit out needs that it'd literally never be profitable, so they're doing that thing from Fight Club where they assume the number of times they'll get sued and lose is going to cost less than paying anyone reasonable license fees.

The stupid thing is, that in the US at least, they're not wrong: in a civil suit over this you have to pay for your own lawyer fees, and since this would be a Federal case, that ends up being pretty expensive.

And, even if you win, you're just going to likely get statutory damages since proving real actual losses is probably impossible, so you'd be lucky if, after a few years in court, to end up coming out ahead - and having to pay for all the legal and other costs in the mean time - so why would you bother?

It's a pretty shitty situation that's being exploited because the remedies are out of the reach of most people who've had their shit stolen so that OpenAI can suggest you cover your pizza with glue.

I hate to be that guy, but do you REALLY think that on-device AI is going to prevent all your shit being sent to anyone who wants it, in the form of "diagnostic data" or "usage telemetry" or whatever weasel-worded bullshit in the terms of service?'

They'll just send the results for "quality assurance" instead of doing the math themselves and save a bundle on server hosting.

They don't ignore it, they just make sure that they have a friendly judge say it wasn't illegal when they did it. Much more civilized that way.

The hilarious thing is AMD probably won't need to learn their lesson: their chips are using about half the watts for the same performance. This is firmly an Intel failure and them jucing the silicon past it's ability to cope to win benchmarks.

And their Zen5 cores look to be even more efficient than Zen4, so I'm sure some engineers at AMD are laughing about this whole thing.

And, of course, that 253w PL1/2 limit is a lie: these chips will absolutely pull north of 400w (450w for the 14900k!) if you let them.

That's a whole-ass computer from not that many years ago, and it's not entirely surprising they're having issues.

Nice to know that Qualcomm's still doing everything possible to make sure you can't just use the damn hardware you bought from them without their permission.

Yeah, seriously. If they had only shown things that actually existed, I'm pretty sure all the negative press would have been totally avoided since even at release it was a solid enough story-driven RPG.

Mostly just the amount of my power bill.

I mean all the usual arrs and overseerr and jellyseerr and such are already on github, so it's... probably fine?

60% of the time, it works every time.

Of course, 60% was a hell of a lot more than 95 managed, so still impressive?

Two things, I think, that are making your view and mine different.

First, the value of time. I like self-hosting things, but it's not a 40 hour a week job. Docker lets me invest minimal time in maintenance and upkeep and restricts the blowback of a bad update to the stack it's in. Yes, I'm using a little bit more hardware to accomplish this, but hardware is vastly cheaper than my time.

Second, uh, this is a hobby yeah? I don't think anyone posting here needs to optimize their Nextcloud or whatever install to scale to 100,000 concurrent users that required 99.999999% uptime SLAs or anything. I mean yes, you'd certainly do things differently in those environments, but that's really not what this is.

Using containers simplifies maintaining and deploying, and a few percent of cpu usage or a little bit of ram is unlikely to matter, unless you're big into running everything on a Raspberry Pi Zero or something.

All of this is investor driven, and a lot of the announcements are 'Yes, people giving us millions of dollars to do things, we're going to make a 2nd game in this series'. You need to announce what you're doing so you can get people to give you the money to fund doing the thing you want to do, since I'm entirely certain CDPR isn't sitting on funding to go off for 5 years and make a game without telling anyone anything.

The hype train is mostly driven by game journalists that see that a company is going to make a game, and then do the clickbait 'GameCo announces Game 2! Here's 10 things that we think will be in it!' listicles for the next few years, which skews everyone's expectations and can drown out more tame discussion since who doesn't like hype?

Things can be true and also be misleading.

This is just shitty clickbait journalism. A more accurate headline "Anticipated Fallout 4 mod won't work on current Fallout 4 versions" wouldn't get the engagement and clicks that a more provocative bullshit title that indicates that Epic won't let you play it does.

Yeah, I'm entirely sure it's upstream of Chrome proper, and kinda consolidates my opinion that anything Google is near should be treated as suspect.