![](/static/f79995a8/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/h1ChnLuBHr.png)
There are dozens, but none with the same reach of people just poking around to find projects. Some people self-host things.
There are dozens, but none with the same reach of people just poking around to find projects. Some people self-host things.
Well use whatever you want, the point is showing you have code out there, which is inherently NOT a very privacy-centric act.
You don’t need to even make your activity public, just someplace people can see relevant stuff you’ve been working on.
Fork some repos, contribute some PRs to some projects you like, and generate some activity if you’d like though. People love to see that.
Do some writeups and post them online, get a public GitHub presence going, and link all those together from some central homepage or LinkedIn or whatever you like. Then try to land some interviews.
They have a container and instructions on how to build and run it. Where are you getting stuck?
Search for the word “changedetection” in your compose file, then find out why it thinks you have a volume named WEB_DRIVER
I’d assume your formatting is off.
I’m not saying this is the fix. This is a debugging step to see what the issue is if it’s not sourcing the local metadata.
Bud, if you don’t know how to read and understand your own logs, I can’t step through this entire thing with you. It’s literally telling you exactly what is wrong.
Plays like an RTS, but not as involved. You control a squad of soldiers moving through an area where different types of alien spawn are taking root to take over. Each level has a timer (under 10m each IIRC), and your job is to sweep through and clear the infestation in that time. You can outfit each soldier in your squad with different weapons and specialties, and split them up to handle different jobs tactically.
Think Syndicate meets Advance Wars.
Try disabling the metadata downloaders.
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.
Don’t they all make that claim?
What’s the controversy?
I don’t get it. Why wouldn’t you just make this a hosted service instead of a mobile app? Better, why wouldn’t you just use Prometheus for this instead of some rando tool?