I don’t want to be forever young, but I’d love to feel like I’m in my 20s until I’m 100.
I don’t want to be forever young, but I’d love to feel like I’m in my 20s until I’m 100.
Of the changes made last week to the license, this one stands out:
- None of the Work may be used in any form as part, or whole, of an integration, plugin or app that integrates with Atlassian’s Confluence or Jira products.
That is a weird carve-out, so I’d guess the license revision (and technically the reason it’s no longer open source) somehow has to do with Atlassian or their plugin marketplace?
Feel like the (totally impractical) fediverse end-game would be for each individual to have their own activitypub service, and federation happening on a person-by-person basis. So you retain some control over anything you publish, and your history is yours to keep.
As others have said, changing UPS batteries is required maintenance, and I agree 18-24 months is the typical service life for even high-end UPSs. However, you may want to look into LiFePO4 based UPSs, which can handle many more charge-discharge cycles and often have 5-year warranties. More expensive and potentially not as recyclable as lead acid batteries, but maybe appropriate for your use case.
This is a good, short read. For those who are unfamiliar with the AGPL license that the author proposes we all start using, the main difference (and I am not a lawyer) is that under the AGPL, the source code including any modifications must also be made available to all users interacting with the software over a network. This prevents companies from making proprietary versions of AGPL software that are only accessible as a web service, which is one of the big ways that corporations are able to profit from GPL source code contributions these days.
he aged