Yes, i point out whackamole in my comment. It’s a completely useless critique of tor/briar because there is no alternative which cannot also be critiqued like this, and there can never be.

you might as well say “well the problem with keyboards is that someone needs to ship it to you.”

oh sure, but you can get around these blocks and this sort of block is ultimately always a possibility short of building your own network infrastructure. and as blocks like that become more common it becomes more common to circumvent them too.

“significantly harder than youve been lead to believe”, no, you just werent clear in your description of the problem. if your problem with tor is “governments can play whack-a-mole blocking ips and traffic” there is no technology which doesnt have that as a downside.

“the tor protocol can be locked” ?

tor is decentralized, if someone’s tor server goes down you just go to another.

it might be a difference of language but it’s important to recognize that courts are part of your system of governance regardless of the words you use to describe it, and are subject to most of the same incentives and corrupting influences, and some thatare unique to courts.

courts are part of the government…

or want a pixel, or want to buy a new phone. the insistence on pixel support only is frustrating.

If they can target the underlying architecture of the models like nightshade does, it will actually be quite hard to deal with for the surveillance companies.

Yeah I don’t agree with the osd being the only approach to being open source. Turns out people have differing opinions on that. You’re welcome.

It wasn’t a response to my comment because you didn’t respond to my comment. You said is proprietary. I point out that it’s not a terrible license. Then you resort to a sound bite non response.

You could have pointed out for example that ftl 3.2 and 4.1 are pretty shitty limitations to impose.

Ah. Of course. Something being open source doesn’t make it open source. It all makes sense now thank you for clarifying.

That also wasn’t technically a response to my comment, it was an ideological defense mechanism to avoid addressing the content of the license.

This license while not the most permitting does not appear to hide the code behind any proprietary shielding though.