> Internet Archive Switzerland joins a growing group of mission-aligned organizations, alongside Internet Archive, Internet Archive Canada, and Internet Archive Europe. Together, these independent libraries strengthen a shared vision: building a distributed, resilient digital library for the world.
I was interested in the others, but https://www.internetarchive.eu is a horrible corporate-looking site with a hero image, a boast about AI, a carousel of news that won't scroll with doing its slow scroll animation, a huge "meet the team" section with mugshots and boring profiles, social media links, a newsletter signup form, and nothing to say where the actual archive is.
Reading what little information they have there, they aren't a public facing or public serving organization. They seem to provide their services to institutions only:
"working with dozens of European libraries and government agencies to build web collections, Internet Archive Europe prioritized collaboration with cultural heritage organizations to safeguard our collective history."
They do exist and involved in archiving. Someone reached out to our amateur radio club and offered to archive any documents we might have. They even asked to archive the video recording of one of our monthly meetings.
20/50 states don't allow mobile gambling, so Texas is only one of those 40%. Some of those 20 states (9 to be exact) do allow sports betting, but only physically, not online.
That said, this means very little when a different type of gambling ("prediction markets") is somehow allowed everywhere because of the corruption of the current administration, with the son of the president being a "senior advisor" to both Kalshi and Polymarket, completely circumventing state-wide bans.
It's better because it actually lists a sample of Bugzilla reports that were made public. This topic was discussed previously (36 comments two weeks ago: https://news.ycombinator.com/item?id=47885042), but the part about bug reports being made public is brand new.
Chrome likes to make up new "standards" and then some websites adopt them immediately.
That said, I can only remember two instances of that slightly inconveniencing me in the past, and both times I was inconvenienced by a Google-run website: once upon a time Google Earth refused to work, and once upon a time I couldn't tweak my Google Meet background. Both are no longer the case.
Citation needed. I've seen the opposite--unless there's a very specific niche that can't be otherwise solved, there's huge internal resistance to going it alone.
The biggest counterexample I can think of: WebUSB was critical to Chromebooks supporting external devices, but I can see why Safari might not want it. It has Firefox support at last, though.
Citation of what exactly? That not all browsers implement the same thing at the same time and that some features are Chrome-exclusive because for one reason or another other browsers refuse to implement it?
Is that really something you need a citation on? You sure seem to have come up with an example of your own.
It's even more fascinatingly dumb to have this discussion like 2 or so years after every major platform decided to kill any notion of 3rd party clients they used to support.
Yes, in an ideal world, that'd be great for both humans and LLMs, but we are about as far from that ideal world as we could be. You can't even do some of the "advanced actions" as a human with human-level reflexes without encountering a captcha, but sure, all of a sudden, everyone will just decide to make their bread and butter that is data easier to explore via an LLM.
It's not "aggressively maintaining the female option", it's just a language quirk. English has a gender-neutral "the" article which you put in front of every noun, German has three different variations of "the" depending on the gender (der/die/das). Literally every noun has a gender, including inanimate objects such as a piece of furniture. "The table" is always masculine ("der Tisch"), "the lamp" is always feminine ("die Lampe") and "the bed" is always neutral ("das Bett"). Sometimes changing the article completely changes the meaning of the word, for example "der See" is the lake, but "die See" can be the sea or the ocean.
Only living things can have more than one gender and in that case, not only does the article change, but so does the suffix. There is no "singress" in English, only "singer", but in German there's "der Sänger" or "die Sängerin". Calling a female singer "der Sänger" would be grammatically-speaking completely incorrect.
The only thing that changed fairly recently is that more and more people intentionally try to maintain gender ambiguity when they don't intent to specify a gender, in which case "the singer" becomes "die Sänger:in", or even "der:die Sänger:in" if you want to be even more pedantic.
Thanks; maybe I didn't explain my point well enough, but I know/understand everything you just wrote.
> The only thing that changed fairly recently is that more and more people intentionally try to maintain gender ambiguity when they don't intent to specify a gender, in which case "the singer" becomes "die Sänger:in", or even "der:die Sänger:in" if you want to be even more pedantic.
Here is my point: in English, the move to gender neutrality of certain words (e.g. actor/actress) seems to have involved adopting the male version, and using it as neutral. (I don't know if some people are offended by this, but if they are, I've not come across it).
In contrast, in German, I impute that some people would be offended by using the male version of a word as a default neutral for all including women, so are deliberately maintaining the female version within the slightly awkward "Sänger:in" construct.
This is a strong, deliberate choice, in contrast to (what I see as) the more passive "eh, let's just use 'actor'" in English.
It used to support it out-of-the-box as well, but it's technically against YouTube's ToS to allow this without paying for a premium, so now you need this as an extra hoop.
Agreed, this sounds strange indeed. Much more likely is that Google found a reliable way to detect the screen status using a standard feature and Mozilla just implements the standard neutrally
Wouldn't know, as I have never been in charge of one, but I imagine Google having the power to make your browser completely irrelevant would be a pretty strong incentive.
A bit of both? Imagine every time you read the word "actor", it is instead spelled something like "actor:ress", or "actor_ress", or "actor*ress" (because the separator hasn't been standardised).
Personally I'm in favour of it, but I will concede that if it's done enough times throughout the text (as German has way more gendered nouns in common use than English) it does come with the downside of breaking the reading flow.
> Internet Archive Switzerland joins a growing group of mission-aligned organizations, alongside Internet Archive, Internet Archive Canada, and Internet Archive Europe. Together, these independent libraries strengthen a shared vision: building a distributed, resilient digital library for the world.
reply