undefinedTruth

u/undefinedTruth@lemmy.zip
0 posts · 179 comments

Recent posts

No posts.

Recent comments

Yes, but what HuggingFace is doing here is the distribution of a data set. And so long the data set itself is open that doesn't conflict with GPL. HuggingFace is not responsible about how others use that data set.

Whether LLMs themselves violate copyright for being trained on MIT or GPL code is an entirely different discussion.

In all honesty, I don't actually regret buying it during a sale several months ago. I do have an RX 9070 XT however and regardless the lack of optimization I was able to make the game run fine on Linux.

It's basically the classic Oblivion with improved graphics, animations and a better UI. There are bugs of course, but the vast majority are inherited from the original. I do honestly think that the remaster provides a better experience than the original, but only if you have the hardware for it. Otherwise, just play the original, it is the exact same game in regard to everything else.

With that being said, Skyblivion seems to finally be right around the corner. So, if you are a little bit patient it should come out by the end of the year.

on Traitors · c/memes · 5 pts · 4d

Most of this stuff is done locally by the browser using media queries in CSS. There is no reason for that data to make its way to the server.

on Traitors · c/memes · 5 pts · 4d

Dude, language detection is literally done with a simple HTTP header set by the browser. There is no need for all the other crap.

It does work with screen readers but their solution seems far from ideal. Also, that relies on the fact that the scrappers don't typically run JavaScript.

Screen readers (used, for example, by people with visual impairment) work from the source code, where your words are already swapped. The font only fixes things on screen, so a shielded block would be read aloud as fluent, wrong English. Shielded sections in our React tier carry aria-hidden to stop that. In its place, an opt-in beta ships the correct text encrypted in the page. A button only screen readers reach asks the reader’s browser to solve for the key: a chain of steps where each one needs the answer to the last. It also needs JavaScript, which most scrapers never run. The cost currently lands on the reader: up to twenty seconds on a slow device. That is friction, and it is the part we most want help fixing.

Pretty much, yeah. Unless each site owner creates a custom mapping.

The font must be sent to the browser so it can display the original words. Anyone who downloads it can therefore inspect it and work out the substitutions. That is unavoidable. But our goal is not to stop someone who deliberately targets a specific site. Instead, it is designed to disrupt large-scale automated scraping, which processes many sites without examining each one individually (because that costs money). ShieldFont currently ships with three different word mappings and gives publishers the tools to create their own, so decoding one mapping does not automatically reveal the others.

You can turn on the AI killswitch and then allow just the translations. If you do that any new AI features added in the future will be disabled by default but translations will always work.

If the whole idea is to just add some friction then you can use your password manager to generate a password for that profile you can't possibly remember, instead of using a numeric PIN. That way each time you want to switch to it you will have first to go unlock your password manager.

Don't be ridiculous, I would never make the phone call directly from the Thinkpad. I would just install Asterisk on the Thinkpad and then use it as a PBX where the cell module acts as the voice gateway. And then make the call via Linphone on my mobile device connected to the Thinkpad over WiFi.

on Here we go · c/memes · 3 pts · 10d

You are saying OpenAI paid HuggingFace to say they got hacked by their rogue AI agent? Noooo... I don't believe it one bit.