carg

Well, I don’t know the specific case about CoMaps, but forking is a really hard decision, and you need to have strong backup from community to dare going that way. I would assume when projects decide to split is because all the attempts to arrive to a good decision failed. Driving a fork for success is a very hard task, and I guess the majority of forks that fail (a lot) are because they didn’t have support from community.

About libreoffice winning over m$ or g$ ? Well, I also would like to see that happening, but not to be replaced by another non-FOSS or half-FOSS option.

What you call drama is a healthy community fighting against violated principles. So, according to you, what’s the alternative? Just keep working with broken principles and never complain? Allow a bunch of greedy members to take over the project?

If you have paid attention, basically community always win: libreoffice vs openoffice, mariadb over mysql, jenkins over hudson, x.org over xfree86, ffmpeg over libav, nextcloud over owncloud, etc.

Right to fork is one of the most important to keep project in community hands and follow declared principles. Some forget that and are just doomed to repeat the history.

Disclaimer: I work on iDempiere who forked adempiere because of community disagreements, which also forked from compiere because of corporative takeout.

Long live to CoMaps!

if you cannot decrypt the file, how can you know that the DMCA violation report is valid?

it requires to create an account

Thanks for sharing.

I did some tests and opened two issues in your github project.

Who are you?

This sounds really aggressive, he’s tobi_tensei, that must be enough.

Even a known and respected cryptographer would not release a tool with such confidence

Why not? Do you know about open source? https://en.wikipedia.org/wiki/Release_early,_release_often

First you need to request testing and code review before you announce to people that it is a “secure, anonymous file-sharing platform.”

I think he’s precisely asking for testing and code review, announcing the intention of the software is not wrong.

This is not a community for sharing your personal programming projects for feedback

Why not? It is related to privacy, it can be the seed for bigger projects, the author is sharing the code so you can evaluate and host yourself.

What a strange way to say “thanks for sharing”.

So, I’m going to try to say it better:

Thanks @tobi_tensei for sharing that code in the open source, please don’t stop your initiative for people criticizing, there are more people that likes and are thankful.