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.
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.
Imagine that: some scammy motivational speakers who have been peddling a bunch of feel-good bullshit for decades didn’t know how to fix a company that was hemorrhaging money with warm thoughts and regards.
I would have taken that bet.
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?
It’s still very subjective to who is making the main CPU, but yeah. It’s meant for low power applications.
No idea who this is, but I can already tell my the fake getup that I do not care to look up whatever persona this guy thought was entertaining. Streamers are terrible.
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.
RISC is only for tinkering at this point.
It’s really just for tinkering at this point, or cheap build systems I guess. There’s some small edge cases where the existing instruction set will beat ARM or x86, but they’re very niche. Eventually it’s expected to be a contender to the more optimized stuff we see in ARM chips these days.
What you’re describing is data TRANSFER. Bad sector detection and management is done by the drive controller firmware.
This reads like an April Fools joke.
This pretty much opens the door for Proton on mobile I guess?
Why? Nobody even knows why he was famous anymore.
If I was a child, and toy stores looked like that, I’d be there in a heartbeat. This is making insane expectations for children that will never come to pass. Fuck this PR firm, fuck this company, and anyone else who has anything to do with this.
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.
The chrome instance is commented out…