Then, in my opinion, you would have failed to perform due diligence. Even if you’d thought C.O. was an adult, suggesting a woman strike up a private conversation with a man neither of you know is always something that deserves a second look (dating sites excepted), because the potential for harm is regrettably high.
Snapchat is not the only problem here, but it is a problem.
If they can’t guarantee their recommendations are clean, they shouldn’t be offering recommendations. Even to adults. Let people find other accounts to connect to for themselves, or by consulting some third party’s curated list.
If not offering recommendations destroys Snapchat’s business model, so be it. The world will continue on without them.
It really is that simple.
Using buggy code (because all nontrivial code is buggy) to offer recommendations only happens because these companies are cheap and lazy. They need to be forced to take responsibility where it’s appropriate. This does not mean that they should be liable for the identity of posters on their network or the content of individual posts—I agree that expecting them to control that is unrealistic—but all curation algorithms are created by them and are completely under their control. They can provide simple sorts based on data visible to all users, or leave things to spread externally by word of mouth. Anything beyond that should require human verification, because black box algorithms demonstrably do not make good choices.
It’s the same thing as the recent Air Canada chatbot case: the company is responsible for errors made by its software, to about the same extent as it is responsible for errors made by its employees. If a human working for Snapchat had directed “C.O.” to the paedophile’s account, would you consider Snapchat to be liable (for hiring the kind of person who would do that, if nothing else)?
Actually, Gentoo has no restrictions against packaging closed-source software, or even for-pay software. The net-im category is full of closed source.
Closed-source games rarely get packaged, and almost never in the main tree, in part because they all have to be fetch-restricted. The system can’t predict whether you bought from Steam or GOG or some smaller store, or whether you have a means of downloading from that store without user interaction, so it has to send you to download the package yourself and place it in the source directory. That’s considered a black mark against the package. (There was someone a few years ago who was packaging GOG games in an overlay, but they don’t seem to be doing it anymore.) In general, no distro will package this stuff—you’re better off installing Steam and having it manage your games.
As for build times, get used to letting updates involving large packages run unattended overnight. Sort out the dependencies, issue an emerge with --keep-going, and go to bed. Works for PI3s and my Athlon64x2 laptop, anyway. (If this is still intolerable for you, maybe Arch would be a better fit?)
Finally, you may not be aware that the most complete list of Gentoo-packaged software available is not on the official site, but at gpo.zugaina.org, which also indexes ebuilds in overlays and Bugzilla.
Yes, they should. They chose to deploy the algorithm rather than using a different algorithm, or a human-curated suggestion set, or nothing at all. It’s like a store offering one-per-purchase free bonus items while knowing a few of them are soaked in a contact poison that will make anyone who touches them sick. If your business uses a black box to serve clients, you are liable for the output of that black box, and if you can’t find a black box that doesn’t produce noxious output, then either don’t use one or put a human in the loop. Yes, that human will cost you money. That’s why my suggestion at the end was to use a single common feed, to reduce the labour. If they can’t get enough engagement from a single common feed to support the business, maybe the business should be allowed to die.
The only leg Snapchat has to stand on here is the fact that “C.O.” was violating their TOS by opening an account when she was under the age of 13, and may well have claimed she was over 18 when she was setting up the account.
Bunch of things going on here.
On the one hand, Snapchat shouldn’t be liable for users’ actions.
On the other hand, Snapchat absolutely should be liable for its recommendation algorithms’ actions.
On the third hand, the kid presumably lied to Snapchat in order to get an account in the first place.
On the fourth hand, the kid’s parents fail at basic parenting in ways that have nothing to do with Snapchat: “If you get messages on-line that make you uncomfortable or are obviously wrong, show them to a trusted adult—it doesn’t have to be us.” “If you must meet someone you know on-line in person, do it in the most public place you can think of—mall food courts during lunch hour are good. You want to make sure that if you scream, lots of people will hear it.” “Don’t ever get into a car alone with someone you don’t know very well.”
Solution: make suggestion algorithms opt-in only (if they’re useful, people will opt in). Don’t allow known underage individuals to opt in—restrict them to a human-curated “general feed” that’s the same for everyone not opted in if you feel the need to fill in the space in the interface. Get C.O. better parents.
None of that will happen, of course.
Installing Gentoo requires you to 1. follow a long list of instructions (correctly, in order, without skipping) and 2. be willing to make some decisions about your system setup. I don’t consider that painful, but some people apparently do. It’s also useful to bring a book or some other secondary form of entertainment to occupy yourself with during the non-interactive parts of the install process. Once the initial install is done, you can minimize wasted time by starting updates right before leaving the computer, or just configure it to always leave one core free for your interactive needs.
Gentoo has never been an appropriate distribution for new Linux users with no technical background, or people who want their system to “just work” without caring about how. It’s always been about choice, and its flexibility is both a strength and a weakness. Regardless, the OP did the correct thing by not including it in their guide.
Actually, what really matters is not the quality of your code or the disruptiveness of your paradigm, or whether you can outlive the competitors that existed when you started up, but whether you can keep the money coming. The rideshares in particular will fail over time in any country with labour laws that allow drivers to unionize—if the drivers make a sane amount of money, the company’s profits plummet, and investors and shareholders head for the hills. Netflix is falling apart already because the corporations with large libraries of content aren’t so happy to license them anymore, and they’re scrambling to make up the revenue they’ve lost. Google will probably survive only because its real product is the scourge of humanity known as advertising.
Again, it’s all business considerations, not technical ones. Remember the dot-com boom of the 1990s, or are you not old enough? A lot of what’s going on right now looks like the 2.0 (3.0? 4.0?) release of the same thing. A few of these companies will survive, but more of them will fold, and in some cases their business models will go with them.
You’d lose that wager, actually—this area has at least two taxi companies but no ride shares (Uber and Lyft have very little penetration in Canada outside a few specific cities), and our household does subscribe to a standard cable TV package, although it’s mostly for the benefit of my elderly mother. Those companies have not been nearly as disruptive as some people think they have.
(As for Google’s search engine, I wouldn’t touch it with a barge pole these days. And Yahoo and AltaVista both sucked even when they were popular—I preferred InfoSeek, back in the day.)
Which have all descended, or are in the process of descending, into suckitude because of business issues rather than technical ones. And trying to replace programmers with LLMs is fundamentally a business issue.
Another good reason to stay away from the US in general and Georgia in particular.
Rolling release distros don’t do this. Gentoo isn’t versioned. I’d guess that Arch isn’t either. Not that you’re the first person to look at an issue that exists only with some distros and assume it extends to all of Linux (and I doubt you’ll be the last).
There are two different RDP implementations in Linux: freerdp (which is the underlying library for remmina as well) and rdesktop. Each has its own set of bugs. No idea if rdesktop offers better support for what you want to do—I use it, but I only have single-monitor setups at both ends. (It has an annoying bug that can make it require multiple attempts to establish a connection, though.)
Tried to register with gitlab three times some months back to file a bug against qemu. It rejected my registration silently every time (as in, it appeared to take it but never sent a confirmation email, not even one that got mistaken for spam). I gave up on filing the bug.
Or sed the existing config file at the end of your script.
And the issue that does exist doesn’t even require Linux to be installed, technically. Unless you’re an IT pro administering large numbers of systems that boot from a network disk image, there is nothing for you to worry about here.
Gentoo does have systemd, actually—package sys-apps/systemd—and there are optional sections in the install documents that explain how to go about using it as your primary init. It’s an officially supported configuration, just not the default.
(But yeah, as for the main problem, sounds like hardware—RAM, your primary hard disk, or the disk controller on the mobo. Start with The Bleeding Obvious and make sure all cables are solid in their sockets and all the RAM is properly inserted.)
Advertising copy is likely overrepresented in the general corpus of texts from the Internet that most LLMs are trained on. Plus, it isn’t a genre where truth matters all that much. It’s intentionally vague and cliché-riddled even when humans are writing it. So it’s something that I’d expect LLMs to be pretty good at creating.
“Garbage in, garbage out” is just fine if garbage was your desired output to begin with.
For gaming, you should be using the most current version of nvidia’s proprietary drivers that supports your GPU, unless that GPU is really old. Have a look at this page: https://www.nvidia.com/en-us/drivers/unix/legacy-gpu/
If your GPU isn’t listed there, use the most recent driver you can find.
If your GPU is on the 470.xx supported list, try 470.223.02, as that seems to be the last in the series.
If your GPU is on the 390.xx supported list, try 390.157.
If your GPU is on one of the other lists, it’s a really old chipset and you should be using the Nouveau driver that’s built into the kernel.
If you’re using the nvidia proprietary drivers on a system that also has Nouveau installed, make sure you’ve blacklisted Nouveau so that you’re loading the correct driver.
Dual-graphics laptops are a bit of a bear to work with under Linux generally. Good luck.
To set the record straight, since you apparently have no idea of the history: systemd isn’t the original Linux init system, and wasn’t foisted on the Linux community because it was technically superior for most people’s use cases. It still isn’t the only viable Linux init system, but it pulled a Microsoftian embrace-extend-extinguish on udev, which makes it more difficult to switch away. Its current popularity is still not based on technical merits. Instead, it’s political, because most people don’t care about what init they’re using and most distro-makers take the path of least resistance.
It’s true that you’re not required to use all of the individual executables that comprise systemd, but most distros will require you to install them. So they’re still present as unwanted clutter, and bugs could still pose a security risk if an attacker can run the executables. (This doesn’t mean that OpenRC or runit would necessarily be any more secure—every non-trivial piece of software has bugs, and some percentage of those are going to be security-relevant. You’re not required to care about small amounts of on-disk clutter, either, but some people choose to make their system partitions small and micromanage the contents even if they’re not working on embedded.)
Compiling your own copy of systemd without the clutter, judging from the contents of the systemd ebuild, requires setting more than 30 compiler options. And then installing the result manually without trashing your system. Not trivial, in other words.
If systemd works for you, then by all means use it, but accept that other people may choose to install something different on their own machines for what you consider to be bad reasons, or no reason at all, and arguing about it just annoys them without providing any benefit to you.
I ended up with a 103-key Unicomp New Model M (essentially the same layout as a 101-key, but with one Windows key and one context menu key stuffed into what would have been the small blank spaces in the bottom row between ctrl and alt—I really wanted a full-length spacebar). Linux is most often installed onto ex-Windows PCs, so it’s hardly surprising that it expects the Windows keyboard layout.
(I believe the current generation of Gnome devs is big on minimalism, AKA omitting or removing features. I can understand the appeal from a code maintenance point of view, but it’s never been a DE that I liked.)
You can buy keyboards with replaceable keycaps. You can also buy keycaps with Tux logos on them for at least some of those keyboards. You can decide for yourself whether your aesthetic dislike of the Windows logo is worth the rather higher price of such a keyboard.