What do the apps have that the browser doesn't?
@lemmy.ml
De-googled Android ROMs:
Linux OSes that (allegedly) work on Android hardware (please suggest additions):
Non-android, non-apple smartphones:
And pretty much every feature phone out there (way too many to list)
>inkjet
LED printers have been around for fucking ever, and the average person doesn't need the graphic fidelity that only an overpriced pigment soup, which goes bad in a month, can supply.
Oh, and literally every part of a toner-based printer is easier to replace/repair... so why would a printer designed around repairability and upgradability use ink???
Edit' And I almost forgot: toner is cheaper per page than ink! Whyyy???????
First and foremost: about 10-20 Exabytes worth of storage space, or roughly 4 Petabytes per day.
That's 4,000,000 Gigabytes of new video per day.
And of course you'd need an efficient way of loading all that video data and streaming it to the end users, so they don't experience major interruptions, even when hundreds of thousands of people are all watching the same video at the same time. Youtube does this with caching servers/proxies, and highly optimized data delivery algorithms.
Once you have all that infrastructure, just make sure it's free and ad-free for all the watchers and uploaders. It's not like you need to pay for all those servers and storage... right?
Nobody wants to point out that Alexey Grigorev changes to being named Gregory after 2 paragraphs?
Slop journalism at its sloppiest. I wouldn't be surprised to find out that this story was entorely fabricated.
I had very few issues with a GTX 970 and i7-4790k. The only issues I hear about with either any more is the linux kernel not supporting some of the features of newer GPUs (e.g. I know ray-tracing was a pain-point at one point).
I don't like recommending distros based on such a general use case, mainly because every distro can be tweaked and configured to exactly what you want. Instead, you should research the different mainline distros that have been around for decades—Arch, Debian, Fedora, Gentoo, Guix, NixOS, OpenSuse, Slackware—and see what they're about, what sets them apart from others, what the maintainers' philosophies are, and what kind of package management system they work with. Once one sounds better than the others, look into it and try it out.
#Dos and Don'ts:
Don't try a niche distro. They are harder to troubleshoot and less likely to be actively maintained.
Don't use Ubuntu. It's just a suckier version of Debian. It used to be user-friendly Debian, but now Debian is more user-friendly than it.
Don't dual-boot with windows. This just solidifies your reliance on windows, especially if you're the type to give up on problem-solving issues that you didn't have in Windows. It also can cause issues with making Linux unbootable.
Do try a live usb with persistence before you commit entirely. It's not exactly the same as a complete install, but it's close enough to let you know how the OS feels and what hardware will or won't work with it. Some people say try a VM first, but that won't have direct hardware access.
Do problem solve the little things. Anything that irks you or bothers you or just slows down your workflow. It doesn't have to be an actual bug or glitch, just anything that could be better. This not only solidifies the feeling of ownership over your OS—you no longer have to settle for anyone else's lousy design choices—it teaches you the resources for troubleshooting larger issues.
Do plan around things not being plug and play at first. Want to test if a game runs on Linux? Great, set aside a couple of hours beforehand: first to install steam and set it up, then to figure out Proton, then to troubleshoot the game not even booting up, then to fix any glitches or whatnot, then to get your controller working. This won't always be the case, but it will irk you a lot less when it is if you expect it. The more you make time for solving these issues now, the less time they'll take up in the future (either they'll be gone, or you'll immediately know how to fix them, or your troubleshooting will be more streamlined).
Do set aside time to learn about Linux "under the hood." You don't have to become a computer scientist, but it will save you a lot of headaches, show you cool things you can do, and make your computer a smoother experience. It especially helps if you take the time to learn as they come up: e.g. installer asks you what "bootloader" you want, but you're not sure what that is, what it does, or why it's necessary? Now's the best time to take a little learning detour.
Do ask questions on forums.
Don't listen to the people who shame you for asking.
Do listen to the people who try to show you a better way of doing things, even if it's not your way.
A few answers say "they aren't private by design," but don't really go into the "why." There's the obvious "it's an electronic tracking device, duh" reason, but there's also a more nuanced reason:
Airtags are able to be picked up almost anywhere because they connect to the nearest bluetooth-enabled Apple device, and then send location info across the internet to you. Without this functionality (the ability of any and every Apple device to locate it), they wouldn't have any way to send their location back to the owner.
Your best "privacy respecting" alternatives are something that uses meshtastic (and hoping there's enough repeaters near you), something that uses cellular data and GPS (which is about as privacy-respecting as Airtags are), or just a key finder/beeper (which only works within a small radius)
At least some level of human review is going to be needed.
So... completely negating the point of a User Repository??? Introduce some kind of authoritative oversight, and it's essentially just another regular repository, erasing all the benefits of the AUR. The whole point of the distro slapping a huge disclaimer of "DISCLAIMER: AUR packages are user produced content. Any use of the provided files is at your own risk." at the top of the homepage is because these kind of compromises are the trade-off one makes
The worse the product is, the more desperate they get to shove it in your face. Good products don't need to pay others to pretend it's good, you just find out via word-of-mouth or free trials
Proxies and VPNs seem like the most obvious targets. They mostly prey on people who don't understand the technical workings thereof (had my mom ask if she needed to get a VPN bc firefox opened on ad for theirs, claiming it enhanced privacy), and serve little benefit to people who are doing the kind of illegal activities that make governments take notice. They serve as a single point of compromise for anyone, and they work worldwide so that all your traffic can be monitored even when you're on a different ISP/in a different country. It's like the perfect MITM, and people are even willing to pay to have themselves monitored.
The truth is that at best they benefit people who only don't want their network-provider watching, but don't care who else may be. It's the perfect setup for a 3-letter agency to just sit and monitor everything anyone does, waiting for someone who's just a little too careless to access illegal content thinking they're anonymous.
I wouldn't go quite that far. It doesn't only protect their business interest; it definitely does achieve the goals they claim—like helping non-tech-literate users to avoid getting scammed with malware—it's just they're only doing it this way because it also aligns with their business interest.
To that end I'd contest the "Security Theater" label. All security measures are ultimately implemented in a way that defends the interests of the owners. It's just that people have forgotten or aren't aware that Proprietary Software means they're not the owners.
Of course if it was just about users' safety, the most effective way to help people avoid getting scammed is to educate them, but that would make people less dependent on Google and less susceptible to vendor lock-in, and people may even start having dangerous thoughts like "it sure is weird how many identifying traits of a scam are also just standard business practices for large corporations like Google."
There's "defeminize" or the more recent "defeminate."
If we take the other meanings of "emasculate":
In the sense of literal castration, there's "oöphorectomy"; in the sense of complete neutering (removal of penis and testicles) there's "spay."
In the sense of weakening or sapping energy... well, the meaning isn't gendered, but the morphology does follow the "male-as-norm" principle. I couldn't find a feminine gendered variation (at least, not in English), but this also doesn't appear to be the meaning that OP is referring to.
Time and again, across years and product categories, Amazon has reached out to its vendors and instructed them to increase retail prices on competitors’ websites, threatening dire consequences if vendors do not comply.
Yes, buying from alternative websites is the bare minimum and the bar is so low it's underground. But that's beside the point: Amazon is price fixing across the internet.
Just looked at Session, and holy shit is that a massive downside...
From their own whitepaper:
Through the integration of a blockchain network, Session adds a financial requirement for anyone wishing to host a server on the network, and thus participate in Session’s message storage and routing architecture.
So you have to pay to self-host, and that's somehow an upside???
This staking system provides a defence against Sybil attacks by limiting attackers based on the amount of financial resources they have available.
Which is a fine explanation in a world where everyone has a relatively equal amount of wealth. This is the epitome of dunning-kruger economics: a little knowledge is a dangerous thing.
Firstly, the need for attackers to buy or control Session Tokens to run Session Nodes creates a market feedback loop which increases the cost of acquiring sufficient tokens to run large portions of the network. That is, as the attacker buys or acquires more tokens and stakes them, removing them from the circulating supply, the supply of the Session Token is decreased while the demand from the attacker must be sustained. This causes the price of any remaining Session Tokens to increase, creating an increasing price feedback loop which correlates with the scale of the attack
So the more nodes a single entity holds, the harder it becomes for other entities to buy nodes and break the monopoly? Did you take 3 seconds to think this through???
Secondly, the staking system binds an attacker to their stake, meaning if they are found to be performing active attacks, the underlying value of their stake is likely to decline as users lose trust in the protocol, or could be slashed by the network, increasing the sunk cost for the attacker.
"Assuming every user is a perfectly rational actor, malicious actors would be shunned. This is somehow due to the economic incentive, and not just how humans operate when they're assumed to be perfectly rational."
Also: malicious actors when they find out they might lose their money if they get caught: "welp, I better not do that then. Thanks laissez-faire capitalism!"
Jesus christ fucked on a pike, these dipshits really drank the crypto kool-aid, huh?
Because privacy is a spectrum, and it makes a good stepping off point for the people that still use text messages and social media chat clients to stay in touch. I can't convince half of my nerd friends to leave Discord for literally anything less shit, but I can convince even my tech-averse mother to use Signal instead of FaceTime.
thanks for using Leebra!
go to feed...