Amethyst and Nostrudel are completely blind to the Community aspect tho.
Still totally building in the Follow / Individual profile perspective.
Yup, I'm building an (ugly) Community Everything App in Material/Dart now to have as a baseline for fixing my performance bottlenecks in Zapchat.
There will be choice!
There's like a dozen people that get this.
Most just keep putting themselves in a content type box, for no reason.
Nostr is the only thing that let's you put the Community central, not the content-type.
Test from jumble.
Please, don't make me lose hope 😅
No seeing any messages in Chachi tho.
Might be a relay (fetch and publish mistake). WIll check.
Just hatched an idea with nostr:npub1l5sga6xg72phsz5422ykujprejwud075ggrr3z2hwyrfgr7eylqstegx9z this morning.
TheForest relay has a pubkey now. Check it out: https://next-alexandria.gitcitadel.eu/events?id=npub1229y50ruvq9hjdxsjknh43gq4n9ef7h3h5hc4ezzrkg0q7kgg0tsv9a402
This is inspired by nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q's communikeys. If a user can have a NIP-05 address that verifies the npub and specifies that user's preferred relays, why can't a community do the same?
Your relay-based community can have a NIP-05 address that specifies which relays that community uses. We've got plans for this in #Alexandria, but other devs might find the idea useful as well.
Awesome!
Can see you in nostr:npub18stt78efprta2el02tzgnez6ehghzgtt000v58967wvkgezjmprs0n7h7u WIP 😍
I might join you on this, if you tell me how I can deal with the variable amounts.
I'd prefer EUR myself (and my frens and fam too, that's for certain). But fluctuating values is worse than introducing the :zap: (sat) concept
Next client???? :thinking:
Quickly pasting this link you asked for here since I have it open: https://wikistr.com/nip-communikey*a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be/nip-communikey*a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be
Hardest things in app building for me so far:
- Speed & performance
- WYSIWYG editors
I'll be overwriting the whole default color set I made with tints of the accent you select.
Easy. Is set up for it.
I just entered APK permission land for you haha. Learning, please wait...
Your profile color / hue is already green 💹
Noted :writinghand:
Add #forest colooooors
Yes: https://chachi.chat/c/660d8c78651f70487ec9b8ddc283e29cf2561693dda3ba246d3fd3c08dbb7083
And I'll send you a very first Zapchat APK to join that same exact #communikey later today or monday.
You android?
Tbh, I'm only switching my communities to my own servers once I have my Badges access controls built in Zapchat;
Yes: https://chachi.chat/c/660d8c78651f70487ec9b8ddc283e29cf2561693dda3ba246d3fd3c08dbb7083
And I'll send you a very first Zapchat APK to join that same exact #communikey later today or monday.
You android?
I need a typescript-dev-who-is-excited-about-communities collab 😉
nostr:npub1ye5ptcxfyyxl5vjvdjar2ua3f0hynkjzpx552mu5snj3qmx5pzjscpknpr nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl nostr:nprofile1qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hszrthwden5te0dehhxtnvdakqqgxxvqas78x0a339m8qgkaf7fam5atmarne8dy3rzfd4l4x6w2qpncu09muc
nostr:nprofile1qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hszrthwden5te0dehhxtnvdakqqgxxvqas78x0a339m8qgkaf7fam5atmarne8dy3rzfd4l4x6w2qpncu09muc bringing epic relay feeds in Nosotros. With Articles etc...
nostr:nprofile1qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hszrthwden5te0dehhxtnvdakqqgypyku3rmgwjnd7xqy2p0jgelju6rqtqkfrellez7h8ap76ssqgsv0shyat should watch out.
https://cdn.satellite.earth/9061ee4155885e046035ffb0f2dd548f60f0308a761e118c6ef4ab18be2c6d85.mov
Also, play this stuff out and what you end up with, will be something very close #communikeys.
Communities with:
- main + backup relays (and media servers)
- an identifier with agency (key)
- the content types they wok with, listed
- write and read access controls for each content type
Got that nostr:nprofile1qyvhwumn8ghj7am9d33k7mt99ehx7um5wgh8w6twv5hsz8thwden5te0dehhxarj9e3xjarrda5kuetj9eek7cmfv9kz7qpqpr28pamqhcfacyqudjrfyyfzhjwgz3xxfc85yjp42396he30ztlsmqnr8k community set up.
Time to start publishing some test APKs in it!
I need a really good (aka terrible) Nostr beta male / geek / nerd face in PNG.
For science.
nostr:npub1njst6azswskk5gp3ns8r6nr8nj0qg65acu8gaa2u9yz7yszjxs9s6k7fqx I'm looking at you.
Same :hugs:
I have a spec ready for #communikeys that lets holders of a Community-badge (confirmed by the communikey) hand out that same Badge to others. Those invited profiles, however, cannot hand out that Badge, until the communikey confirms the Badge for them.
I think an invite tree that only has one layer like that is the best middle way for good UX and feasibility on the App, Relay and Spec level.
https://wikistr.com/nip-badge*a9434ee165ed01b286becfc2771ef1705d3537d051b387288898cc00d5c885be
I edited my Community in Chachi and now I can find it!
Must have gotten lost Damus relay + chached in Chachi (so we could still see it there) somehow.
As long as you work with:
- rectangularly shaped nodes
- have some sensible max and min relative sizings for them
- know on which side the connections start and end
Your app can figure out a proper rendering for it.
I really think just copying these `from`and `to`tags from the JSONcanvas spec is enough and avoids having to interop on exact formatting syntax:
```
["fromSide", "top"|"bottom"|"left"|"right"]
["toSide", "top"|"bottom"|"left"|"right"]
["fromEnd", "none"|"arrow"]
["toEnd", "none"|"arrow"]
```
This :graph: Graph will be my first test event 😉
1) agents (which is the wrong hype/focus imo)
2) exactly the part I can learn most from, and a very similar approach to what we're doing with nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9.