cstine @ cstine @lemmy.uncomfortable.business

Posts

0

Comments

86

Joined

2 yr. ago

Object skipping is a most welcome addition, especially given I've had a couple of print failures when a super skinny tall thing gets wonky and I'm forced to chuck it all to try again.

Wow, I'm shocked that they're going to sell the biometric data to anyone who wants it. Well, not that shocked. Actually, not shocked at all.

UptimeKuma is what I use; it'll watch tcp connections, docker containers, websites... whatever. And the notifications are pretty comprehensive and probably cover anything in 2023 would want to be using.

Just to be pedantic, it's not pull, it's push: the data is POSTed from the server that hosts the community.

Right now loading a page makes a bunch of API queries to pull all the related data for the posts, votes, sidebar info, and so on AND the API is very untuned and sending way more data than the WebUI/a client needs to actually generate a page: hence my 'it's less efficient' comment, though this is certainly something that can be tweaked to improve performance between the back and frontends.

I will, however, admit that this is only true if someone is actually reading the content they're subscribed to. The 'subscribe to everything' scripts turn this math on its head because now you are using resources to gather data you don't care about.

ActivityPub isn't anything more than JSON over HTTP(s); there's no reason at all that you couldn't simply tunnel all the traffic using hidden services over Tor using nothing more than the Tor daemon to create a hidden service and the proxy functionality to route all outbound HTTP traffic over Tor.

ActivityPub is not a distributed network: you don't have communications between servers in a mesh, the server that owns a community(ex. fediverse@lemmy.world) pushes out JSON data to any subscribers.

Small servers won't talk directly to each other, unless they're subscribed to communities on each other so having a lot of small servers doesn't actively impact the load on each other, but only on the larger servers that have the more active communities.

And, even then, the JSON requests are going to be a lower impact than a user actively browsing the site, though probably only marginally and maybe not in all cases.

I love the Silicon Valley techbros lately. Their sales pitches have gone from 'we have this cool new thing' to 'we've created something that solves the problems you didn't have until we created the problem you're now dealing with!'.

Much shareholder value or something, I guess.

IRC is extremely federated: building a network of linked servers sharing the same channels was done pretty early in it's existance.

If anything, IRC is more decentralized than ActivityPub-based services, because there's no 'home' server for a given IRC channel, and if thus if a server goes down, you don't lose all the channels that were created on it.

The windows version isn't released yet; the Mac version is.

Allegedly Windows is by end of year, but they're not really being exact with a date.

I think the top 3 reasons are, ultimately, the same reason; the people who are already there don't want you there, and they like the obscurity of discovery and obfuscation of communication, confusion around instances for onboarding, and ability to gatekeep exactly how you're allowed to use the platform.

There's issues with the underlying platform, for sure, but the established user base likes it the way it is, and is very strongly invested in preventing change.

And, that's okay! If you have a platform that you enjoy using, it should be defended, and aggressively.

But, at the same time, you shouldn't be utterly confused why so many people either don't want to or bounce right off your platform and aren't sticky when it's pretty obvious (and has been for a while) that the culture is the big driver for it.

That's fair; I wasn't really considering how poorly performing PSUs were at extremely low loads, despite knowing that they are.

Odd that a random brick would be substantially better than a same-era actual PSU, but I suppose it's hard to say without more specifics.

Partially it's a license problem. The MPL around gecko is much closer to the GPL than the BSD license that that Chromium blink uses, and thus it's much less appealing for commercial products to use it.

I've found enough interesting people to follow (along with Mastodon users, of course) that I'm happy, but that's entirely a personal and very subjective opinion.

Agree with this comment: Firefish is much better than the current state of Mastodon, especially since all the complaints you have are basically being wont-fixed by the current dev team.

The T variant is the low-power, lower clocked (3.2ghz vs 2.5ghz) almost half the TDP (65w vs 35w) variant; kinda the whole point is it's going to use less power.

The answer for your question is 'no'.

You're never going to reduce power usage substantially by swapping PSUs, because there's just not enough efficiency gains to be had even if a Pico PSU was more efficient which they really aren't.

You say the hardware is 'nothing too different' but you mention ddr4 vs 3, which makes me think the Dell is a generation or few older which could easily impact power draw by 10w.

Geeky yes, but Mark Lenard is great in every appearance.

Balance of Terror from TOS is, without any doubt, my favorite Star Trek episode.

I've kinda quit playing commander for most of the reasons Prof outlined: it feels like it's a never-ending arms race, and the way to win is to spend the most money at the table, fully aided and abetted by WotC's pricing on everything commander related these days.

Combined with the 'every deck is a 7' problem, it went from being fun, to being less fun, to being pretty sure I'm just going to get stomped.

So no more commander, and the last remaining bastion of MTG in my life lately is just pauper, because well, it's got a grand total of no $100+ cards in it.

Technically you're correct: your VPS provider can inspect your network traffic, the contents of RAM and anything on the disk.

Bluntly: you have to trust your VPS provider, and if you're unsure they're trustworthy you shouldn't use them.

(Scaleway is legitimate, bound by actual useful data protection laws, and has a comprehensive privacy and security policy.)