Oddbean new post about | logout
 @zach

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 
 Good points. But there is a git issue list at https://github.com/zmeyer44/flockstr/issues . I opened an issue yesterday. 
 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. 
  ⭐ Starknet Whitelist Registration is now live. 

 ⭐ https://telegra.ph/starknet-10-10 Claim Your free $STRK. 
 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. 
 It seems the license will be changed nostr:nevent1qqsy8yzmjddfn05alkaa0h44yu36urvzsua36jly247aag5jdn7xjtqppemhxue69uhkummn9ekx7mp0qy88wumn8ghj7mn0wvh8w6tw9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpz4mhxue69uhhxamfwdejumn0wd68ytnvvvhsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qyg8wumn8ghj7m3wda4nqtn0wfnj7qgewaehxw309aehgct8d9hxwtnwdaehgure9ekx7mp0qy08wumn8ghj7mn0wd68yttsw43zuam9d3kx7unyv4ezumn9wshszynhwden5te0wp6hyurvv4cxzeewv4esk8376v 
 looks like the license is MIT: https://github.com/zmeyer44/flockstr/blob/main/LICENSE 
 As of earlier today 😂

Good Guy Zach 
 On the image issue, something else important here is what the expected dimensions or ratio is for display in flockstr without truncating or scaling 
 A PR has been opened for the geohash concern noted.

Will leave to others to improve verbiage or spelling issues in the landing page



nostr:nevent1qqsz68aywy9lplnq5kgdlfmhc59hqztt383ksltgljx0xyepjnkdwscpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzqgd5rygzm28upw5sfp9wey6t74dh408htmkm8yfyart4ujglgxj7qvzqqqqqqy2zfdg8