If you’re going to do that, at least ask for something useful. Y’know, like “Destroy all advertising firms.”

bash: sudo: command not found

After all, we don’t know that he has it installed, especially if he’s running a really old distro.

I’m aware that he probably meant miles, but he still used the wrong abbreviation (should have been mi). Gotta be careful about that kind of thing, although I’m not sure what the tech anecdote equivalent of the Mars Climate Orbiter would be. Someone taking it too seriously, like I’m doing here, probably. 😅

Except that 80 metres is only a few carlengths . . .

That’s kind of an insult to the parrot, isn’t it?

Between “One too many nulls” and “The tests are larger . . .” in the beginning, then moving up one notch for each day you’ve been wrestling with it.

Eh, I’m sure we can overrun it just by gluing sufficient instances of Factory to the end of the classname.

And Perl.

Pretty sure the US allows individual states to set the ages. In Canada, it’s provinces that set it. Lowest age I’ve ever heard of was 12 (for limited permits to move farm machinery along back roads in Saskatchewan, although that was decades ago and it might not still be a thing). I had a full and unrestricted license at 16, but the rules have changed since then.

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.

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.

I will have to remember not to use that command anymore. 'Scuse me while I clean up the hairball . . .