The "upstream" atlassian agent got DMCA on their GitTea repo

[haxqer]

The "upstream" atlassian agent got DMCA on their GitTea repo

[haxqer]

I think Atlassian will focus on the cloud version, including many new plug-in functions that also support the cloud version.
Because in addition to the cloud version, other versions (server or data center) will be cracked even if the encryption algorithm is complex, so there is no need to waste energy on other versions of encryption algorithm.

There is no need to worry about this problem. Even if you worry about something, you can use the old version. The current version of Server Or Data Center is locally verified, and the old version is feasible. The functions of the old version are sufficient.

[voarsh2]

There is no need to worry about this problem. Even if you worry about something, you can use the old version. The current version of Server Or Data Center is locally verified, and the old version is feasible. The functions of the old version are sufficient.

I suppose - but I personally like up-to-date software, especially since some people won't just be running it localhost... I know Atlassian's focus is their damn cloud, and they purposefully withhold active feature development on Server/Data Center to entice Cloud.... here's hoping the original maintainer comes back in future - if the keygen breaks.... :D

Let's not forget that it was probably Atlassian that did the DMCA to the repo - and they could be after yours next :D

[haxqer]

Locally verified means no network authentication is required. I use the wrong words. It should be offline verification.
In addition to the cloud version, all others are offline verification.
As long as it is offline verification , it can always be cracked.

Considering the price of jira and confluence, including the price of plug-ins, the scope that DMCA can affect is actually small (except for large enterprises).