nostrify hitchmap?

[guaka]

(relates to #64)

just putting this out here, feel free to close the issue

nostrify:

• log in with nostr keys (still not obvious on iOS now afaik)
• if spots are nostr notes, they could be created and/or consumed by other apps, e.g. a nostrified hitchlog, notes.trustroots.org
• if #hitchhiking becomes a tag it would also be possible to use the application for other trustroots circles
• future: additionally suggest adding tags like e.g. #lookingforhost #lookingforride, and announce to nearby hosts or drivers https://github.com/Trustroots/nostroots/issues/19

[bopjesvla]

We currently don't have any auth whatsoever. As long as we don't get spam I don't think user accounts are worth it. Even if we do get spam, iOS support would be necessary.

Out of curiosity, how do nostr clients handle private keys on Android? In general, private keys should not be on phones, right?

[guaka]

re keys: I'm no expert here. But various types of private keys are in all kinds of places, definitely also in phones. Phones can actually be better than laptops because they have secure enclaves.

I have some experience with using https://addons.mozilla.org/en-US/firefox/addon/nos2x-fox/ This extension is storing your nsec, and can sign and do other things that a specific website requests. I am assuming it's very similar with the Android app. And I'm confident enough that someone will find a way to do something like this on iOS.

People have been losing nsecs and this hasn't been a big deal so far. As nostr progresses it will become a bigger deal, but I also expect good ways to handle this will be figured out. For now I think we can tell people the npub is like a username and the nsec is like a password that you have to store really well (because there's no password reset!), ideally in password manager.

Since there is no auth or user names in hitchmap now it could simply be an additional feature, where a user that wants to can (verifiably) claim to have a specific identity (npub). This can also include a claim of being specific user on Trustroots as soon as we have nip-05 there https://github.com/Trustroots/trustroots/issues/2692

[guaka]

Various thoughts, slightly based on experience writing https://github.com/guaka/nostrhitch

Spots would probably be various notes tied together

• a hitchhiker can post that they are looking for a ride to a specific location, this could then be showing at rideshares.org for some time (until the hitchhiker found a ride)
• when the hitchhiker found a ride they can comment on this node that they found a ride
• when they get to their destination they can add more notes
• other hitchhikers can post notes that are also linked to this specific spot if they are hitching from the same spot

Drivers:

• a driver can post an ephemeral note on https://rideshares.org, that they are going from a location to another location and that they are happy to pick up riders, these notes can also (temporarily) show at hitchmap.com

iframe/embed hitchmap.com:

• at hitchwiki.org with a mediawiki extension, reusing all the tags
• at https://www.trustroots.org/circles/hitchhikers

There was someone who asked about a hitchmap.com api but then didn't really say what they were building, I pointed out that by going the nostr way there's no need for an api, @tillwenke agreed.

There are probably 100s if not 1000s of local/national/continental rideshare groups on telegram and facebook, but IMHO they all suck for providing and getting rides. And then there's blabla and other commercial platforms, but I didn't like using them (compared to the hitchhiking experience), neither as a driver nor as a rider. It should be doable to build something that is easier to use than chat groups. It's harder to get enough people to use it, but I think we have a chance by pushing it thru hitchwiki, hitchmap and trustroots. (Obviously I believe the rideshare experience is better when there's no money changing hands.)