lemmyvore @ lemmyvore @feddit.nl

Posts

15

Comments

2,750

Joined

2 yr. ago

I'm just explaining why Google can't put YouTube behind a paywall. It's fine as long as it's an open platform. If it becomes a paid product it raises the bar.

With cgroups, it's a standard kernel feature. You can limit RAM, CPU, network access, lots of things. It's used in Docker, LXC, Kubernetes and lots of container solutions.

Lol. Yeah it's all fresh or properly sourced material.

Go search for any music video. You should be finding exactly one (1) official entry. In some cases there are legit live recordings + montage that should also be only one of.

Instead there are dozens or hundreds, and most of them are not transformative enough to qualify for fair use. Google knows which ones are there illegaly because they are clearly able to identify and demonetize them.

But why not straight out delete them, or tell the uploader to delete them or else? Because they want to have lots of content regardless if it's legit, and they want to show ads, just as long as it goes to the right people.

They can put ads on questionable content that's free to watch as long as they're ready to remove it if and when asked, but they can't sell a product based on questionable content. It comes too close to what piracy websites are doing.

There's some hardcore conflation going on that assumes that people with technical skills will tend to be good at everything, or that they'll gravitate towards the uber-geeky stuff.

In my experience it's a very wide spectrum. Lots of programmers are strictly focused on the language they use and don't care to know anything about the OS, or networking, even computers. They are definitely not jacks of all trades.

There are people who can do programming as well as system administration and build a PC and build some book shelves and so on. But that's a very specific type of person who's a tinkerer and happens to be into programming, it's not because they're a programmer.

I've tried Firefox limited to 1 GB for a laugh. It's usable. It won't do many tabs at the same time but it's usable.

You can actually go lower than that but you'll start to run into limitations with YouTube videos etc.

There are also other browsers out there that are more light-weight but perhaps not as feature-full as Firefox. Giving up extensions alone reduces a lot of complexity. If you fire up the package installer on any Linux distro and search for "browser" you'll find a ton. There aren't many engines but there are a lot of browsers.

YouTube was built on illegal content and still has a buttload of illegal content and Google knows it but won't do anything about it. Let's not call the kettle black.

If they really want to be serious about it fine, turn it into paid-only access. It will neatly solve the whole ad debacle and they won't have to play cat and mouse with VPNs and blocking and all these shenanigans.

Ask yourself why they don't do that. It's because 90% of the content on there is illegal and when they host it for free they have an excuse. But if they turn the whole thing private and ask for money to access it they become liable for all of it.

These days I follow a hard heuristic: Always use synthetic keys for database tables.

And the way to follow this rule is fairly simple, but it has a few twists.

For internal use, the best and most common key (in a relational database) is an auto-generated incremental sequence. But it it ok to use it externally? – across databases, across types of data storage, across APIs / services etc.

It's tempting to refer to the sequence number in API calls, after all they are going to that particular database and are only going to be used with it, right? Well not necessarily; the database and the code powering the API are different systems, who says there won't be other apps accessing the database for example.

The current OpSec school of thought is that sequence keys are an internal database mechanism and sequence numbers should only be used for internal consistency, never used as external references (even for the "local" API).

Sequence keys also don't offer any way to deal with creating duplicate data entries. If you've been around for a while you've seen this, the client sends the same "create" request twice for whatever reason (UI lets user multiple-click a button, client assumes timeout when in fact it had gone through etc.) Some programmers attempt to run heuristics on the data and ignore successive create attempts that look "too similar" but it can backfire in many ways.

An UUID is pretty much universally supported nowadays, its designed to be unique across a vast amount of systems, doesn't give anything away about your internal mechanisms, and if you ask the client to generate the UUID for create requests you can neatly solve the duplicate issue.

Do keep in mind that this doesn't solve the problem of bijection across many years and many systems and many databases. An entity may still acquire multiple UUID's, even if they're each individually perfectly fine.

There can also be circumstances where you have to offer people a natural-looking key for general consumption. You can't put UUID's on car plates for example.

https://bbs.archlinux.org/viewtopic.php?pid=1149530#p1149530

I'm just gonna address the domain question.

ccTLD's for countries that are members of the EU usually have pretty strong privacy protection, especially if you are buying as an individual.

.de (Germany) is probably the cheapest (3-4€) but if you're not a resident you will need the registrar to arrange a mailing address for you for a small fee (another 3€ or so). Still going to be a pretty low price.

.nl is another cheap option, without any residency requirement.

The only issue with both is that you can only buy for one year at a time.

The owner's details in the registry are never published. Legit requests in case of abuse etc. need to go through the registry.

Also ytdl-sub would work for your case.

I've had my fill of proprietary media boxes. I have a box full of them somewhere. Eventually they fall behind in codecs and protocols and processing power and updates and they become useless.

I guess I'll bite the bullet and install Kodi in a container...

People who use discord don't want to use it like a forum. They want instant interaction.

If you think about it a lot of forum banter is just that, just because it's slower and persistent doesn't guarantee a higher signal to noise ratio.

If Discord were to add wikis so people can add persistent FAQs and guides it would cover 99% of its user needs.

If Discord would add wikis and improve its search it would freaking destroy everything else. It would be the place for everything a modern gaming community could want.

"Nobody ever got fired for choosing IBM" - or something like that. It's still a great defense when things go bust and they probably knew they would.

That would actually be super interesting. Yeah, let me switch between cams on cars, pit crews, stands, helicopter etc., with real sound where possible. Hell yeah.

I never got mine. Been a lot more that a month.

It's s great fit for people with goldfish memory span.

Sure, but my point was that you don't have to go far to imagine such a thing. It's been here for ages.

It's fucked because there are people buying that shit, in numbers that turn a profit over the cost of developing it. And it's a very low cost because the skin support is something they put in when they make the game, and then get an intern to shit out a gaudy skin.

If you don't like it you're obviously not the target demographic anymore. It's mobile gaming tactics creeping their way on PC.