Oh wow, they really closed it down huh?

Not too long ago you were able to change it.

This dumbing things down to prevent customers from fucking themselves over and using up CS resources is getting ridiculous.

Say you need to change some settings but your modem/router isn’t online then you’re SOOL.

Cox, who uses the same gateway, is even worse. They won’t even allow you to enable legacy mode (802.11b) for IoT devices that cheaped out on WiFi cards, not even on a separate network and their customer service can’t enable it either.

I dread moving into a Cox region where there’s no fiber competitor available.

Agreed.

Hold them in contempt of court and let them spend a week in jail all expenses paid.

They’re just trying to run out the clock so that, come election time, they’ll throw their hands up in the air and go “Welp, guess we’ll have to use the old map”.

Having a special master draw up a map is great in theory, until SCOTUS stays the lower ruling and drawn map and decides to not rule on the case until after elections (if they even were inclined to rule in favor of a fair map to begin with).

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.

Only if there’s a risk at incriminating yourself, and if it’s not immediately apparent how you’d run that risk (e.g. you’re a witness that doesn’t have a direct relation to the crime at hand) you’d have to motivate how it could be incriminating.

The US can look at how other countries, that don’t outright provide free education, do it instead of reinventing the wheel.

Getting rid of the discharge protection is only a small part of it.

It’s more important to set a legal maximum for college tuition for accredited institutions.

Then make any subsidies and funds contingent being accredited.

Lastly make federal loans contingent on enrollment to accredited institutions, with the additional benefit of being able to cap the loan amount at a level correlated to the legal maximum tuition (not to be confused with setting at the tuition level because living expenses need to be taken into account as well).

Make the interest rate sub 1%, because the government shouldn’t profit off of you as it is a service and do away with private middle men that administer the loans, instead establishing a special loan administration agency.

This will have as effect that institutions either get in line or lose all government funds and a significant portion of enrollments.

If you then also manage to uphold a uniform quality level that you regularly inspect at the accredited institutions, you’ll end up with a clear, affordable choice of quality education v. unknown quality education that may or may not be a huge waste of non-publicly provided money.

ETA:

You can even take it a step further and follow more examples from abroad in terms of acceptance.
Where you aim to get to a situation that everyone that applies with the pre-requisite prior education credentials, gets accepted.

The way this is often done abroad is with a centralized application process managed by the government, in which you indicate your top 3 preferred colleges, the portal verifies your prior education (as it’s centrally registered) and then enrolls you in order of preference.
For some studies, like law school, med school and psychology they’ll have more applicants than available spots, and in those cases it’s decided by lottery with slightly weighted chances based on your grade average.
The end result is that the vast majority of people automatically get accepted and the ones that don’t get in via the lottery are almost guaranteed to be placed the following year.

This solves the whole minority/legacy/etc. acceptance debacle, makes applying for schools less like applying for a job with writing essays and stuffing your resume with a bunch of extracurriculars and in the process makes the accredited institutions even more attractive compared to the potential hold outs that keep doing things the old fashioned way.

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).

It’s hard to explain without a similar sound existing in English.

The “eu” part in “neuken” and “keuken” is pronounced like the French word for 2: deux.

The ”-ken” end of both words is almost exactly pronounced as the word “cunt” without the t.

“de” is pronounced like “the” but with a “d” sound, like “duh” but not in the exaggerated way you’d do it when you’re mocking someone. And “in” is the same pronunciation as the English one.

So putting that all together, I’d write it out as follows if I’d like to make it pronounceable for an English speaker: “neuxcun in duh keuxcun”

That sounds like a gaping security hole, but with how likely it is that you lock yourself out with the current 2FA implementation, I can’t be mad about it.

If all else fails you could also reach out to the admin of your instance I suppose and see if they can disable 2FA on your account, but I figured it’s best to avoid the headache altogether and just not log out until you’re 100% the 2FA works properly.

That’s also a good way of verifying! As long as you go through the login process somewhere different than your current browser window you should be able to make sure it works properly.

Current 2FA implementation in Lemmy is a bit janky with the risk of being locked out.

First things first: DO NOT UNDER ANY CIRCUMSTANCES LOG OUT UNTIL YOU’RE 100% SURE YOUR AUTHENTICATOR WORKS AND THAT YOU CAN LOGIN USING ITS GENERATED 2FA CODE

Now that that’s out of the way, here are some steps to follow:

1. Ideally clicking on that button will open your authenticator which will then prompt you to select login credentials to attach it to; if it doesn’t and you instead are lead to a URL with a secret key or if you right click and you can copy that URL, then you need to manually copy the URL and paste it in the 2FA section of your authenticator or password manager
2. Once you’ve figured this out don’t log out, instead open a private browser window and test to see if you can login with your credentials + 2FA

If you can’t get it to work then you can disable it in the window you’re still logged into.

If you share which authenticator you use, people might be able to give you more specific instructions to get you through step 1.

Whatever you do, don’t log out. You will be locked out!
Unlike most common implementations, there is no built in step to verify if you can successfully generate a TOTP before 2FA is fully enabled.