If you can't determine, with the same level of certainty as any sixth grader, whether 17077 is #prime, then you are neither intelligent organically OR artificially.
No, it really bothers me. And it's so clandestine and leaves me with the distinct impression there is obfuscation delivered as authoritatively masquerading misinformation.
So I swapped out the first word of each sentence to clarify what those fuckers are actually saying, while pretending to say it isn't that way. Fuckin' bitches.
The first word in each sentence used to be "Allow" and "Offer", respectively.
Now a more accurate, straight forward, and honest edit follows:
Compel web servers to evaluate the authenticity of the device and honest representation of the software stack and the traffic from the device.
Enforce an adversarially robust and long-term sustainable anti-abuse solution.
I encourage prettier to give this this a quick read - it isn't difficult to comprehend what's really being said here and what the grand design is.
I'll comment further on this discussion as to how I perceived this upon initially being alerted to it by @ariadne over at @Fediverse:matrix.org but suffice it to say this is but a particularly #FOSS, #Privacy_Respecting, or #DeSoc friendly campaign.
The big news here isn't the headline, it's what's buried in the article itself - an article that links and clings to non #Fediverse, deprecated silo resources like Twitter to pad the results of cooperative studies between these two universities.
Of particular note is an apparent broken promise to #open_source the technology on one hand, and the infinite power that #FOSS can play when millions of eyes are on the prize with cooperative development.
The big news here isn't the headline, it's what's buried in the article itself - an article that links and clings to non #Fediverse, deprecated silo resources like Twitter to pad the results of cooperative studies between these two universities.
Of particular note is an apparent broken promise to #open_source the technology on one hand, and the infinite power that #FOSS can play when millions of eyes are on the prize with cooperative development.
If you are horrified by the Web Environment Integrity proposal by Google (#DRM for ads), stop using Chrome and switch to Firefox and block ads everywhere.
The only eyeballs left for Google to show ads are the ones protected by ad blockers. That’s the highest growth opportunity they have, and we cannot let them have it.
Nobody uses that crap anymore anyway - they use Firefox, chromium, Vivaldi, Brave, among others instead.
Oh! Wait! There still exists stupid people in this world, but have no fear, Darwin will prevail and natural selection will eventually descend upon them.
Seriously though, with so many continuous and severe advisories by the likes of #DHS and others, one does wonder why even the subjugated chattel still insist.
Let's pretend we're proponents of free and open source software, enlist an army of week intentioned FOSS developers to contribute to our project, and once successfully deployed in many enterprises across the industry...
Pull the rug out and convert it into a proprietary product with a bunch of undisclosed, hidden code that we won't ever show you - Muahahaha...
Yeah. I see this happening right now in several prominent and celebrated open source projects that you're probably completely oblivious to those sinister objectives.
This is why the most ubiquitous desktop operating system in the world is Minix.
What's that you say?
Yup, Minix. But that's no secret, the cat was out of the bag on that one a few years back (after being secretly so for many years).
Before you contribute any more code, translations, or documentation to a software project, consider this:
Now, there's another point to be made here, without specifically naming any projects currently abusing user contributions. Let's call this hypothetical project "hammer&anvil", itself a fork of a popular software project - but claims it's all about being free and transparent, wanting to distinguish itself from the project it's forked from by adopting GPL3 instead of a permissive license.
Sure, the project's BDFL (let's call her "Strawberry Daiquiri"), says one day, "were forming a fork of project X because they've formed a company and I'm afraid what they are going to do with X because it's under a permissive license. This girl will be brutally transparent and completely run by the community under the philosophy of anarchy, but we're going to call it a sociocracy so you don't know that it's really just me making a proprietary product for my own ambitions".
Well, Miss Daquiri decides to capture by capitalizing upon the sentiment that folks have for Copyleft - it's supposed to protect free software, right?
Well, this fork (hammer& anvil) is a hosted solution - meaning SaaS, meaning, it runs elsewhere (other than in your computer) in the cloud as a publicly accessible service. Hmmmm.
That means that the most appropriate Copyleft license is likely the AGPL, and not the GPL as one would expect fur a desktop or other local program that you actually download and install in your laptop or server.
The GPL requires that when you distribute (give away or sell) your program, either by letting someone download or handing it to them on a USB stick, Etc., You must also make available ALL of the source code, including any changes you've made to the program.
But if you run a modified GPL program as a service in the cloud you don't have to provide ANY off the changes you've made to the code.
Hmmm.
With AGPL you do have to supply your users with ANY code modifications you've made to the running service to which they have accounts...
So let's just say that you fork Mastodon, and call it Glitch-Soc, modify it, and run it in the cloud for people to create accounts on and use (for free or for monthly subscription fees - it doesn't matter). ANY and ALL changes to the code base that you make MUST be made available anytime a user asks for the source code, because it's an #AGPL licensed product.
And in reality, such is actually the case with this exceedingly popular and capable #fork. It's a fine product in it's own right.
But had you changed the license to all contributions moving forward to #GPL, you wouldn't have to provide any modifications you made (unless you give or sell the software product itself on say, a USB stick or via download).
Why? Because you're just allowing them to access and use your service, your not actually giving them the program to use for themselves elsewhere - so any modifications you made since forking under a different license (GPL instead of AGPL) isn't something you have to show them.
You've essentially created a #proprietary product (if you're so nefarious as to hide your code changes by butt disclosing them), the only code of which you must supply being that which existed under the AGPL before you forked it.
Both #Copyleft and permissive open source #licenses like #BSD and #MIT can be a good thing, or they can be abused beyond the intentions of the #FOSS inclined project contributors. Just make sure that you understand what can and cannot be changed where your intended purpose for the #distribution and #availability of source code is concerned....
There are BIG differences between the ramifications of each #license and how they can affect transparency and distribution of your free gifts to the world.
In our hypothetical scenario with hammer&anvil, the #BDFL, #Strawberry Daiquiri, has decided that she's going to launch a hosted service, and she's going to include things that you don't see and can't be aware of behind the scenes which, if disclosed, you would have nothing to do with - but you'll never know what kinds of scary things she's done with the product that only resembles the original on the surface, because Miss Daquiri will never have to show you the code she has added behind the scenes.
"Beautiful Victor, Beautiful."
-The Monster, speaking to his creator in the film, 'Frankenstein, The True Story'.
Well, not really before, coz we did air fry them before adding the cheese some, and the prep was to mince bacon, onjions (sic), anda couple of portobello stypes, frying and reducing them in an iron skillet, then filling those jalapenos, before putting them into the air fryer for less than ten mins at 375° F, then sprinkling either shaved mozzarella on half or a Mexican blend on the other half. It's def a recipe to scale up, leaving your lips tingling.
I'm a few days late posting this. Certain projects and utilities I try to showcase as soon as they come out of the oven, but lately I've been tending to other, more pressing matters since my move back to #SuperSunnySouthernCalifornia - like chillin' at the #beach, #spearfishing, and of course, bangin' it out with girlfriends I haven't been able to hangout with for over six years.
Whenever I troll that out, I manage to snag another fellow #Slacker or two - or at least, someone who understands intimately, the dynamics of what was going on in the #distro world back then.