irotsoma @ irotsoma @lemmy.blahaj.zone

Posts

0

Comments

209

Joined

6 mo. ago

My Meta account got locked without explanation and support couldnt tell me why, but suspiciously right after they implemented their new policies allowing hate speech but also I had deleted all of my posts going back to 2006 not long before that and had only been using it fir groups, so it wasn't as big of an impact so wasn't worth suing them to find out why I was locked out exactly or to start a new account.

GrapheneOS is great, but this move by Google may make it difficult for Graphene to continue to offer major updates. Only time will tell. But for the short term it's a great option.

I've decided not to invest in any more Pixels, personally. Even if they reverse the decision this time, it just means it will happen later, so then future versions of the OS will be out of reach or at least not as good as they could have been. I probably will keep my Pixel 7 Pro with Graphene until the battery is too bad for daily use.

Battery circuits come on enough to be a load that needs to be considered and will show up if you measure load on the device vs load consumed by the components connected to the power supply. In terms of low power devices, it is significant, though not the primary concern. But compared to the pi PSU, the charger not to mention the battery and internal PSU of a laptop, consume way more power and produce way more heat.

All of the rest assumes needing always on, heavy load processing which isn't what the post I replied to was talking about. I was specifically replying to idle power load. And in my case, even with a bunch of self hosted applications, most of the time my servers are idling. If I was running a virtualization farm or something that was always under heavy load, then yes, as I mentioned, a single board server isn't ideal.

As for disks, I don't use SSDs on my pis except one that actually does a lot of local data processing. Everything else runs in memory and stores persistent data on my NAS, including logging. Virtual memory/swap is disabled on all and things that need temporary storage/cache of small amounts of data is cached on RAM disks where applications can't be configured to not use disk caching. The only need for the SD card is for boot and some minimal IO needed for local OS operation. I have a Raspberry Pi 3 B i got about 8 or 9 years or so ago with the same SD card in it.

They aren't what I use as a database server, obviously, but they are extremely low power compared to what an old laptop would need and work great for things like pihole, and other network applications as well as being a part if my home kubernetes cluster and run the majority of the cluster's processes on demand.

Only if you're running it at full load all the time and comparing that to a comparable number of raspberry pis it would take to do the same amount of work. Also, only if you live in a cold climate and the heat generated is not a concern and power is supplied by a renewable source so power isn't a concern.

Not quite. Unless the system has pretty advanced power management and is using very recent technology with high density, it's unlikely that an x64 chipset will use less power than a comparably powered arm64 chipset. Not just the processor, but the smaller board is actually a power saver and allows it to generate less heat meaning both less power wasted and dissipated as heat as well as less power needed for fans to properly dissipate the heat. I've never seen a laptop use 3W at idle when considering the whole device, maybe just the CPU, but not if you include the rest of the components like RAM and disks and power supply. And especially true in a laptop that is old enough that it's being recycled. Heck, the power supply and charger alone might be using 3W at idle with full battery.

With a raspberry pi 4, the typical power usage for the 2GB RAM model is 5W under load for the whole device and about half that for idle. Add a couple of watts for the extra memory and wider bus on the 8GB model and other things can add to that, but that's mostly accurate. The pi 5 is a little more and the 3 is a little less. Of course, the efficiency of the laptop at full load might end up being better than a comparable number of raspberry pis it would take to do the same amount if work, but comparing a single pi or any other reputable arm-based, single board computer to a single laptop at idle is always going to be that way.

They hire experts to deal with it.

The issue with any crypto mining is that you can't uaually do it casually. You are generally competing with others to return the result first in order to get paid for a block. If you mine too slowly, you'll never actually complete any blocks. If you mine too fast, you use a lot of energy. The only way I found it economical for an average person over the long term is if it's not a popular coin, but popular enough to have some value or you generate a lot of excess power from solar and your power company either doesn't buy it or the rate is miserably low. There are short term scenarios where it can work, but much like the stock market, you need to be paying very close attention to profit margins, power rates, crypto price, current local temperature, etc.

Yeah, and it was a one off restore, so others who are mentioning self hosting will still be taken down as long as that policy remains.

Right, but taxing a CPU, PC Bus, and PC memory takes more electricity than doing the same amount of "work" on a GPU with longer, more specialized pathways, allowing more work on a single cycle, but less flexibility on the type of work. So if it takes 1hr fully taxing a CPU, PC bus, etc, vs 1 hour fully taxing a GPU and its integrated memory and bus, the one using the GPU is going to take more electricity. Also, you can chain GPUs which can't be done the same with CPUs since GPUs all have their own discrete bus and memory on a single card. Problem became that GPU production couldn't keep up with demand so they became more expensive for the hardware, but overall, the cost of electricity vs value of the blocks combined with producing fewer blocks on a CPU once the chains reach a similar complexity as a competing cryptocurrency, means that overall you're more likely to make more profit from GPU based mining than CPU based mining.

It's a complex calculation to figure out and many people mine without realizing the money they're spending on electricity, home cooling, and parts wear is more than they're making on the crypyo.

Even if the algorithm will perform better on CPUs than other crypto algorithms, there's still the fact that the processor in a GPU is much less complex and so: many more tasks can run in parallel because they're all very similar, the bus is much shorter, bandwidth to memory is much higher, and memory is generally much higher performing. So overall, mining on a GPU will generally be more energy efficient than on a CPU. And of course crypto becomes harder and harder to mine as they grow, by design.

Personally, I find Traefik much simpler than Nginx, especially with Kubernetes, but even with pure docker, but it's definitely not as performant. That's balanced by the fact that it does a lot of automatic detection and has dynamic config loading so I don't have to break other services when changing configurations.

Not sure that's true. And mining on a CPU is even less efficient. Your hash rate will be way lower unless you've got a really high-end system with a really low latency bus and RAM. And if your hashrate is too low, it would take months for you to find a single block unless you're pooling with a bunch of others and splitting the profit. It's quite variable, but very, very few people can make profit on any popular coins. Too many people to compete with to find a block.

Oh and don't forget cooling cost. The fans in the computer, the fans in your house, and your air conditioner in your house need to disipate the heat and there's a lot more generated per clock cycle from a CPU than a GPU using comperably old technologies. If you live somewhere that you're producing more electricity with solar than you consume, then it's probably not a cold climate.

They've been consumed for training already, but that data is harder to hand over as evidence in a court filing. It's not really human readable and isn't necessarily going to contain exact queries done by users and the output of those queries which is what the news orgs want.

That makes them think you aren't available, but if you have any kind of voicemail it means they know it's a real number so autodialers will probably still try later. I think this request is how can we fool the spammers (automated or otherwise) to think the number is totally invalid so they stop calling it.

That is difficult since there's probably some indication from the phone company other than just a voice message that indicates a number is invalid/unallocated.

That said, muting is the way I do it, but now most autodialer systems are configured to call twice in a row to get around the Do No Disturb settings on most cell phones, so it is more annoying now.

You still have an upstream DNS server that you rely on to provide updates to your unbound server. Problem is that corporate or extremist government controlled DNS servers can track all of your requests as well as censor any domains they don't approve of. And if DNS servers or their users don't use secure protocols, then those requests additionally are tracked by ISPs or any other systems the requests travel through as well as them having the ability to block individual requests they don't want fulfilled like the Great Firewall does or most corporate internal systems sometimes do to prevent employees from accessing social media or other sites they deem not work related.

Yeah, video streaming is not a good thing to put on a limited bandwidth server either directly or as a VPN or proxy passing data.

Best bet would be if you can set up a reverse proxy on your router and have that accept all inbound requests and direct to the correct internal server and port.

Yeah, that kind of defeats the purpose of using a "stable" distro though. As you mentioned, other better distros are available.

Problem with Manjaro is they have their own opinionated repository that is not always in sync with Arch because they try to introduce more "stability". I found this actually caused the opposite in most cases as there are a lot of dependencies that end up being behind and so you can't install more stable versions of a lot of software. With the complexity of modern software dependencies, it has become a big problem. Also, they have in the past caused lots of problems with AUR and have let their SSL certs expire multiple times. Overall, they just haven't been reliable IMHO, so I moved to Fedora a while back.

Yes, these are not "private" services, they are "secure messaging" services. Commonly confused issue. Privacy requires controlling the communication infrastructure. Security only requires controlling the items being shared.