Does the F-Droid fork have an app store version? Author did say they used an iPhone.

Since F-Droid is an Android store, it most likely doesn't even exist for iOS.

But that's kinda the price you pay there.

No, and they won't because it's against Apple's terms of service to license your app as GPL.

Even if this were true, it's irrelevant since Maps.me isn't GPL software to begin with.

It is true, take it from the FSF themselves [0]. Or the VLC devs [1]. However, you're right that Maps.me is not GPL; I misread the question as asking about F-Droid itself which is GPL.

[0]: https://www.fsf.org/blogs/licensing/more-about-the-app-store...

[1]: https://www.zdnet.com/article/no-gpl-apps-for-apples-app-sto...

The way that this comment implies a carelessness about the way I operate is more than a little annoying, especially in light of the clear-cut carelessness of your original comment.

> take it from the FSF themselves

Is that supposed to be a trump card? I've read that FSF document. I read it when it was published in 2010, and because I'm not careless I read it again this morning before and after I posted my comment. I've also looked at it more than once in the intervening years.

> Or the VLC devs

VLC is on the App Store right now.

The FSF post was true in 2010, but unlike GPLv2, v3, etc, the Apple terms are not static documents. They've been revised multiple times in the last 10 years, and the FSF post hasn't been updated. The last time I spent an afternoon doing an analysis, I found that the terms at the time didn't conflict with GPL. At this point, if a person is going to claim that there's a conflict, the onus is on them to show that it's true—just like the FSF did at the time they published that blog post. It doesn't suffice to show that it was true in 2010. But again none of this matters here, because Maps.me isn't GPL software, so this entire diversion has been a waste of time.

Given the cost & overhead of distributing via Apple, I can't imagine there'd be much incentive for this.

Could you expand on this please? What costs apart from the $100 or so dev license?

$100 is not insignificant.

On top of that there's the cost of Apple hardware; you can get away with not having an iPhone and using xcode's emulation for many cases but with custom graphics heavy things like omim had, this approach would be limiting. And you still need a Mac either way.

And all this is to create an app that's competing directly with an almost identical app on the same store with only marginal benefits (the Android one in contrast has the benefit of being available outside the Google ecosystem, as well as having some exclusivity within F-Droid itself).

It would be a not insurmountable but still significant extra amount of maintenance effort. Given the maintenance effort was already seemingly unmanageable supporting Android alone it's understandable.

As far as I know, you actually need a Mac or other Apple computer to push something to the Appstore and even then it's not a fun process.

This knowledge is second hand from a friend of mine, whom I had the pleasure of listening to when he was ranting about the process a few years ago.

Maybe things have changed since then..?

I did not experience any inconvenience with putting apps into the iOS AppStore. Rather, I found the process quite easy and my apps got approved faster than expected (within one day).

Did you already have a Mac? Because that seems like a significant part of the process if it is stil necessary.

I̶t̶ ̶l̶o̶o̶k̶s̶ ̶l̶i̶k̶e̶ ̶t̶h̶e̶ ̶F̶-̶D̶r̶o̶i̶d̶ ̶f̶o̶r̶k̶ ̶w̶a̶s̶ ̶l̶a̶s̶t̶ ̶u̶p̶d̶a̶t̶e̶d̶ ̶f̶i̶v̶e̶ ̶y̶e̶a̶r̶s̶ ̶a̶g̶o̶,̶ ̶a̶n̶d̶ ̶t̶h̶e̶ ̶'̶w̶e̶b̶s̶i̶t̶e̶'̶ ̶l̶i̶n̶k̶ ̶j̶u̶s̶t̶ ̶p̶o̶i̶n̶t̶s̶ ̶t̶o̶ ̶m̶a̶p̶s̶.̶m̶e̶,̶ ̶r̶a̶t̶h̶e̶r̶ ̶t̶h̶a̶n̶ ̶a̶ ̶p̶u̶b̶l̶i̶c̶ ̶r̶e̶p̶o̶s̶i̶t̶o̶r̶y̶ ̶o̶r̶ ̶a̶n̶y̶t̶h̶i̶n̶g̶ ̶s̶p̶e̶c̶i̶f̶i̶c̶ ̶t̶o̶ ̶t̶h̶e̶ ̶f̶o̶r̶k̶.

̶G̶i̶v̶e̶n̶ ̶t̶h̶a̶t̶,̶ ̶I̶ ̶c̶a̶n̶ ̶s̶e̶e̶ ̶w̶h̶y̶ ̶t̶h̶e̶ ̶a̶u̶t̶h̶o̶r̶ ̶w̶o̶u̶l̶d̶ ̶c̶o̶n̶s̶i̶d̶e̶r̶ ̶i̶t̶ ̶a̶ ̶d̶e̶a̶d̶/̶a̶b̶a̶n̶d̶o̶n̶e̶d̶ ̶p̶r̶o̶j̶e̶c̶t̶,̶ ̶a̶n̶d̶ ̶s̶e̶e̶ ̶n̶o̶ ̶r̶e̶a̶s̶o̶n̶ ̶t̶o̶ ̶p̶i̶c̶k̶ ̶i̶t̶ ̶u̶p̶ ̶i̶n̶s̶t̶e̶a̶d̶ ̶o̶f̶ ̶s̶t̶a̶r̶t̶i̶n̶g̶ ̶f̶r̶o̶m̶ ̶t̶h̶e̶ ̶m̶o̶s̶t̶ ̶r̶e̶c̶e̶n̶t̶ ̶M̶a̶p̶s̶.̶m̶e̶ ̶p̶u̶b̶l̶i̶c̶ ̶r̶e̶l̶e̶a̶s̶e̶.̶

EDIT: Disregard, I was confusing the actual F-Droid fork with an older re-upload on the same store. The former is called "Maps" while the re-upload is "Maps.me".

Maybe you're looking at the wrong place?

> It looks like the F-Droid fork was last updated five years ago

The latest release is August 2020 [0] and the latest update to the repo happened at the same time [1].

> and the 'website' link just points to maps.me, rather than a public repository or anything specific to the fork.

There's a "Source Code" link [0] which points to the Gitlab repo [1]. I don't even see a "website" link.

[0]: https://f-droid.org/en/packages/com.github.axet.maps/

[1]: https://gitlab.com/axet/omim/tree/HEAD

> Maybe you're looking at the wrong place?

I was, thanks! There's a "Maps.me" app on F-Droid that's the one I described (presumably the same APK as the Play Store?). Whereas the fork you guys are talking about is just "Maps". Editing my comment.

Sorry for meta, but what's the hn markdown for strikethrough?

Looks like the parent ran his comment through a strikethrough character generator; I don't believe HN supports it natively.

You are correct.

Wish HN would document such things, feels a bit gate-keeper-y but I doubt intentional.

Not sure what you're looking at, the last commit to the fork is August 2020.

The author of that fork has also been actively engaged with the maps.me devs throughout its development, you can see a lot of these discussions in the issues on the original github mapsme omim project.

You originally posted as lucideer then instead of editing that you posted as piaste.

It looks like there are more of us than there are, possibly.

No, we're different users. Out of curiosity, why did you think otherwise?

I should have mentioned it. There's now a mention at the end of the post:

I'm aware that one fork already exists, but it hasn't seen any updates for a year and the app doesn't seem to work at this time. The plan is to eventually integrate axel's work back into the app.

It was updated 4 months ago, it's actively maintained and I use it frequently. Someone else was looking at the wrong listing and you may have done the same thing. The correct listing is simply called "Maps"

F-Droid: https://f-droid.org/en/packages/com.github.axet.maps/

Gitlab: https://gitlab.com/axet/omim/tree/HEAD

When looking at the commit history on github of axet project, the most recent commit is only 4 months old. That comment about it not seeing updates since years looks wrong.