Replying to @⁨inclementimmigrant@lemmy.world⁩

Shout out to Fluxer.

Still don’t think its quite ready but its chugging along and its been fun following the progress. I know they have some big updates inbound. Hopefully people actually give it a shot and flip over to Fluxer.

I’d also add that the “Proton” subscrition equivalent - “Plutonium”, is a better value proposition. But I will admit, they still need to clear a few hurdles before even I feel completely comfortable ditching Discord.

But its Open Source and it has a self-hosting option, along with the Quality of Life you expect from Discord in terms of the app layout, screen sharing, etc.

Edited ⁨⁨Sep⁩ ⁨28⁩, ⁨2026⁩, ⁨18:44⁩⁩en

Replying to @⁨dan@upvote.au⁩

The new one usually won’t have the same issues at first, but they’ll have the same opportunities and motivations that lead to the issues. People will see a different provider and say they’re not doing the bad things, and they’ll be correct for a few years maybe, but then it becomes a struggle to get them to switch to the next thing. This whole problem would mostly be solved with open-source alternatives instead.

Replying to @⁨Cethin@lemmy.zip⁩

The thing with age verification is that it’s a legal requirement, so they’re all going to have to do it.

Running an online service with a lot of users is very expensive, too. All these proprietary services eventually realise that they need revenue in order to continue operating. That’s one of the reasons why decentralized, federated services are the way to go - everyone runs their own small community, so there’s no one company or person that has to cover an enormous bill.

Replying to @⁨dan@upvote.au⁩

That’s why I think we should start teaching FOSS Linux as the first operating systems Kids are exposed to. It’s neutral ground in the sense that no one company owns and controls it, and the things they learn will help them understand why things are the way they are, not just what the latest marketing-hype “feature” is.

Someone I know went to a university that ran off Linux and I’m jealous of the comprehensive Linux 101 they got. It took me years to learn some of that stuff.

Replying to @⁨Glitchvid@lemmy.world⁩

It’s not, people are objectively being retarded about this. They merged in the actual prod code base from the closed private repo that had the entire small team working on it for months. Into the open source public repo when as the first major refactor and functionally went from preview build to first real public beta.

A few million lines of code from a small team and a number of one of contributors over months of work on a brand new project is perfectly god damn normal.

The repo went from elevator pitch to real product in one go cause the work had been done else where.

Replying to @⁨nulluser@lemmy.world⁩

Not necessarily. Huge additions without matching deletions often happen during restructurings like vendorizing dependencies, importing external packages, generating bindings, or migrating private repos into a monorepo. In these cases new code canbbe introduced to repository and there will be no corresponding deletions in commit history.

I’ve did similar restructurings myself, eg. Making automatically generated resources static

Replying to @⁨northertech@fedia.io⁩

I’m not sure why you’re being so hostile, but you’re fundamentally confusing a codebase’s hand-written LoC with Git commit additions.

Nobody is saying someone authored 11M lines. Commit fa3e8525 was a workspace reconciliation - importing external repository code, dependencies, and assets into the public repo for the first time, so exactly the type of thing I was talking about. Git counts all imported lines as additions.

Before asking others to “stay in their lane”, maybe make sure you understand how Git history handles repository imports and dependency tracking. Have a good day.

Replying to @⁨douglasg14b@lemmy.world⁩

Just speaking from personal experience. Here’s a story.

One time I did a massive refactor, basically touching every function in the software. For background, this was a massive enterprise application. The backend was about 10 million lines of code, the front end was… probably triple that, I didn’t bother counting. Yes, building the code took more than an hour, even on extremely beefy machines.

The reason for this refactor was there was a huge amount of tech debt that finally caught up to us. You know, putting it off for years, using deprecated functions and old methods, feature flags, even forking software and modifying it to be compatible. Just years of finding creative solutions, until finally things said “enough” and there was no more bandaids. I was given the green light to fix up everything at once. Programmer’s wet dream, at least for me; I was so happy.

Anyway, in this project, we did rebase not merge. So, after 3 months of working diligently in a branch; I had to rebase the whole fucking thing because my coworkers obviously weren’t idle that whole time. This part I didn’t enjoy so much.

It took 2 weeks to rebase all the merge conflicts. It took so long, I had to rebase again. Multiple times. Each rebase getting closer and closer to being able to finally merge into master.

Finally I did it. I told everyone else to just relax and take the day off, while I merge into master and fix all the problems. There was many problems of course. But the final commit was tens of millions of lines of code changed, all by myself. This was before LLMs. But I have the type of brain that can sit there for 9 hours straight every day and tidy up code and enjoy it.

Edit: just to clarify, “rebase” makes it look like all those changes happened at once instead of spread out over months, and would make a huge spike like that. Also just because LLM wasn’t a thing didn’t mean I did it all manually… I heavily used find-and-replace, upgrade scripts, codemod, and many other automation tools. I think I even wrote a few manual codemod scripts to get it done.

Replying to @⁨lordziv@lemmy.nz⁩

Not when it’s a fucking private to public merge. Why the fuck would a tiny public repo that was basically a elevator pitch in code base form send up red flags when you merge in the actual product that includes the better part of half a year worth of development from a team of people?

Are you allergic to context and critical thinking? Or do you enjoy just being paranoid?

Replying to @⁨defaultusername@lemmy.dbzer0.com⁩

I wouldn’t call it a shit show, they were first in E2E encrypted collaborative messaging platforms and get all the hits. Moderation turned out to be incompatible with E2E encryption. People kicked out of channels can still decrypt because keys revocation hasn’t been made.

Matrix server is a resource hog and a mess, and the protocol has never took off to spark alternative implementations.

Encryption doesn’t scale well for big channels.

They got many things right, but got crippled by many things they couldn’t possibly predict.