I think it could be a great solution. I’ve never considered it before. That said there’s one sticking point for me:

Apportion payment to developers based on software use by paid users and the size of their contribution to that software.

That^. That needs a lot more detail. If they provide solid details there that most can agree on, then I will actually be on board with the solution.

Yeah I wish there was a way to contribute to the hosting with torrent-like seeding. My phone can seed a torrent, but its not going to host an instance.

1 like = seed for 1 month seems like an interesting model

Labeling datasets is costly process. When you dont opt out, you’re letting them build a labelled dataset on you-specifically for free.

Same for me: just say no, and they say OK. Effortless but the option is totally invisible.

The irony is, I’ve seen the staff stop using the face scanner for everyone halfway through the line to speed things up. So its not saving time, just costing money to increase surveillance.

Yeah, cookies, account logins, and other stuff make it hard too. Ex: randomly exploring gmail emails at different times of day, but not actually marking emails as read.

Psychology. Ever see ring doorbell footage where the owner says “drop the package” and people do? Its not like the owner could do anything, but for some reason it makes people behave differently.

Here’s a very similar question I asked here a few months ago: https://lemm.ee/post/8165932

The clients are source available for telegram though

I mean technically the client is verifiable if you use discord in a browser tab… and verify it every time you load the web page… 🙃

Celebrities are going to be shocked when they hear about email

Distros should ship with this this under /readme.jpg

(I know I’m two months late)

To back up what you’re saying, I work with ML, and the guy next to me does ML for traffic signal controllers. He basically established the benchmark for traffic signal simulators for reinforcement learning.

Nothing works. All of the cutting edge reinforment algorithms, all the existing publications, some of which train for months, all perform worse than “fixed policy” controllers. The issue isn’t the brains of the system, its the fact that stoplights are fricken blind to what is happing.

Cool, this is exactly what I was hoping to learn but couldn’t find. It sounds like its still a pretty manual process, but thats okay. If thats how it is righ now, then thats exactly what I want to know.

I’m considering making tools (GUI local app, but also website AUTH frontend/backend tooling) to try and make systems like this more commonplace and standardized. I didn’t know about revocation keys, so I’m glad I heard about that before trying to build my own.

Nailed it

Yeah, sorry I incrementally edited the title before posting and accidentally made it make no sense. I meant publicly announce that a private key was compromised

I don’t see anywhere in his comment(s) where he says something postive about privacy guides.

Use e2e for all communication you can

He got convinced, its now Auxolotl!

https://github.com/auxolotl/

Theres going to be an official reevaluation once the governance has finished bootstrapping.

I read it as “a pin nix” like appendix with a lisp

Agreed, I made a thread for it. You’ve got some good names!

https://forum.aux.computer/t/aux-name-enhancement/179