All because they throw it into b2b with teams and ado and windows and whatever other shit they call software.

We have no control over data retention or anonymity.

We grow organically. We barely get any reports. If we do, I’ll block or add a comment why it’s kept for transparency. Mod log is public.

If you think the approach needs adjusting, feel free to suggest what and why. Do remember I’m a volunteer though. Limited time.

My issue is that corporate folk behind this attempted to do this. IMHO, the stewardship of the project is all wrong, and the motives questionable. It did feel like you were defending their actions. Corporate influence is not a defining aspect of open source for me. Its an unfortunate problem that ultimately leads to the true dilemma. Open source is about sharing and giving your time freely, corporate goals is how can we profit from our position in this project.

Through pushing through user antagonistic changes completely at odds with users wants and hoping people are pliable enough to forget all about trying to be screwed so you can bide time until the next at attempt to screw users?

Well, that’s the vibe I’m getting from you. I naively assumed open source was based on trust, shared effort and contributions to benefit users so they can install software on their machine that they know is reliable/trustworthy and privacy focussed because anyone can scrutinise it. Silly me.

So they raised a PR with the intention to do this?

Are you saying the only reason they backtracked is because users weren’t happy?

I think originally it was the other way and many distros use a compiler flag to stop it being opt out.

They tried to add in opt out telemetry in. A few forks were created as a result.

Meh. Prefer Tenacity without the enshittification.

deleted by creator

If you enable overlay, does it work?

Did it ever work? If so, when did it break?

No. It’s a reference to super productive devs. The 10x devs. You can have unproductive full-stack developers and rockstar back end devs.

Startups hack things in to production?

Shocked, I tell you.

Source available fails on principles of open source. Such as the right to modify and distribute.

Oh do tell… As I think you don’t understand how LLMs work…

Like AI can tell good code from bad. Just common vs uncommon usage.

You must work in dreadful places. I’ve seen it a few times, but most places have been productive.

It needs a good lead dev to set the culture though.

Whitespace change debates can be avoided by using rule sets in IDEs and agreeing standards within the team.

Good static code analysis tools in pipelines and IDEs handle most technical issues leaving reviewers to focus on design, maintainability, clarity and readability.

You can avoid pickiness if you communicate why, so they learn and understand. If you use PRs as a training and learning tool they’re quite productive. If not sure, ask why something was done.

And if you get picky comments respond with “personal preference and not part of team rules”. But also, you cannot be defensive in your PRS. You have to be open to feedback and points and happy to discuss. Be polite even when feedback is invalid. Defendivesness kills constructive feedback and no matter how old you are and how long you’ve been doing it, you can still improve. Oh and if you been doing it that long, you’re a senior or lead and can influence how things are done.

Is GTFS short for Get The Fucking Schedule?

I want it to be true.

With some, deleting and recreating accounts may work. Some may be tricky.

The less Google usage, the less data they get, the less they understand about who you are now.

A distinct lack of integrity. I’ve avoided jobs for companies who I know build nasty stuff. I don’t want that on my conscience. If I’m semi-competent at my job, I’d be enabling the acceleration of that.