![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
The chrome instance is commented out…
The chrome instance is commented out…
AGAIN.
This is not “phoning home” as claimed. It is not a SECURITY RISK as claimed. It is a privacy want/complaint/nag at the very VERY least. THIS IS ALSO NOT A PRIVACY FOCUSED PROJECT.
Refer to the original comment, and realize this was being run in a container. So, what…it’s a risk to have libcurl ide tidied on your server? Your IP address is so damn private and important? Literally nobody cares.
Y’all need to get better hobbies, seriously. Probably just need to get off the Internet if this is the stuff causing consternation in your lives.
Friend, please listen to reason.
The “code” you linked to is not functional code of any sort. Not to be nitpicky, it’s just an HTML image tag, so its Markup at best. All you did was stop the loading of an SVG image. The fact that they source it from their own domain tells you everything: they have a script that runs to check the current number of stars, then generates this image that reflects that. SVG is an image format. It’s really standard.
All your other points you’re making because you do not have much experience in the software realm, which I’m not saying to be dismissive or anything at all, I’m simply illustrating that all the points you’re questioning or mentioning are 100% standard.
Also, you might want to freak out about the social badges being sourced in this as well. This isn’t a “privacy first” project or anything. They aren’t doing anytweird, you’re just misunderstanding some things.
Yes, exactly.
Not only is it insanely power hungry and will drive up electric bill, it’s storage and memory limited, and worst of all, 32-bit.
You wouldn’t be able to run much as far as modern software goes on it, and even then, not for long. You probably won’t even find a working distribution because of the age of the hardware, and the fact that large swaths of 32-bit drivers have been removed from the kernel over the years.
Just chalk it up to being E-Waste, and take it to someplace that will properly recycle it.
Okay, well they were very clear about it, and they have a pro version, so aren’t removing the customizations that exist.
Secondly, that isn’t a “phone home” bit that you hacked around, it’s literally a header that loads a GitHub badge, and that’s it. It’s part of a lot of open source projects.
Blocking the DNS of the GitHub host it’s calling back to is sufficient enough for everyone if this is a concern (it’s of no security concern, freal), and you don’t need a fork for this to be fixed. Maintaining a fork is an insane amount of work, and trusting someone who is maintaining a forked repo is WAYYYYYY more risky than just using the official repo, which has thousands of stars, and multitudes of users poking through it’s code.
I for one would never touch your forked repo without doing a full diff, and I’m not going to worry about doing that every time a release is missed by you, or a fix isn’t upstreamed…yada yada. I would just use the official repo, and block the offending GitHub domain if I found it offensive, which I don’t.
Know what I mean?
This only works for specific mechanical failures, and I’d say about 25% of the time. It works because metal shrinks when cold, and this can sort of let a drive limp along for a short period of time to get small amounts of data off.
Drive clicking is the drive arm malfunctioning, and I wouldn’t expect the freezer trick to do much if it’s a messed up actuator or something. You already know the drive is bad though, so why not.
What you’re describing is data TRANSFER. Bad sector detection and management is done by the drive controller firmware.
Firewall, Auth on all services, diligent monitoring, network segmentation (vlans are fine), and don’t leave any open communications ports, and you’ll be fine.
Further steps would be intrusion detecting/banning like crowdsec for whatever apps leave world accessible. Maybe think about running a BSD host and using jails.
Try switching your browser to a mobile view and see if that works. I have a hunch.
Do you have money to replace everything plugged into those outlets, and sufficient home insurance that also ignores such things? Then, no, I guess.
Just take an hour and make a ground yourself. It doesn’t take a lot of specialized knowledge to do so.
Edit to say, I’m pretty sure any surge protector worth itself has a ground output on it already. Just run a wire from it into the literal ground if possible, or over to a place in your home that is properly grounded. You’re just trying to give something like a lightning strike a path of least resistance to discharge into. Any metal conduit in your home SHOULD be grounded, so that’s an easy option.
Conduit should run fine up to many hundreds of users on a single node as far as message passing goes. For the storage part, you’ll only operate as well as your storage solution. I’d honestly expect to invest some money on that part if you want the system as a whole to operate well, because some of the Matrix message handling is synchronous to media if attached to a message.
It’s like 31 Flavors, but less efficient.
The number of drives doesn’t matter when you can’t copy to another. There is no replication path here.
RAID 5 is a minimum of 3 drives…I’m not sure what you mean.
Not at all possible whatsoever though. If he has two drives nearly full, he would never be able to fit all replicable data on a RAID 5 of any kind.
What you’re describing as a solution is the “3 jugs of water” problem. The difference is you need only one coherent set of data in order to even start a RAID array. Juggling between disks in this case would never make the solution OP is asking if all data can’t fit on one single drive, due to the limitations of smallest drive capacity. You can’t just swap things around and eventually come up with a viable array if ALL data can’t be in one place at one time.
He said the two drives are mostly full. It’s not a paritioning issue at that point.
Ahhh, makes sense. That kind of wrecked my brain for a moment.
Ah, he said PC, so I just assumed he wanted the distribution on x86. I see where you’re coming from though.
If all of your data won’t fit on one single drive, you can’t increase your reliability with RAID at this point. You need at least one drive of a size capable of holding all your data to replicate to at least one other drive for RAID 1 at a minimum. Increasing RAID levels from there with replication (not just striping) will only reduce the total amount of space available from the smallest drive capacity in the disk group until you hit a certain number of drives.
Honestly, if you’re wanting to increase reliability for fear of data loss, take a run through your data and see if there’s anything you can ditch (or easily replace later), see how small that data set can be. Revisit RAID combinations after that.
Try disabling the metadata downloaders.