white-flame
Joined 11 years ago
Joined 11 years ago
Now, whether the browsers or mobile OSes actually are secure because of that, is a separate thing, but those are good steps to take.
We still need to figure out which files compose EURISKO.
But a big thing is that back then, games were often made on a timescale of months, and with a budget. Hobbyist dev has no limits to how much time they want to sink into doing something properly. Ideas & techniques have had many years/decades to percolate into existence.
However, I haven't done any serious roaming with such a configuration; has anybody tried it?
Most people don't outright block offtopic material, they just gloss over it, and it still ends up with influence because that's what Facebook optimizes for. Plus people will still take the occasional click of curiosity to see what some posts are all about, even if they're not really into that content.
Yes, if you do have the discipline to take a zero-tolerance personal policy and immediately block even inoffensive things that just touch into the realm of polarizing, you can probably keep your feeds clean. But most people (eg, non-HN types) don't understand what Facebook is doing and don't think to actively defend against it, and just absent-mindedly consume the feed with no click discipline.
This is not a common carrier, but an active distorter.
The two big problems poisoning this well are:
1) monetization usually reaches for manipulating people's personal socialization stream, and
2) public broadcast of personal content to the feeds of strangers, usually the most inflammatory subset because of point 1.
The thing is, Facebook actively pushes the trash at you, because trash content monetizes the best.
The only effective avoidance mechanism is to not use it (unless there's some facebook-specific browser plugin that strips it all out).
"What if we just stopped distributing and blindly executing untrusted binary blobs?"
A trusted compiler in the OS, and some set of intermediate representations for code distribution would solve a massive amount of security issues, increase compatibility, and allow for future performance increases and disallowing suspect code patterns (spectre, rowhammer, etc). Specializing programs at install time for the local hardware makes way more sense than being locked into hardware machine code compatibility.