I was responsible for multiple RADIUS services used by millions of people every day. The existing software is slow to build with, difficult to scale and expensive. I couldn't let it go.
Step one was building the platform to run it on and make it sustainable as a business. Step two is implementing protocols like RADIUS that lack a separated compute/storage model but should really have one.
I chose C# because I know it, and build native single-file executables using AoT.
Possible forms of inclusive speech: Leser*innen, Leser:in, Leser_innen
This extension removes these possible forms of inclusive speech. Arguably they hurt the reading flow and the German language has the generic masculine. However, proponents of inclusive speech feel that the generic masculine isn't inclusive.
It seems like you would lose meaning by automatically replacing words, no? Why would you want to censor your internet experience, just because you find someone else's use of language awkward?
It's still the same word, just as generic masculine. Gender speech isn't part of the German language but an add-on with no standardization (that's why there are multiple different approaches). Apart from looking awkward one of the main criticisms is that it hurts the reading flow. Following that point the extension improves the reading experience.
To prevent accusations of "masculinism" or sexism and to have a stronger case on having the goal to improve readability the add-on could include an option (or even make it default) to replace by generic feminine instead.
The times where you have to try to appease small but vocal perpetually outraged groups are over. The German language has no generic feminine so adding it to the extension would contradict its goal.
> The times where you have to try to appease small but vocal perpetually outraged groups are over.
Zwei Punkte: erstens, nein, such times are never over. Only thing that changes is who is outraged and by what.
Zweitens, you're a demonstration of this right now by caring. To be clear, I'm not criticising you for this, you're allowed to care about stuff, but you're literally promoting an extension that rewrites someone else's word choice because you don't like it. Es ist dasselbe, und ist gründlich no different to how English Sprachbewahrer complain about the split infinitive in Star Trek's "to boldly go" or common use of the phrase "very unique" (unique means one-of-a-kind, how can you be "very" that?)
> The German language has no generic feminine so adding it to the extension would contradict its goal.
Die deutsche Sprache ist keine constructed language like Esperanto, whose rules come from a book, it's a natural language whose rules are discovered by observing those using it. As people change what they say and how they say it, so too does language change over time.
The German language is what those using it, do. On the basis of the political adverts I see around here, this includes the conservative CDU borrowing die englische Phrase „Made in Germany“: https://www.cdu.de/aktuelles/cdu-deutschlands/mainzer-erklae...
The goal as stated on the extension page is to improve the readability of texts by replacing :, *, _ forms. So some customizability to the user's wishes would be quite nice.
My calculus textbook (Königsberger, 2004) in university used alternating generic masculine and feminine in its exercises, which I found a delightful use of language.
Forgive my ignorance, but it seems that there is more information in the "explicitly inclusive" form than the "implicitly inclusive" one. Doesn't the existence of the inclusive form allow you to explicitly use a non-inclusive form? So in this case
Lehrer being explicitly male
and Lehrer:innen being explicitly inclusive?
I appreciate that this seems to be an emotional topic, but if people choose to use language in a new way, would it not be best to not withhold that information from you as a reader? Someone else wrote that it's like using an ad-blocker, but if I were to read an article, I would want to read it in the exact form someone wrote it, no? It's a bit like Americans auto-replacing "fucking" with "f***g" in their browsers to avoid an annoyance, but they lose information in the process.
When was it introduced and why? It seems in the opposite direction of travel from many languages, which have been trying to make more gender neutral options available.
(exception: Chinese didn't really bother with gendered pronouns until about the nineteenth century, due to the need to translate European languages, so some had to be introduced)
German feminist are looking for a long time to eliminate the generic masculine form. But unlike English, which allows you to use they/them to refer to both genders - and which i kind of like - German doesnt have such an option.
So since my youth, multiple proposal have been put forward, among which the gender-star. Lehrer -> Lehrer*innen, Lehrer:innen.
It was never taken seriously, until we got a left wing government (2022 or so) and since then its getting more and more used. Especially in progressive media. Some even speak it. With a short break that represents the star or :. Sounds pretty stupid, but people do it.
In my mind, its the ultimate form of virtue signalling :-)
but hey. to each their own. I just prefer to ignore it if possible
People use the extension for the same reason people use other content blockers against advertisement, notices banners, social media widgets and so on, namely not to suffer avoidable annoyances.
> you would lose meaning
No meaning is lost that has not been there before.
> someone else's use of language awkward
Most would judge that it's not just awkward, but grating.
Youtube is virtually unwatchable without it. I honestly have no idea how most people cope. Truth is, even with an adblocker there's so much rubbish on the page that gets in my way. Invidous is much better but it's too unreliable.
Sites that autoplay a video, which follows you as you scroll are the worst.
I like the Unhooked extension. You can select which parts of YouTube you want to remove (e. g. Shorts). My start page is empty, I need to visit the channel pages to watch their videos.
AI psychosis: (informal) A phenomenon wherein individuals reportedly develop or experience worsening psychosis, such as paranoia and delusions, in connection with their use of chatbots.
Changed back or not, this demonstrates that they're either willing to make sweeping changes like this that hurt a massive number of users, or that they're incompetent to the point of not realising the impact of the first change. They'd have had to just blindly make the change, since the original PR was approved and merged within the same minute by the original author (no additional eyes, at least that we can see), or ignore user complaints and make it anyway. Both cases demonstrate terrible stewardship of VSCode.
To be fair to OP, that follow-up doesn't appear to be mentioned anywhere in the discussion on #310226, either. They probably should have left a note about that change before locking the thread.
To be honest, I didn't see the follow up. It just incensed me enough that they would do that to begin with.
Right up there with Zed being pretty open that they siphon your code through their API surface and have a "Just Trust Us Bro" data retention policy, along with no way to turn the collaboration features off.
I went and re-read point 3B. I agree that some hypothetical ipv42 faces a translation problem.
But it does not follow that address design is irrelevant. The structure of the address space directly determines whether translation can be stateless and alogrithmic.
In a hypothetical ipv42 design that preserves a deterministic embedding relationship between old and new addresses, translation at the edges could be largely stateless and mechanically reversible, to reduce coordiation overhead between operators and it makes reachability more predictable.
In our world ipv6, the transition seems to require a mix of dual stack, nat64, dns64, tunneling aproaches. The mapping between ipv4 and ipv6 is not uniformly deterministic across all deployment contexts.
Also, there is just a human factor. The mental gymnastics that go on. The perception of what is the way forward? With ipv6, it feels like everyone has to go get their ipv6 stack in order. With a hypothetical ipv42, where the ISPs and backbone providers can throw in the translation layers, it feels like, to me, they would have gotten on board much more quickly. Yeah, I know, it is just a feeling.
I agree with you about the embedded addresses, and I don't understand why the space was moved to all zeros to a bunch of other mappings.
but the utility of this isn't that high. we already know how to handle 4-4 and 6-6 traffic just fine. but if a 4 host wants to talk to a 6 host, it just doesn't have the extra bits in order to describe it, so this just doesn't facilitate 4-6 endpoint communication at all. this is true even you substitute v6 with any other layer 3 with a larger address space.
where it does help is in a unified routing backbone, that would allow v4 prefixes to be announced in the v6 routing system. which is arguably useful.
It's supposed to Just Work on clean and rescue systems. Otherwise, it's a regression with respect to v4. The fact that it doesn't work is evidence that someone has been doing something wrong. The user at the receiving end of this clusterfuck is not that someone.
No, I did not bother because I don’t use IPv6 and I don’t plan to use it anytime soon.
Reporting an issue usually involves some effort, and the support may decide to follow up even if I say that I don’t need a fix. It’s better if someone who cares about IPv6 reports it.
I've got experience with the LIDL cloud aka STACKIT and work for a STACKIT partner. Just drop me a message if you are interested. Two fun solutions implemented (fully automated via Terraform):
Site-to-Site VPN between STACKIT and Azure using a LibreSwan VM and an Azure VPN Gateway
FortiGate HA cluster in STACKIT - not a single ICMP packet got lost during failover
reply