@getkirby Your license is not open source. Have you considered revising this misleading heading on the "for developers" page of your site?
E.g. to "sustainable business model" instead of "sustainable open-source"
@convexer
- 15 Followers
- 27 Following
- 208 Posts
@soatok I read your rec of age for file encryption. Since age operates on individual files, I was curious your opinion of tools like Cryptomator and Nextcloud's E2EE app. These give a decrypted "view" (in Cryptomator's case, via FUSE; in Nextcloud's case, by encrypting in the sync process) of flat files stored in the cloud—way more ergonomic+efficient than encrypting a huge tarball with age. But both have lots of issues and few alternatives. Why? Is the problem harder than it seems?
Is there an #rss / #atom feed reader that lets you store your subscription and read/unread status in a flat file or sqlite database? I see all these #foss projects that claim to be a "self-hosted" feed reader software, but standing up an entire server is overkill for my needs. I just want to keep a file with my subscriptions in my Nextcloud and point a client to it. #linux #android #software
To be clear, I understand that you are allowed to ask for a license fee in exchange for GPL software. It's just that the only other software I can think of ballsy enough to actually do it is RedHat, which makes me nervous that the Cryptomator folks would attempt a similar rugpull down the line.
@thelinuxcast Have you any experience with Cryptomator? Seems to be a pretty slick GPL app for transparently encrypting cloud storage, but something squicks me out about how aggressively they push for donations ("licenses") especially with the mobile apps.
Things I like about Ubuntu: very well tested, ufw, snaps (show me a flatpak for nextcloud or pwsh and then we can talk)
Things I like about Fedora (and derivatives): more current, more love for KDE, better community
Sigh... another docker image that could have been a conda environment....
Lots of ppl are complaining about the GitHub "draft PR" feature, saying it's redundant with existing git functionality, etc.
Well, I think it's a great feature for precisely one reason: My boss *does not know* how to resolve merge conflicts, so the only way I can have multiple PRs going at once is to issue all of them as drafts and mark them, one at a time, as "ready to review," rebasing on main myself so that he has only to click the green button.
Man, #wordpress was one of those projects that had mass-market reach and really contributed to the democratization of the internet. A huge win for #opensource and case study in why it works. Isn't even the new york times website WP on the backend? And then they burn themselves to the ground like this.