...sweet summer child
visa is hitting DLSite hard
https://cs.dlsite.com/hc/en-us/articles/1500002888202-What-p...
actually it seems all the major western credit card players have already blocked them. i remember seeing pay with crypto so i guess thats what you need to use in the west
Another framing of this: Mastercard / Visa, and by extension whomever had them to do the crackdown, are now powerless to change DLSite.
Googling for news, it seems like the story between DLSite and M/V is a push and pull. Many articles turn up that say they have an agreement, then a disagreement, then an agreement again, then a suspension, then they bring it back again etc.
My point here is that their relationship with M/V seems to have failed to actually change them, so, the point "they're powerless to change Japan" stands.
I see the assault, but the results are very different from what we can see with Steam and itch.io - I think maybe because of how much M/V matter in the West vs. Japan. Whereas these western companies gave in to pressure, the same pressure in Japan didn't work, the stores just seemed to restrict the card usage, and call it a day.
I wish other payment processors spread in the West. With a much more even distribution of power, they could not abuse it like this (and others could not use them to abuse it like this).
No shit, people just use a different credit card, instead of the site pulling a game or shuttering, because these groups have no power beyond pestering Visa.
Not that anyone saying "sweet summer child" ever had anything smart to say.
"i remember seeing pay with crypto so i guess thats what you need to use in the west"
In other words you know nothing and couldn't be bothered to look it up before posting.
>I haven't heard of this. Is Reddit enforcing ID verification
just double checked, thyre enforcing you to validate a date of birth with an external camera based system
>Generative AI is administering the fatal injection. This experiment has nearly reached its conclusion.
i was hoping to avoid draw a defitionist conclusion for this. it seems like thats whats the world is doing. theres literally no pushback to this IRL, most of the public seem to be in favor of these IDs system
Is there anything we can actually do to combat this?
Im short of ideas, tho the 33% rule can be potentially worked around by generating loads of fake content similar to a previous poster who generates fake content for scrapers to eat
Im in the UK and they recently passed a similar law banning any explicit _imagery_, which I already thought was bad but the land of freedom beats us out again, the literally surveillance state, at least that's that's enforced top down by ofcom instead of an army of injury lawyers so it works at ofcom's speed
I dont understand the needed distinction between "chromium" and "non-chromium" browsers, thyre just web engines and ultimately technical details. Although chromium having significantly more compatibility (or chrome features that websites use) the average consumer will be using websites that keep strict accordance with webstandards to support safari.
For technical users its another story but for the average user the web engine of your browser doesnt matter, just the shell around it, so I find it quite silly the notion we need X browser and also an X chromium browser
Some people think it’s important to support more browser diversity by not using chromium-based browsers. Some people also think that it’s bad to use pretty much anything produced by Google. Plenty of reasons to want non-chromium browsers
For me personally, it comes down to diversity. If all other browser engines "go under" and we are only left with Chromium, websites can only be built for 1 browser. Although Chromium is a great engine (evidenced by how many browsers are built on top of it and how widely the underlying Chromium engine has been embraced), it's not without quirks, bugs, flaws, and vulnerabilities.
Firefox is built from the ground up in a different way from Chromium, with its own set of bugs, quirks, flaws, and vulnerabilities. There may be some overlap, but having entirely different architectures means we keep pushing the compatibility envelope, we get "copycat" features, where one engine does something great and the other implements it in a way that works with their own engine, etc.
It's just better to have more than 1 browser engine around. I wish it wasn't so difficult to start a new engine from scratch today, the sheer amount of features a web browser must have to get people to even consider reading your About page, and the overwhelming complexity of modern webstacks, mean you basically have to be grandfathered in as a browser that's been around for decades and has a huge amount of community support.
I am aware of alternative browsers, Arc and the like. I'm very happy to see someone seriously go after an entirely new browser engine that's not Gecko or Chromium, and the traction they're gaining while not being "fully featured" sort of sums up the sentiment of my message (I hope). Having alternatives is good.
And there’s the other side of the coin: some websites break in Firefox (and other non-Chromium brewsers, perhaps). I’m keeping Ungoogled Chromium just in case (and for testing my own websites, of course).
(Remember to complain politely, but loudly, if something works in Chromium only.)
I only started really using Firefox as a daily driver probably two or three years ago so I’ve been lucky to have my compatibility be like… 99.9%. Little snitch and my VPN break far more sites than Firefox does. But I keep brave on hand just in case.
The accuracy of this tool does not matter. This is exclusively designed for box ticking "reports" that nobody reads and a produced for the sake of itself.
The new term for this is "AI Loopidity", highlighting the unintelligent ouroboros nature of one side using AI to generate content and then another side to consume content.
“Pencil-neck” is a strange insult to use here. How are software developers, or hardware design engineers, or finance workers any less “pencil-neck” than “board of directors”?
