Supermarket AI meal planner app suggests recipe that would create chlorine gas
You are 120% wrong and it IS enshitification.
No. It is enshitification. Do not @ me.
This feels like an obvious bullshit cop-out reason to defederate against a specific community that they don't like for whatever silly reason they can't reveal to the public.
Never have I seen an actual link to content survive very long on lemmy.ml or dbzer0.com. Just like the good old /r/Piracy we discuss piracy, but we do not directly facilitate it.
Someone please slap the back of their heads repeatedly and aggressively with these facts. This excuse is disingenuous as hell.
If you are a user of lemmy.world; RUN. NOW! Find a new instance. Switch away from them before they reach terminal enshitification velocity.
The trouble with Rooting is trust. You are placing trust in a number of apps and software components to not abuse that access.
If you limit apps that are granted root access and make sure only safe apps are granted access; then all should be well. But don't blame anyone if you damage your device.
This is why Rooting your device should ideally only be done after any manufacturer, OEM and carrier warranty has expired. It has benefits; but so too do the guardrails we program into modern operating systems. Rooting your device can be akin to bowling without the bumpers preventing your ball from falling into the gutter.
"Rooting" is literally the act of taking control of the "root" user profile. This is the same as SYSTEM on Windows and even "root" on a Macintosh. As the names imply; the "root" user is the first user. When you are "root"; there are no rules about what you can run. You are essentially as powerful as the operating system itself.
But that omnipotent power does come with a great responsibility. With root access you can literally order the Operating System or even the hardware to kill itself; deleting important files or altering core code is not going to be met with resistance. Sometimes it will even comply with your commands without even checking if they are valid.
Without appropriate understanding of what you are commanding your device to do...Yes, rooting can be dangerous. However; if you do know exactly what you are doing, or are following instructions that are well known to work exactly how you intended them to that were written by someone who does know what they are doing...then Yes, Rooting can be Safe
Too bad. Welcome to lemmy; where downvotes don't always mean anything.
Yeah they're probably banking on people not leaving. Depending on if that agent is good to you and if he/she is local; you should consider just asking them to help you shop around because you need "Change XYZ in your ABC policy" and you need a provider who isn't going to shaft you for making that change.
If they are not a local agent with access to multiple insurance providers...I guess find one locally.
I was talking to my insurance company the other day and they warned me that if I make any changes to my policy they’ll drastically jack up my rate because of the changes in the economy.
This is when you sternly warn the agent/sales rep that this behavior will result in you seeking a new insurance company AND agent for all of your needs
No; it is clear that you are in fact wrong.
These are intended to be pros and cons.
The wording is intentional; and the processes can in fact be hard if you are not well studied in doing these things.
While this is good advice that is sound...You shouldn't have to do this! It should just work! This is the primary reason that users reject Linux.
Most users do not have the time and patience necessary to troubleshoot the issue. Too often, with many distros, many things are "Unsupported" because someone stopped maintaining something.
Many users will not enjoy Linux when all distros available have something they are unreasonably required to sacrifice or do without due to lack of support or code necessary.
Privacy Does Not Equal Anonymity.
Yes; having anonymity does confer some level of privacy, but it is not the only means of having privacy.
Now let's peek at the advantages:
- You own the domain.
- You can host your own mail exchange (MX), configure it the way you want and host it anywhere that will permit you to send and receive emails. Point the DNS record(s) at whatever MX server(s), that allow it, that you want. Personally I use Tutanota for my inbox and SimpleLogin for my junk aliases..
- You have control over where your mail gets routed. By DNS records; you can do a lot of things and point your emails in directions that avoid restrictive networks or unwanted relays as well as securing that route too; ensuring that no one can quietly redirect your mail elsewhere. I use Njalla for my domain.
- You have control over who hosts your inbox. This allows you to swiftly change mailbox or hosting providers without losing your long used email addresses.
- You aren't sharing a domain with many users; which usually means fewer issues with email deliverability due to spam and abuse. Once your domain gains a positive reputation as a small-time email provider; most email services Will accept sent emails even if junk filters do not. Your recipients have an easy way to whitelist your entire domain.
- Your email will receive less spam overall.
Some disadvantages may include:
- Your domain will be aggressively filtered as junk by most Aggressively Configured Junk Filters.
- Your emails may be occasionally rejected by certain email providers with aggressive anti-junk configurations and applications deciding who they will receive from at the MX level.
- Your emails may be easy to snoop on at the network level; as they will have an identifiable domain on the envelope and will be primarily routed to a specific host. This is problematic if you or your mailbox provider don't force remote mail servers to use TLS encryption.
- Your domain may be abused or spoofed for spam if you do not configure your DNS and MX settings correctly. (Use DKIM so remote servers can tell if another server is spoofing your domain)
- You will be 100% responsible for all mail that is sent; or appears to be sent by your domain name. This includes all spam that spoofs your domain name; therefore you must USE DKIM to mitigate it.
- You must properly configure everything. If you misconfigure it; the remote servers will notice that and REJECT all of your emails that are sent out.
- You may need to maintain your own MX (mail server) and host that if you choose to do so. This comes with additional performance and administration burdens. Double them if you allow anyone else to use your domain as an email address; because you are now responsible for their conduct as well.
While I'm usually all for that sort of consequence to happen to someone who is legitimately being gross or creepy; I don't think they should've actually fired her. Legitimately it should've been a stern warning and a request to apologize for the statement at worst.
Do I think it was a good idea to tweet it? Of course not. Was it unprofessional? Probably. I guess it depends on if the tweet or statement was made IRL or on Twitter via an alternate account.
Who needs an NFC chip when you can just place a nail shaped NFC sticker on them and gel paint over them? We don't need implantables; those could get copied anyways and cause the need for unnecessary surgeries to replace them as well.
Buy the tags; apply them to your nails and paint them any color you want; pair them to your phone and use appropriate username + password + 2FA + Fingerprint combos to authenticate to your financial institution.
Lost a nail? No big deal. The tags don't carry financial data; they just provide a URI to the merchant; which can ping your phone/smartwatch and ensure that you are:
- Present at the location.
- Not too far away from pay terminal.
- Have not signaled to your devices you are under duress. (Spoken keyword and/or excessively stressed biosigns)
- Have not blocked spending by tap.
Please keep the bots to a minimum.
Approved bots that the admins manually review the use cases for is absolutely fine.
I just don't want things to revert back to reddit days where I'm constantly BLOCKING new novelty bots that are absolutely freaking useless and add nothing to a conversation.
Also; PLEASE; implement the following ideas into a(n) agreement/covenant for bot operators; I quote this directly from the Tao of IRC:
The master Nap then said: "Any automata should not speak unless spoken to. Any automata shall only whisper when spoken to."
There's no denying that WEI is evil. It may in fact be the feature that kills the Chrome Browser and gets Google fined into poverty.
But from a user standpoint; I get it. It Just Works. That polish built into Chrome that allows users to sync their browsing sessions across machines? It's absolutely critical and required.
The FOSS community has this weird habit of requiring it's users to make sacrifices to meet it's values. Where that doesn't harm the user, their workflows or their convenience in general; users are typically more than happy to do so.
However; A lot of FOSS and FLOSS projects tend to take ridiculous stances against certain kinds of polish features and will REFUSE to implement them no matter how many people ask. In my opinion; if you want a software project to succeed and overtake massive competition; that's just stupid. Especially when it's as easy as forking a repository and baking the "Controversial feature" into the user-friendly fork version.
If you want to provide a core piece of software and all; sure! Please do that! But a lot of projects don't, and won't spend any time on user experience at all; and any kind of work on the UX arises because something is inconvenient for the devs.
Worse is that oftentimes; the polish features that are being blanket denied and intentionally omitted from the software are in fact not that complicated to implement in a manner that runs consistent with the values of the FLOSS community. Sure; that means that perhaps you do have to host a lot of things yourself to make sure that you truly retain control over your data; but that's actually pretty easy to learn how to do.
I do understand the limitations of the average FLOSS project. Unfortunately; a lot of FLOSS and FOSS devs are very quick to decide that they know the best, and will frequently and often refuse to listen to the user. That's not better. It's worse. At least when a user is a customer, they have some degree of influence and can exert some small force on development priorities. In the FLOSS community; you can donate every cent you have to a project and it does not necessarily guarantee that you will get a say, or even one request, fulfilled. For some users; that is not better, it is worse.
We still have a long way to go before we reach a society with the maximum amount of balance between beneficial qualities, and none of the negative qualities, of socialism and capitalism.
God yes this is so freaking annoying.
As much as I adore FOSS and hold it near to my heart; Most FOSS software just doesn't have a lot of polish. That isn't a fault; but some of the zealots take it that way; and that last 5% of polish is sometimes required, and is absolutely critical to some users' workflows.
You appear to have a solid idea as well as some potential proof of concept code which does not appear to have been uploaded to GitHub yet but you don't appear to have posted anything usable yet for the end user.
Are you seeking developers to get passionate about this or are you just trying to draw in future user eyeballs?
Honestly; it isn't clear, and there are already mature technologies that exist that is similar to what you seem to be proposing (see i2p, tor, freenet) which are only suffering from a lack of adoption due to their development being backend first and not being able to focus a lot on usability or glitzy UI.
You look like you could have some good skills with graphical things; have you considered contributing your skills to an existing project?
Just another bit of proof that humans are not ready for AI. This AI needs to be deleted. This is not simply operator error; this is an administrative error, and an error of good common sense on the part of many many people involved with creating this tool.
You cannot always trust that an end user will not be silly, malicious, or otherwise plainly predictable in how they use software.