Development is pretty rapid too. I didn’t track the features on the updates, but new versions were getting pushed regularly. No mobile app which was kind of a bummer, but the progressive web app integration was pretty good. It felt like a mobile app.

Edit: I forgot to mention the note sharing function, it shares a URL of the note that allows the recipient to view and edit the note through the URL. It was a little janky when compared with sharing a note between two users using themselves app, but it still worked pretty decently.

You might like Blinko. It seems similar to Keep to me. I set it up for awhile, but it didn’t give me anything beyond what I already have with Joplin, so couldn’t justify keeping it or transitioning to it. Here’s a video from DB Tech on the set up process: Self-host Blinko with docker

Awesome, thanks. I’m going to give it a try. It seems like the best FOSS find my device type service available by far.

I’ve been wanting to spin this up myself, but the fact that the Dev says his example docker-compose.yml is incomplete has stopped me in the past. Did you have to add anything to get it functional?

Not the OP, but I believe they’re talking about the upgrade from 128 bit AES to 256 bit AES. It created some compatibility issues between clients for a few days as the ones that weren’t updated yet couldn’t decrypt the newer 256 AES encrypted notes. That was my experience anyways. It’s a great app/server from my personal experience.

I like it 👏

I see what you did there 😏👏

Not the OP, but there was a time about a year ago (can’t remember if it was pre- or post- Daniel leaving the team lead role) where graphene was very vocal about how they felt that the Google play store security model was superior to that of F-Droid and Aurora. They poured massive amounts of development in to making it possible to use the play store directly in the OS through the sandboxed plag services. They expressed very clearly that they felt the only safe places to get apps was either directly from the developer or through the play store.

Graphene hasn’t been as vocal about this kind of stuff since Daniel stepped out of the limelight, and I did a quick search for the old twitter posts that covered the topic but couldn’t connect to them on twitter. That could just be because I don’t have a Twitter account and Elon is jacking up Twitter access these days.

I’ve been using GrapheneOS for about a year and I’ve never seen F-Droid bundled in their installer or app store. They’ve been vocally against F-Droid for quite some time. Other more FOSS focused projects bundle F-Droid.

If it’s only been a day, I might wait a bit longer before writing it off. The issue could very well be resolved soon. Even the big tech companies have a service go through problems for a day or two.

I only tested Notesnook for a few days, so I may not remember it’s key elements well, but Standard Notes seemed like a very similar product (the downside is the subscription, it was basically unusable to me without paying).

The NotesNook UI is the best I’ve seen, it’s hard to find that level of polish in a FOSS android app.

I think you’ll struggle to find what you’re looking for without a subscription model unfortunately. If you do want to retry Joplin that is my recommendation, I run it with a locally hosted Joplin sync server, it’s fantastic for my use case. It’s been recieving a lot of solid updates lately too.

My thoughts exactly

I’ve basically agreed with you this whole time, see my initial comment regarding the difference between the previous comtribution model and the new request for purchase:

Yeah, functionally it’s the same.

However we’re drawing different conclusions about the situation. You say it’s misleading and morally wrong to refer to “buying” this software, I say it isn’t and that it’s actually a helpful perceptual change in fostering support from their users.

I don’t really think there’s anything else to say beyond that. If you don’t like how Immich is handling their software, don’t use it.

Evidently there’s some difference to the approach. I’m not familiar with the WinRAR days, but they specifically address that in this video. I don’t know if it being similar to WinRAR is a good thing or bad thing in your book, but maybe you’ll enjoy the video.

https://www.youtube.com/watch?v=YdwG6SHeZEA

The technicality of usage rights is irrelevant, the developer is asking you to pay a set price that they’ve set as the total they would like to be reimbursed for providing the development service. That’s not a contribution, that’s a purchase. They’re generous people though, so they won’t restrict your use of the software if you choose not to pay.

Maybe you make donations to FOSS developers regularly. Unfortunately, I did not in the past. While I always intended to, it just slipped through the cracks. After running in to FUTO and the software they sponsor, I’ve been motivated to donate to or purchase much of the free software I’m using, and it’s entirely because of the way they approach their relationship with the user.

If you feel like that’s a dark pattern, or that your payment would only be purchasing an empty NFT, then I guess that’s your choice. But purchasing FOSS applications provides an incredibly important line of support to developers who stem the tide of surveillance capitalism and the digital abuse that big tech has filled our world with. Call it a donation, contribution or purchase price. In any case you are exchanging value for something that has made your life better and supporting the person who made that possible.

Maybe it would help to view the cost of Immich as purchasing a ethics NFT. Sure, you have no observable difference in the material world, but you as a person have affirmed your ethical values through reciprocal action with someone who shares those values 😉

Ownership is being conferred by purchasing immich, that’s what the product key codes they’ve started using indicate.

That is the fundamemental change in the way they are offering Immich: if you pay, you are provided with proof of ownership (product key). If you don’t, you are using it as a part of an indefinent trial period.

Why do you think you aren’t really buying it? Is it because they allow you to run it without paying money for it?

I don’t think the definition of “purchasing” software should be defined by whether you can run the service without paying or not. I think it’s best defined as paying money for something that you like and want to exchange value for. In my book that’s nothing near a dark pattern, as I can’t imagine anyone being confused by it, let alone mistakenly believing there is missing features that they won’t get until they buy.

I feel like there’s a pun semi-buried here…

Privacy is a marketing angle right now for sure. I hate seeing companies like apple advertise to the vague privacy concerns of the general public. Companies like Proton are also making money based on privacy concerns.

As far as I’ve seen, FUTO’s approach is to fund and support independent developers who have a high skill level and well thought out piece of software. They focus on software that is Open, or source available for auditing and viewing purposes, privacy respecting and free of any kind of advertising. They also are pushing for a new culture of payment to these developers that is not a donation to support, but a purchase to use. They don’t insist on the purchase though, you can use any piece of FUTO sponsored software free of charge indefinitely.

They do, but I don’t think that would apply to Immich. Immich is under the AGPL, and hasn’t taken on any FUTO licensing. In a QA they did awhile back they said there was no plans to change it as well, so should be AGPL for the long term.

As far as I’ve seen, the only connection that Immich has with FUTO is the $1M grant and continued development support. I would imagine any sales from these Immich server purchases are now obligated to go to FUTO, but that’s the only connection between the two companies.

I saw a lot of concern in the original github announcement regarding the use of the term “license.” People felt it gave the team a legal footing to paywall features down the road and offer them only to licensed users, along with a few other concerns based in the legal implication of the term license. That of course runs counter to their statement that no features will be paywalled ever, so I guess there’s still some anxiety over their trustworthiness out there. Understandable given some of the rug pulls that have happened in the open source world over the past year though (i.e Redhat, redis, etc…)