Can you be more specific?
Are you asking if it will detect and allow you to use more than one drive? I’ve never used it, but why wouldn’t it?
Can you be more specific?
Are you asking if it will detect and allow you to use more than one drive? I’ve never used it, but why wouldn’t it?
Trippy. Saved.
Its not worth the energy cost, honestly. Plus you’ll be quite limited on memory, which reduces the potential uses. Any $200 minipc from the last 5 years would be a better buy.
Yeah, so like every single other monitor platform out there that is open source and widely used.
I’m asking WHY this specific thing does something better or different?
The instructions literally say you are doing exactly that.
Dafuq are you talking about?
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?
They have a container and instructions on how to build and run it. Where are you getting stuck?
I would assume so? All their other stuff is Zigbee, and it’s got a huge following.
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.
Try disabling the metadata downloaders.
The chrome instance is commented out…
Yep. That was a property from the Master System and Game Gear that got a 3D revamp for DC, but don’t think it was really very popular to begin with, so naturally wasn’t a huge selling point.
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.
That’s the best time to market. They simply didn’t have the big IP that Nintendo and Sony had been marketing at the time. Sega at that time led with Sonic - as they always do - and then a few properties that were really fun and original, but required an expensive console to even try and get aquatinted with.
This is not even bringing up the prior hardware failures they had launched. They just miscalculated on the popularity of Sonic globally. It’s not enough to get people with consoles that are working just fine and still have years of games to come to switch.
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?
Okay, that’s more direct. I would assume all packages have static paths that aren’t able to be changed through the GUI. I would read their docs and find out about that specific angle to try and sort it out. Also, symlinks are a thing, but you may create race conditions that particular OS may not expect if your mount timing is not absolutely bulletproof and perfect every single boot.