USPS’ website does this, sort of.

If their text service is down it’ll let you know and just skip the 2FA process even though normally they offer an option to get the code via email.

The fact that they do this is bad enough, the fact that this happens so often that I’ve seen this at least a dozen times is even worse.

You’re right that a lot of Terms of Service documents and similar agreement documents have language that reserves the right to modify those terms.

At the same time just because something is in the terms doesn’t mean it can stand the test of adjudication and terms as well as changes are often challenged in court with success.

Unity is in a particular tricky situation because the clause that governed modifications in their last ToS explicitly gives the user the option to pass on modifications that adversely affects them and stick with the old terms:

Unity may update these Unity Software Additional Terms at any time for any reason and without notice (the “Updated Terms”) and those Updated Terms will apply to the most recent current-year version of the Unity Software, provided that, if the Updated Terms adversely impact your rights, you may elect to continue to use any current-year versions of the Unity Software (e.g., 2018.x and 2018.y and any Long Term Supported (LTS) versions for that current-year release) according to the terms that applied just prior to the Updated Terms (the “Prior Terms”). The Updated Terms will then not apply to your use of those current-year versions unless and until you update to a subsequent year version of the Unity Software (e.g. from 2019.4 to 2020.1). If material modifications are made to these Terms, Unity will endeavor to notify you of the modification. If a modification is required to comply with applicable law, the modification will apply notwithstanding this section. Except as explicitly set forth in this paragraph, your use of any new version or release of the Unity Software will be subject to the Updated Terms applicable to that release or version. You understand that it is your responsibility to maintain complete records establishing your entitlement to Prior Terms.

https://web.archive.org/web/20201111183311/https://github.com/Unity-Technologies/TermsOfService/blob/master/Unity Software Additional Terms.md

Cue the nuclear shills that will handwave away any legitimate concern with wishful thinking and frame the discussion as solely pro/anti fossil, conveniently pretending that renewables don’t exist.

ETA:

Let’s look at some great examples of handwaving and other nonsense to further the nuclear agenda.

Here @danielbln@lemmy.world brings up a legitimate concern about companies not adhering to regulation and regulators being corrupt/bought *cough… Three Mile Island cough*, and how to deal with that:

So uh, turns out the energy companies are not exactly the most moral and rule abiding entities, and they love to pay off politicians and cut corners. How does one prevent that, as in the case of fission it has rather dire consequences?

So of course the answer to that by @Carighan@lemmy.world is a slippery slope argument and equating a hypothetical disaster with thousands if not millions of victims and areas being uninhabitable for years to come, with the death of a family member due to faulty wiring in your home:

Since you can apply that logic to everything, how can you ever build anything? Because all consequences are dire on a myopic scale, that is, if your partner dies because a single electrician cheaped out with the wiring in your building and got someone to sign off, “It’s not as bad as a nuclear disaster” isn’t exactly going to console them much.

At some point, you need to accept that making something illegal and trying to prosecute people has to be enough. For most situations. It’s not perfect. Sure. But nothing ever is. And no solution to energy is ever going to be perfect, either.

Then there’s the matter of misleading statistics and graphs.
Never mind the fact that the amount of victims of nuclear disasters is underreported, under-attributed and research is hampered if not outright blocked to further a nuclear agenda, also never mind that the risks are consistently underreported, lets leave those contentious points behind and look at what’s at hand.

Here @JohnDClay@sh.itjust.works shows a graph from Our World in Data that is often thrown around and claims to show “Death rates by unit of electricity production”:

Seems shocking enough and I’m sure in rough lines, the proportions respective to one another make sense to some degree or another.
The problem however is that the source data is thrown together in such a way that it completely undermines the message the graph is trying to portray.

According to Our World in Data this is the source of the data used in the graph:

Death rates from energy production is measured as the number of deaths by energy source per terawatt-hour (TWh) of electricity production.

Data on death rates from fossil fuels is sourced from Markandya, A., & Wilkinson, P. (2007).

Data on death rates from solar and wind is sourced from Sovacool et al. (2016) based on a database of accidents from these sources.

We estimate deaths rates for nuclear energy based on the latest death toll figures from Chernobyl and Fukushima as described in our article here: https://ourworldindata.org/what-was-the-death-toll-from-chernobyl-and-fukushima

We estimate death rates from hydropower based on an updated list of historical hydropower accidents, dating back to 1965, sourced primarily from the underlying database included in Sovacool et al. (2016). For more information, see our article: https://ourworldindata.org/safest-sources-of-energy

Fossil fuel numbers are based on this paper which starts out by described a pro-nuclear stance, but more importantly, does a lot of educated guesstimating on the air-pollution related death numbers that is straight up copied into the graph.

Sovacool is used for solar and wind, but doesn’t have those estimates and is mainly limited to direct victims.

Nuclear based deaths is based on Our World in Data’s own nuclear propaganda piece that mainly focuses on direct deaths and severely underplays non-direct deaths.

And hydropower bases deaths is based on accidents.

So they mix and match all kinds of different forms of data to make this graph, which is a no-no. Either you stick to only accidents, only direct deaths or do all possible deaths that is possibly caused by an energy source, like they do for fossil fuels.

Not doing so makes the graph seem like some kind of joke.

Most doxxers don’t technically release the information, rather they’ve acquired it and point others to where they’ve acquired it or simply disseminate it further.

That’s what I’m saying. In most cases the doxxer isn’t the one who originally provided the info, but rather someone who has found the information online via a Google search or something similar.

Isn’t that a little bit of circular reasoning?

If I doxx someone online then it gets indexed by Google, if someone then Google’s the information it stops being doxxing?

I’d assume most doxxing isn’t done by someone who has unique firsthand knowledge (e.g. “Oh I know John, he lives on so and so road”) and instead is done by finding the information online whether via Google or a different public source.

At least in the US, where a ridiculous amount of private information is deemed “public”.

There are plenty of instances that are open, but it depends on your definition of “censored” if they are what you seek.

Completely “uncensored” instances are rare if not non-existent because most instances will at least try to adhere to the laws of their jurisdiction and in addition will have some rules in place to keep things running smoothly and pleasant for everyone.

Most big instances are run from the EU so they’ll often have rules regarding hate speech.

Depending on your definition your only options might either be Japanese instances due to less strict laws around certain content or right wing instances, but both will be almost uniformly blocked on other instances.

It means no porn, how much that overlaps with anything remotely considered NSFW is up to the admin and you’d have to ask them.

The individual cashier won’t care, but the manufacturer might, especially if they’re returned as defective because they then make their way back as RMA.

Shops will also stop stocking the item if it stands out because more people return them.
They want to make a profit after all and if they have to discount items as “open box” then they’re losing out on profit, especially since the margins on some of these are already pretty low for retailers.

You don’t know Some Software Corp and their world famous website somesoftwarecorp.com?

But for iOS you’re forced to use Xcode for implementing certain things like permissions, build and upload.

You can do all that via VSCode as well if you so desire.

Permissions, configurations, etc. are essentially all just XML files and can be edited as such, building, running in simulator and uploading can all be done via CLI.

And if you’re not comfortable doing it via the terminal in VSCode, you can also find some extensions.

Personally as a native dev I don’t know why you’d want to of course, but to each their own.

I think you might be misunderstanding what this does.

You did a search for symbol references that contain “User” ignoring cases.

When you do a search for symbol references this way, Xcode will return two things:

1. A declaration of all the symbols containing “User” and/or some context surrounding the symbol (ignoring Case)
2. Show any places where your code references the symbol

And it did just that.

The first three .swift files show references to symbols that contain “User”.
The forth one, User.swift, is in and of itself a symbol that matches the query and has symbols inside itself.
The last one UserViewModel.swift is in itself a symbol as well and all the parts that are nested within that you’ve annotated with underscores and question marks, serve to give you context about the symbol “UserViewModel”, hence the ellipses.

It’s essentially telling you “Hey I’ve found this symbol UserViewModel, it starts with a var named username, has a bunch of stuff following that (i.e. …) then has an extension, then some more stuff (i.e. …) and then ends”.

Without knowing what’s inside UserViewModel.swift I can’t tell if it goofed with giving you a typical declaration, but that doesn’t change the fact that its trying to give you context about a valid search result, the symbol UserViewModel, so that you can figure out if that’s the one you’re looking for.

Keep in mind that variables are considered symbols as well, but in this instance I don’t think that’s what happened here, otherwise it would’ve been marked with a P instead of a C.

If this is not desired behavior then I suggest you switch from “Containing” to “Matching Word” or instead consider using the search bar at the bottom of the Symbol Navigator. Another option, if you’re searching while going through code, is to right click on the symbol in your code and click Find > Find Selected Symbol in Workspace.

Lastly it might be an idea to go over the Xcode documentation as a refresher. This would be a good starting point.

That said, Apple clearly feels that things can be improved by clarifying, because in the current Xcode beta they’ve changed the option label from References to Symbols (and added a few more options).

Most likely different incentives and platform culture.

Customization isn’t that big on iOS, other than the occasional viral fad, so there’s less interest for custom keyboards and in return less development spent on it.

Monetization of custom keyboards is also really hard and due to limitations on tracking and collecting data the incentives that Android has don’t really exists on iOS.

So what you end up with is a handful of custom keyboards often by big players that have bags of money to throw at it or as a companion to a regular app (e.g. Grammarly, GIF apps) to fulfill a specific function.

They’re right about browsers, but jumped the shark on keyboards.

Custom keyboards come with some rules and limitations for obvious reasons, but they’re by no means the system keyboard in disguise like how browsers are all WebKit under the hood.

Here’s documentation on custom keyboards: https://developer.apple.com/library/archive/documentation/General/Conceptual/ExtensibilityPG/CustomKeyboard.html#//apple_ref/doc/uid/TP40014214-CH16

The scandal didn’t lie in following court orders, it lied in the marketing and the fact that the French ToS lacked any nuance to indicate that it would even be a possibility that ip would be logged.

Furthermore, even when dealt with court orders, other companies that don’t tout privacy to be one of their core values, have chosen to fight such orders in court.
Proton could’ve at least tried to show that they were putting their money where their mouth is, by challenging the order.

Between this and the IP logging scandal, it seems that they’re going downhill fast.

Good instinct, here’s a BBC source.

Edit: Apparently this is old news? Or the news is that lawsuits have commenced?

Pro tip: if you do insist on using Google scroll to the bottom until you see a notice like the one below.

You can then click on the complaint to see the URLs that were removed.

They’ve wisened up a bit and now require a (throwaway) email to access the links, but chances are that if you’re looking for something more obscure, the link you seek is still there.