CrypticCoffee

So if it isn't a RCE vulnerability, what vulnerability is it?

If you think I'm a fan boy based on "even if he is an egotistical man-child living off the proceeds of hereditary wealth", you're need to engage your brain, my friend.

When you're picking only the points you like, it's called confirmational bias. On the same Don Lemon video you quote, he admitted he bought it to protect freedom of speech, regardless of if it costs him money or not. Obviously, it's his over glamorised version of events. Here "freedom of speech" means proving a space for only those that agree with him, which is what I alluded to. Considering your dislike for Elon, you're intolerance of anyone with a different opinion to you is strikingly similar.

For someone so anti-Musk, you spend an awful lot of your time posting about him. He's living rent free...

Because you don't agree with them, they're a fan boy?

He's a billionaire who bought a platform to create a public space for right-wing political discourse so those ideas can get pushed into the mainstream. He bought it like every right-winger buys media, for influence. If he can push policies that favour his businesses, he can gain more back from his other businesses.

The fact you dislike him makes you want to think he's an idiot, because it feels nice and validating, but ultimately, there is motives behind his actions, even if he is an egotistical man-child living off the proceeds of hereditary wealth.

Why does this feel lie a viral marketing campaign to get people to watch stuff on X?

"I interviewed Elon, got cancelled and he mad. Watch on X". It just doesn't add up to me.

Edit: It's not on X, apparently. It's on YouTube. So I was probably a little out on this. Very clever viral marketing still, but hopefully not to the benefit of X.

They sunset Atom to push VS code despite assurances they wouldn't.

Co-pilot slurping open source code and spitting out code without license attribution. One example of this was when it spat out Quake 2 code and comment verbatim.

Enshittification started, you just ain't ready to see it yet. MS has a track record and will continue.

2 git hosts is just 2 tabs and by the time federation happens, you've already got vendor lock in because of all the issues. I doubt migration of those will be straightforward.

Interesting project and good luck on this.

Did you not consider something like Codeberg to host this? Many open source devs do not trust MS or their stewardship of Github, and considering the aim of this project is against American control of information, surely this really needs serious consideration.

Many open source devs do not want to use Github at all now.

Usually when you change your database structure, you would change the object that this is mapped into. If you were to change one without the other, that would be a monumental developer oversight. Adding a field without using it in many frameworks wouldn't necessarily break it, so it wouldn't be a bad change per se.

Any change you make to persistence should reflect as a bare minimum, the object data gets mapped into. This would likely be part of the same branch, and you probably shouldn't merge it until it's complete.

You're looking for tooling to protect you from human errors, and nothing is going to do that. It's like asking, how can I stop myself from choking when eating. You just know to chew. If this isn't obvious, it's a good lesson in development. Make one change at a time and make it right. Don't rush off to presentation changes or logic changes until your persistence changes are complete. When you get into habits like this, it becomes steady, methodical and structured. Rushing is the best way to make mistakes and spend more time fixing them. Less haste, more speed.

For example, if I add a new field. I'd write the SQL, run it, populate a value, get that value and test it. Then I'd move on to the object mapping. I'd load it into the code, and get a bare minimum debug out to see it was loaded out, etc. etc.. Small tweak, test and confirm, small change, test and confirm. Every step is validated so when it doesn't work, you know why, you don't guess.

Most languages have an IDE which will manage the import of that object and when you rename incorrectly, it'll flag it up. If you're calling an incorrect function or variable, it'll flag it etc. Many will have refactoring tools so when you rename something through this, it'll rename all instances of that.

Most users find mobile banking works out of the box on GrapheneOS.

I'm not disputing the last stuff is not fun. Matrix works quite well and you can set up a bridge with discord. Using spaces correctly cuts down spam easier also. The problem remains, even if you set them up, my experience is 92% of users come in through Discord. I'd love that to change, but it's just a fact of the matter.

Why when you can use GrapheneOS. FOSS, privacy respecting Android...

The moment you collect data, it can be abused. To stop abuse, we must stop data being collected.

Maybe just prevent MS merging or buying anything ever again until they fix shit. Ultimately, if their assurances aren't worth shit, any case they put forward cannot be believed, and to the contrary, will likely be unreliable.

If you can, force them to split in certain areas.