I get what you’re going for but this would absolutely wreck privacy. And depending on how those signatures are created, someone could create a virtual camera that would sign images and then we would be back to square one.

I don’t have a better idea though.

It’s no accident that capital is aligned with fascist. Line must go up.

Startpage for the win!

Instead, these searches return a list of traditional web links.

“Oh…oh okay. So you know what that is. Why are unable to provide traditional web links for ALL my searches? Because, I’m gonna be honest with you Google. I never asked for you to ‘summarize’ my web results and the fact that you can turn it off at your discretion tells me that you could turn it off for everyone.”

Fortunately it doesn’t federate

Ftfy.

Absolutely LOVE syncthing. I recently had to go on an emergency trip and was glad I set up syncthing on my phone but hated that I didn’t set it up properly on my laptop.

If you simply want to allow people to view your code, you can just upload it to GitHub or something similar.

By default, your work is copyright and you hold all rights, excluding those you give up to GitHub.

Open-Sourcing your project is all about choosing the license that you want your users to use.

Please, for the love of God, choose an existing license. Don’t go out and try to make one yourself or mix and match. Not only do you open yourself up to liability but it just makes it harder for you to keep track of it.

Choosing a license is all about your personal preference and what your goals are. The two ends of the spectrum:

• MIT License: do whatever you want, so long as you attribute me. Most libraries use this license.
• GPL/AGPL: if you use my code, you must also release using GPL/AGPL or similarly appropriate license. Linux Kernel famously uses version 2. Linus Torvalds has issues with some of the terms in V3.

There is a lot of middle ground between these two philosophies. Most of the major licenses have seen some level of court cases. I personally use AGPL, which is often seen as one of the strongest, most restrictive, licenses.

I do not recommend releasing code to public domain. This often is a point of contention between OSS purists and OSS “spirit”. I personally believe we’re entering a new world of AI-driven content and I don’t want more code feeding that beast.

The license is then copied and pasted to a LICENSE file at the root of your repo and, boom. You’ve open sourced your code.

Keep in mind: that commit (and all future commits) will be available under that license until your copyright expires, so long as that license exists in your repo. You cannot claw it back.

One word of advice: you aren’t likely going to see a bunch of people downloading your stuff. So don’t get your hopes up that you’ll have people submitting bug reports or making PRs, etc. All of my projects are just for me to use with one or two people reviewing it for fun. All but one, anyway.

It might help to know what exactly you’re trying to do. Are you trying to automate something? Buy stonks? Download porn? Click ads?

There might be better solutions than automating a browser.