Wow! Wish the majority of packages i encounter has this problem; too many releases.

That sounds really nice. Actively maintained packages for a change.

Cut these States out. Forever. Let them be as examples of what happens. Stop providing them FOSS and maintenance.

Or

Will have to write a software license targeting companies and boot lickers imposing kyc.

I wrote the, not yet published, framework between sqlalchemy and web routers e.g. litestar and FastAPI.

Will be monitoring this. If it appears distros are more than willing to impose kyc or even entertain the notion (kyc as a thought crime), will expressly exclude them by imposing rates that would bankrupt countries.

You cannot impose kyc so can use my own packages and expect me to go along with it.

Also can contact other developers and ask them to switch over to an aggressive no-kyc license from their permissive licenses. Targeting packages known to be used by offending distros or other distribution channels.

kyc is a cancer. Will enthusiastically hunt it down and ostracize it.

linux is not exempted. Open your eyes and survey some cafes access points. They have rolled out captive portals everywhere. Linux runs most routers and some variant of BSD runs the rest.

These are the lawmakers main target. Cuz corporations can't wait to comply with edicts.

Exactly! Boot lickers (kyc as a thought crime) are also expressly excluded from using packages i've written.

What i'm suggesting is a supply chain attack targeting only imposers of kyc. Only change is the license.

Each web site is built on a tech stack. With shared tech stacks. There are only a few possible choices.

Would only have to convince very few authors and it affects the entire planet. Cuz many of these packages are not easily replaced.

Our tech stacks are hanging on by a thread. Maintenance is very underfunded which screams, at risk! Without the good will of maintainers and them self-funding the maintenance, all the companies making web sites would have have legal liabilities hanging over their heads, if they ever dared to have their web site impose kyc.

Is there anything else can help to clarify?

it's more than merely about imposing kyc. "Age verification" entails asking to provide a photo. Which is then sent straight to the US and Canadian govts and compared against other people's photos. It's an intelligence gathering operation.

This is a fact, not a theory.

https://vmfunc.re/blog/persona

That already happened. Privacy browsers are a reaction to the enshitification of browsers like firefox.

Would like to modify aGPLv3+ license and include the following clause

Web sites, apps, blockchain smart contracts, desktop apps, or scripts that include Background IP in their tech stack and found to advocate, consider, or impose kyc on their users, having not obtained a waiver beforehand, incurs fee of the amount, 10x previous year's GDP of the country with global reserve currency status or largest economy, whichever is greater. User authentication should be limited to the top 2 private privacy IMs. Login walls requiring email verification is kyc. Paywalls that don't provide the option for Monero or offer Monero payment option but not at a discount, is kyc. Physical address verification, although kyc, as long as there is a physical product involved, does not trigger this clause.

aGPLv3+ already says companies have to seek waiver for commercial use from the author.

This is how Python package authors say, Sure np there is just a fee involved.

Saw this posted in another thread. Being able to compare features raises the intelligence of the conversation.

It's worth the read

https://eylenburg.github.io/im_comparison.htm

"I admire your creativity. Will talk with our team, get their feedback, and timeline. See when can add support for emojis in usernames"

i'm not so sure. Shitting over code takes actual effort and skill. Wish more people took the time.

Have never had the experience. Feel free to prove your point

https://github.com/msftcangoblowm

Because foreign packages have been STEALING our CPU cycles for TOO LONG! It's time to put AMERICA FIRST and make importing FAIR and BALANCED again!

What is the novelty of that? Did they invent mood, voice tone, computers, or coding?

Also it's against the public good. So shouldn't be protected by gov't. We don't need Minority Report childish "tech" deciding how to censor, not only our speech, but our tone of voice?

Doubt this patent could stand up to scrutiny. Is this all Meta can come up with? They better stick to buying up companies.

any sufficiently washed crypto is better than fiat

Actually not really. opt-in privacy is worthless. Being the only one making private transactions within a sea of users making transparent transactions is worthless.

paper fiat currency is mostly anonymous for offline transactions between two people.

For online transactions, privacy is actually very very hard. So not all cryptocurrency are created equal.

And mentioning ETH and pretending it's a cryptocurrency is misleading. It's PoS (1998 technology). PoW was created to solve the problem of PoS masternodes.

Thank you for introducing me to act. First time seeing it.

i ditched Ubuntu for Void Linux LXDE. Void Linux has runit rather than systemd

This predates snapd

Disclaimer: you have to setup the wifi and enable logind

Oh look!

This noob doesn't know how to setup a TG bot. What a poser

Oh wait! That's me

willyoumarryme_bot_telegram#1

To the upvoters. Why? Why do you think this is worthy of our time and attention?

I downvoted this article cuz this patent is unworthy of a post.

You are right! What a lost opportunity.

Tools i recommend:

• rebuff -- finds places in code to replace with better algorithms. Wanted a tool to recommend itertools and itertools-more usage, but achieve that. Chosen cuz it's not Rust.

• typos -- fixes typos in both code and docs

• mypy+pyright+stubtest -- need all of them. pyright phones home. mypy isn't enough it misses way too much.

• pretty format YAML

• cyclonedx-bom -- create software bill of materials

• pip-licenses -- NOTICE.txt and licenses.json Answers question does my toolchain include virus licensed packages?

• interrogate -- Any code documentation missing? Does not enforce documentation quality.

• wreck -- sync requirements files; otherwise it's tedious (i'm the author)