486

@486@lemmy.world

This is a remote user, information on this page may be incomplete. View at Source ↗

⁨Comment⁩ on ⁨‘The tyranny of apps’: those without smartphones are unfairly penalised, say campaigners⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:
Yeah, Bonzi Buddy!
⁨Comment⁩ on ⁨Intel Becomes Potential Takeover Target Of Broadcom, TSMC: Reports⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:
There is also AMD and they are doing pretty well. I wouldn’t write off x86 just yet.
⁨Comment⁩ on ⁨Elon Musk’s X blocks links to Signal, the encrypted messaging service⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:
It is, but Signal and Matrix aren’t really all that similar. Matrix’s privacy is pretty atrocious. It stores tons of meta data about users all over the place. That’s the exact opposite of what Signal does.
⁨Comment⁩ on ⁨Intel Becomes Potential Takeover Target Of Broadcom, TSMC: Reports⁩ ⁨⁨1⁩ ⁨week⁩ ago⁩:
Ugh, Broadcom buying Intel would be terrible.
⁨Comment⁩ on ⁨Homelab upgrade - "Modern" alternatives to NFS, SSHFS?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:
Sure, if you have exactly one client that can access the server and you can ensure physical security of the actual network, I suppose it is fine. Still, those are some severe limitations and show how limited the ancient NFS protocol is, even in version 4.
⁨Comment⁩ on ⁨Freed At Last From Patents, Does Anyone Still Care About MP3?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

You need sampling at twice the frequency as a minimum to extract a time domain signal into the frequency domain. It says nothing about “perfect” especially when you’re listening in the time domain.

Yes it does. You can use a higher frequency, but that does not change anything except increase the maxiumum frequency possible. Even with perfect ears and the best equipment, there is no audible (and mathematical) difference to be had.

Everyone who claims otherwise should watch Monty’s explainer videos. I know they are quite old at this point, but everything he explains is still perfectly valid. If that does not convince you, nothing will.
⁨Comment⁩ on ⁨Freed At Last From Patents, Does Anyone Still Care About MP3?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

It turns out that dynamic range is limited by the audio sampling rate and the human ear can easily detect a far greater range CD audio supports.

Dynamic range isn’t limited by the sampling rate. It is limited by the resolution, which is 16 bits for the audio CD. With that resolution you get a dynamic range of 96 dB when not using any dithering and even more than that when using dithering. Even with “only” 96 dB that dynamic range is so vast, that there is no practical use of a higher resolution when it comes to playback. I know that the human ear is supposed to be able to handle 130 dB or even more of dynamic range. The thing is, you can only experience such a dynamic range once, afterwards you are deaf. So not much point in such a dynamic range there.

There are good reasons to use a higher resolution when recording and mixing audio, but for playback and storage of the finished audio 16 bits of resolution is just fine.
⁨Comment⁩ on ⁨Homelab upgrade - "Modern" alternatives to NFS, SSHFS?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

NFS is bulletproof.

For it to be bulletproof, it would help if it came with security built in. Kerberos is a complex mess.
⁨Comment⁩ on ⁨Homelab upgrade - "Modern" alternatives to NFS, SSHFS?⁩ ⁨⁨2⁩ ⁨weeks⁩ ago⁩:

If someone compromises the host system you are in trouble.

Not only the host. You have to trust every client to behave, as @forbiddenlake already mentioned, NFS relies on IDs that clients can easily fake to pretend they are someone else. Without rolling out all the Kerberos stuff, there really is no security when it comes to NFS.
⁨Comment⁩ on ⁨What do people use for a shelf-stable backup⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

archival strength USB NVME drive,

Does such a thing exist? Ordinary flash storage is pretty ad at keeping its content when powered off for a long time, due to how flash memory works. I’d be curious about such drives.
⁨Comment⁩ on ⁨What do people use for a shelf-stable backup⁩ ⁨⁨3⁩ ⁨weeks⁩ ago⁩:

Thanks, I think the risk here is that there may not be hardware to read it.

M-Disc DVDs are readable by ordinary DVD drives. So you could simply put a USB DVD drive alongside those backup M-Discs on the shelf.
⁨Comment⁩ on ⁨No Frills PCB Brings USB-C Power To The Breadboard⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:
Missed opportunity there, not being able to select all the other available USB-PD voltages. Not every circuit runs on 3.3 or 5 V.
⁨Comment⁩ on ⁨AMD captures 28.7% market share in desktops⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:
Actually AMDs mobile parts are pretty good at idle power consumption and so are their desktop APUs. Their normal CPUs, which use the chiplet design are rather poor when it comes to idle power consumption. Intel isn’t really any better when compared to the monolithic parts at idle and Intel CPUs have horrible power consumption under load. Their newest CPUs are better when it comes to efficiency than 13th and 14th gen CPU, bus still don’t match or even exceed AMD.
⁨Comment⁩ on ⁨Australia struggling with oversupply of solar power⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:
With spinning turbines, the issue is, that you need to maintain a constant speed of the turbine at all time. That rotation speed directly correlates with the mains frequency. That’s either 50 or 60 Hz depending on where you live. If the load increases by a lot the frequency drops and the turbine speed decreases, when the load decreases, the opposite happens. The people maintaining the grid have to make sure load and supply are in balance to keep the frequency stable and the trubines within their operating parameters.

Compared to that, solar panels have none of these constraints. For one, the output DC voltage not AC, and secondly they don’t mind at all when there is no or very little load. So you can easily simply disconnect solar panels when there is too little demand without any issue. You can’t easily do the same with a power plant with a turbine.
⁨Comment⁩ on ⁨Australia struggling with oversupply of solar power⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:
While that is true for power plants with spinning turbines, it isn’t true for solar power. There is no issue at all when you don’t consume all the energy that a solar panel could produce.
⁨Comment⁩ on ⁨Solar modules now selling for less than €0.06/W in Europe⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

MW/h

There is MW which is a unit of power and then there is MWh which is a unit of energy, but what is MW/h supposed to mean?
⁨Comment⁩ on ⁨JetKVM - a polished take at the nanoKVM(?)⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:
Why? Even 1080p is more than what is usually needed for such a KVM solution. It is not like this is meant for doing remote work on a computer or anything like that.
⁨Comment⁩ on ⁨JetKVM - a polished take at the nanoKVM(?)⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:
It lets you remotely control a server as if you were sitting in front of a screen and keyboard directly attached to it.
⁨Comment⁩ on ⁨Bitwarden Makes Change To Address Recent Open-Source Concerns⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:
I was really sceptical of the CTOs first response, but this does actually seem to be genuinely good news.
⁨Comment⁩ on ⁨Concerns Raised Over Bitwarden Moving Further Away From Open-Source⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:

The head of BitWarden has come out and stated the SDK being required to compile BitWarden was a mistake, however, and if this proves to be true (which I have no reason to doubt) then I see no reason why any of this is an issue.

I don’t see why this should make any difference at all. Sure, I get why he is are saying they are going to fix it - he thinks that this gets them in compliance with the GPLv3. But from a practical point of view there is no difference at all. The software is useless without that SDK part. Even if it does indeed get them in the clear from a legal point of view (which I am not convinced that it actually does), it is still a crappy situation.

I think, it would look way less shady, if they said they are going fully source-available and not pretend that they are keeping the client open source. I would still dislike that, of course. At least that wouldn’t have eroded the trust in them as much as it did for me.
⁨Comment⁩ on ⁨Concerns Raised Over Bitwarden Moving Further Away From Open-Source⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:

Proprietary is a strong word IMO. Here’s the repo, it’s not FOSS, but it is source available.

Yeah, that’s what I meant by “proprietary”. I guess having the source to look at is better than nothing, but it still leaves me uneasy. Their license lets them do anything they want (ignoring that - as it stands - their license is void due to the linkage with GPLv3 code, but they said they want to fix that). I have no idea what their plan is. I don’t think it is in their best interest to go the route they appear to be going. Having truly open source clients seems to be a selling point for quite a few customers. But what do I know…
⁨Comment⁩ on ⁨Concerns Raised Over Bitwarden Moving Further Away From Open-Source⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:
I really hope that this is actually the case, but I am not very optimistic. This doesn’t seem to be a mistake. They intentionally move functionality of their clients to their proprietary SDK library. The Bitwarden person stated this in the Github issue and you can also check the commit history. Making that library a build-time dependency might actually have been a mistake. That does not change the fact, that the clients are no longer useful without that proprietary library going forward. Core functionality has been move to that lib. I really don’t care if they talk to that library via some protocol or have it linked at build time. I wouldn’t consider this open source, even if that client wrapper that talks to that library technically is still licensed under GPLv3.
⁨Comment⁩ on ⁨Concerns Raised Over Bitwarden Moving Further Away From Open-Source⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:
Maybe you want to read the comment by kspearrin in that Github issue again. They are clearly moving away from open source. He explicitly states that they are in the process of moving more code to their proprietary “SDK” library.
⁨Comment⁩ on ⁨Concerns Raised Over Bitwarden Moving Further Away From Open-Source⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:
It is really not just a packaging bug. If you read that comment of the Bitwarden person a little further, you’ll notice that he’s talking about that proprietary “SDK” library that they are integrating with their clients. Even if they manage to not actually link it directly with the client, but rather let the client talk to that library via some protocol - it doesn’t make the situation any better. The client won’t work without their proprietary “SDK”, no matter if they remove the build-time dependency or not.
⁨Comment⁩ on ⁨Syncthing Android app discontinued⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:
Perhaps the hard dependency was a mistake, but not them moving more and more code to their proprietary library. It appears that their intent is to make the client mostly a wrapper around their proprietary library, so they can still claim to have an open source GPLv3 piece of software.
⁨Comment⁩ on ⁨Concerns Raised Over Bitwarden Moving Further Away From Open-Source⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:
Thanks, I haven’t seen that one before, but I’d really prefer an open source application.
⁨Comment⁩ on ⁨Concerns Raised Over Bitwarden Moving Further Away From Open-Source⁩ ⁨⁨4⁩ ⁨months⁩ ago⁩:

BitWarden already has lots of clients.

Are there? I’d be very much interested to know. I’ve been looking for other clients before, because I didn’t like the sluggishness of the Electron client, but couldn’t find any usable clients at all. There are some projects on Github, none of which seemed to be in a usable state. Perhaps I have been missing something.

This is being blown a bit out of proportion though. All they are saying is the official SDK may have some non-free components going forward. So what? It’s a private company, they can do what they want. Or the community can just fork it and move forward with a free one if they want, but it’s just not going to be in the official BitWarden clients. Hardly news or a big deal.

Nobody said that they can’t do that (although people rightfully questioned that their changes are indeed comatible with the GPLv3). I very much disagree that this isn’t a big deal, though.
Concerns Raised Over Bitwarden Moving Further Away From Open-Sourcewww.phoronix.com ↗
Submitted ⁨⁨4⁩ ⁨months⁩ ago⁩ to ⁨selfhosted@lemmy.world⁩ | ⁨46⁩ ⁨comments⁩
⁨Comment⁩ on ⁨What are good harddrives to use with serves⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:
I would advice against using SSDs for storage of media and such. Not only because of their higher price, but also because flash memory cells tend to fade over time, causing read speeds to decrease considerably over time. This is particularily the case for mostly read-only workloads. For each read operation the flash memory cell being read loses a bit of its charge. Eventually the margin for the controller to be able to read the data will be so small, that it takes the controller lots of read operations to figure out the correct data. In the worst case this can lead to the SSD controller being unable to read some data alltogether.