It's not the size, it's a size to content/quality ratio. I'll happily download a 500GB game if it's got the content to match.
Uncompressed assets doesn't bring higher quality visuals or content, it's merely pure laziness or a scam to make people feel like they're getting more for the outrageous price games have gotten.
Free speech includes respecting speech you disagree with and speech that makes you uncomfortable.
If the roles were reversed and you were lined up to be banned because you're not siding with the "correct" side, you'd be crying abusive censorship.
That's what the downvote and block buttons are for.
Yes, a lot safer. Even bugs in the renderer or media player would typically be triggered by JavaScript by say, moving elements around really fast or whatever.
Without JavaScript, the browser renders that page and that's it, there's no JS to modify it or open popups, nothing to dynamically load/refresh content. The most you can do without JS is animations and responding to simple events like changing the color of a button when the mouse is over it. So your only shot to attack this is the renderer during initial page load, once.
You need to set up your PC to be on that IP address first, TFTP doesn't magically listen to a particular IP, you need to configure the PC with that IP.
ip link set eth0 up
ip addr add 10.10.10.3/24 dev eth0
ip addr add 10.10.10.1/24 dev eth0
Then you can start the TFTP server on the interface:
dnsmasq -d --port=0 --enable-tftp --tftp-root=/path/to/tftp/root -i eth0
For all its flaws and mess, NFS is still pretty good and used in production.
I still use NFS to file share to my VMs because it still significantly outperforms virtiofs, and obviously network is a local bridge so latency is non-existent.
The thing with rsync is that it's designed to quickly compute the least amount of data transfer to sync over a remote (possibly high latency) link. So when it comes to backups, it's literally designed to do that easily.
The only cool new alternative I can think of is, use btrfs or ZFS and btrfs/zfs send | ssh backup btrfs/zfs recv which is the most efficient and reliable way to backup, because the filesystem is aware of exactly what changed and can send exactly that set of changes. And obviously all special attributes are carried over, hardlinks, ACLs, SELinux contexts, etc.
The problem with backups over any kind of network share is that if you're gonna use rsync anyway, the latency will be horrible and take forever.
Of course you can also mix multiple things: rsync laptop to server periodically, then mount the server's backup directory locally so you can easily browse and access older stuff.
The absolute worst is self checkouts that have the audacity to ask for a tip. What fucking service?
It really flew over people's head that Trump caved in and that's just us following on our word to remove the retaliatory tarrifs on CUSMCA goods.
There are much better things to complain about the liberals, the whole handling of the AirCanada strike among other things. That's a real failure right there.
It's good we're diversifying trade, but the US is still our only land neighbour.
That's what the off-site backups are for.
People need to stand up for themselves and refuse to go back to work. If the government keep getting away with it, they'll keep doing it.
You can't force people to work.
It helps hackers sure, but it also help the community in general also vet the overall quality of the software and tell the others to not use it. When it's closed source you have no choice but to trust the company behind it.
There's several FOSS apps I've encountered, looked at the code and passed on it because it's horrible. Someone will inevitably write a blog post about how bad the code is warning people to not use the project.
That said, the code being public for everyone to see also inherently puts a bit of pressure to write good code because the community will roast you if it's bad. And FOSS projects are usually either backed by a company or individuals with a passion: the former there's the incentive of having a good image because no company wants to expose themselves cutting corners publicly, and the passion project is well, passion driven so usually also written reasonably well too.
But the key point really is, as a user you have the option to look at it and make your own judgement, and take measures to protect yourself if you must run it.
Most closed source projects are vulnerable because of pressure to deliver fast, and nobody will know until it gets exploited. This leads to really bad code that piles up over time. Try to sneak some bullshit into the Linux kernel and there will be dozens of news article and YouTube videos about Linus' latest rant about the guilty. That doesn't happen in private projects, you get a lgtm because the sprint is ending and sales already sold the feature to a customer next week.
Technically it wasn't really designed with megainstances in mind that swallows the entire fediverse.
My instance has no problem whatsoever keeping up and storage is well under control. But we're few here subscribed to a subset of available communities so my instance isn't 90% filled with content I don't care about and will never look at. Also reduces the moderation burden because it's slow enough I can actually mostly see everything that comes through.
Lemmy itself is also pretty inefficient in that regard, you can very much make software that pulls instead and backfill local cache as needed.
Even my Reddit subscriptions would be pretty easy on my instance.
Wouldn't surprise me if it doesn't check the UTF-8 validity at all and just lets the apps get broken UTF-8 where most of the time nothing horrible happens. That or they just strip invalid characters.