Good points. But there is a git issue list at https://github.com/zmeyer44/flockstr/issues . I opened an issue yesterday.
nostr:npub1zach44xjpc4yyhx6pgse2cj2pf98838kja03dv2e8ly8lfr094vqvm5dy5
just gonna put here so others can see whats needed as DMs get buried and there is nowhere to post these as git issues
I need a way to add events and either not be the host, or specify someone else as the host
I need to set more precision on the geocache
I need to know what spec is for the tags used when referencing images for events and calendar as its not in NIP52 and ideally you and coracle and other clients trying to support would establish and document that standard
Discussion
Thanks for posting what the repo is, since the site doesnt reveal.
The license on Flockstr is not FOSS, and hence I cant contribute to it.
Good point too. At least the nostr protocol is open, so are the events posted on Flockstr. So as posters we still own the data which can be re-used at other calendar clients, that makes it different compared to Meetup.com or so. Anyhow I also prefer to see a FOSS license for the client as well.
looks like the license is MIT: https://github.com/zmeyer44/flockstr/blob/main/LICENSE
As of earlier today 😂
Good Guy Zach