Here’s an open letter to the Organic Maps Shareholders with the most info:
https://www.comaps.app/news/2025-04-16/1/

Which is referenced in the article here:
https://news.itsfoss.com/organic-maps-fork-comaps/

And discussed on the OpenSource community here:
https://lemmy.world/post/30461779

Basically some drama went down between the devs.

• Organic Maps has remained an LLC instead of transitioning to a Nonprofit.
  • The projects finances have not been made public (they’re not required as an LLC) and there are concerns about how that money is being used.
• There was a decision made to include Kayak affiliate links in the app: https://web.archive.org/web/20250602163403/https://github.com/organicmaps/organicmaps/pull/6523
• The current board only consists of 3 people: Roman (@rtsisyk), Viktor (@vng), and Alexander (@biodranik). Major decisions can’t be made if only 1 person objects.
• The code for their map download service was closed sourced when an MIT license was removed and there were concerns about Organic Maps keeping in line with its open source values: https://web.archive.org/web/20250523094656/https://github.com/orgs/organicmaps/discussions/9837#discussioncomment-11569196
  • When these concerns were raised, Alexander (@biodranik) revoked Roman’s (@rtsisyk) access https://web.archive.org/web/20250427142515/https://github.com/organicmaps/organicmaps/pull/9860
  • The situation was resolved about a week later with the code for the map download service becoming public and With Roman’s access being restored.

Edit: ‘to’ the shareholders, not from

Yeah, they definitely should focus on adding more RAM to their flagship phones, but smaller models are ideal for smartphones.

Smaller models are quicker to run and use up less battery. Besides, if they’re using some AI models I would rather it be run locally than have my data uploaded to some server somewhere (big assumption that they wouldn’t do that anyway, I know)… Or at the very least I can still run it even if the network goes down.

I had the same problem, but I found that turning up the advanced Parameter Values in the Text Prediction settings helps to keep everything spelled correctly. I’m currently at 10.4 for the transformer strength and 8.3 for the autocorrect threshold and I’m noticing a lot less issues… I haven’t tested out turning it up all the way yet.

I also have the Transformer fine tuning enabled.

The swipe feature definitely needs some attention.

They do have a crowdsourced way of helping to improve their swipe prediction, more info on the link here: https://swipe.futo.org/

You’ll notice that even the swipe prediction for Heliboard comes from a closed source library.

Futo has been my favorite so far compared to other keyboards. I haven’t used Heliboard yet, but it also looks like a good option.

Yes, there are NAS grade SSD’s that can be used.

As long as you use the right kind of SSD, there aren’t any problems with doing this.