Avatar
jb55
32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245
I made damus, npubs, and zaps ⚡️ Independent bitcoin core and lightning dev.

It also has tons of stuff like management, moderation, 7 moderation kinds! All of this is not necessary in my proposal

Without losing the network effects of the community via forking. Forking naturally emerges as an evolving relay set for that community. The creator of the community can’t do much to change it.

My nostr community idea:

- can only post in one community at a time.

- separate follow list for communities you’ve joined (relationship statuses ideally)

- communities have a name, banner, and description and can only be created once (name is immutable, non addressable). communities therefore have a specific sha2 ID which is the unchanging identifier for the community.

- non-addressable sha2 id over d-tag name anchor, otherwise it's not clear which "bitcoin" community you are referring to.

- size of community is counted by number of people who have that community id on their community follow list.

- community posts have a distinct design (shows the community name on top of the post in your timeline like in X)

- community can have addressable data associated with it via the creator or frost creators (sidebar info like on reddit)

- Since threads could be quite large, we should use [NIP-22 Comments](https://github.com/nostr-protocol/nips/blob/master/22.md), this would allow us to pull large root threads first (if building a reddit-style design)

- outbox: community author can create a preferred relay list for the community, or it can be more amorphous and exist everywhere

- cross sections of the community can be moderated if viewed from the perspective of moderated relays that host content from that community

- the community name changing would be confusing, immutable is good for the community creation anchor.

- description could be overridden with the addressable metadata event, but name can’t change

- there could be forked or hidden parts of the community on unofficial relays. these are just different views of the community associated with the sha2 id of the community.

- they have much better network effects as well and can exist for long periods of time as they can exist on any or all relays

- community members can publish relay lists and they can fight over which views of the network are the "official" ones, effectively forking the community without needing to change the root identifier

- the largest community for a given name would be the defacto “reddit community” for that identifier

Feel free to add questions and I'll add them to my notes here:

https://github.com/damus-io/notedeck/issues/788

nostr:note1euh6hp3ww2udhel4nxzzvv83tpgnzsfk7m8v7azhavgh05xntfrs2ur3ra

i don't think we support 15. that would be a really old version

specifically:

- cross sections of the community can be moderated if viewed from the perspective of moderated relays that host content from that community

- in this model noone can stop you from posting to a community. the community would exist as notes spread across different relays. there could be a canonical relay list associated with the community, but there could be forked or hidden parts of the community on unofficial relays. these are just different views of the community associated with the sha2 id of the community.

Replying to Avatar elsat

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s Nackoo’s frame of reference is a admin/moderated telegram community with channels.

Non-moderated generally means no admin.

However, if you are running a relay on which the community operates there is an admin capability (i.e. can whitelist, blacklist etc).

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s does your spec envision a community that can be run solely on one relay, or multiple relays?

this is all covered in https://github.com/damus-io/notedeck/issues/788 so far

There is no singular definition of a community on nostr. I am proposing one of many alternatives.

in this model noone can stop you from posting to a community. the community would exist as notes spread across different relays.

there could be a canonical relay list associated with the community, but there could be forked or hidden parts of the community on unofficial relays. these are just different views of the community associated with the sha2 id of the community.

i wanted it to have a persistent sha2 id though, otherwise it's not clear which "bitcoin" community you are referring to

cross sections of the community can be moderated if viewed from the perspective of moderated relays that host content from that community

there is a moderated communities spec, it's an alternative to that

writing my ideas here:

nostr:note1fuyhcze0pqgxkj6wy84h9scexretmthhurrufpmn05jnyadzp3tqm87kca

gonna build something first before I NIP it

there are a bunch of important differences:

- can only post in one community at a time.

- separate follow list for communities you’ve joined

- communities have a name, banner, and description and can only be created once (name is immutable, non addressable)

- size of community is counted by number of people who have that community id on their community follow list.

- community posts have a distinct design (shows the community name on top like in X)

- community can have addressable data associated with it via the creator or frost creators (sidebar info like on reddit)

```

type: crash

osVersion: google/oriole/oriole:15/BP1A.250305.019/2025031400:user/release-keys

package: com.damus.app:16777985, targetSdk 30

process: com.damus.app

processUptime: 69 + 250 ms

java.lang.UnsatisfiedLinkError: Unable to load native library "/data/app/~~0xeKoL3f2a1xIapBuXrORg==/com.damus.app-4Siu4C8dujaJ6Kg94tiNWw==/lib/arm64/libnotedeck_chrome.so": undefined symbol: ANativeActivity_onCreate

at android.app.NativeActivity.onCreate(NativeActivity.java:178)

at android.app.Activity.performCreate(Activity.java:9132)

at android.app.Activity.performCreate(Activity.java:9110)

at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1541)

at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:4201)

at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:4406)

at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:222)

at android.app.servertransaction.TransactionExecutor.executeNonLifecycleItem(TransactionExecutor.java:133)

at android.app.servertransaction.TransactionExecutor.executeTransactionItems(TransactionExecutor.java:103)

at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:80)

at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2782)

at android.os.Handler.dispatchMessage(Handler.java:109)

at android.os.Looper.loopOnce(Looper.java:232)

at android.os.Looper.loop(Looper.java:317)

at android.app.ActivityThread.main(ActivityThread.java:8973)

at java.lang.reflect.Method.invoke(Native Method)

at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:591)

at com.android.internal.os.ExecInit.main(ExecInit.java:50)

at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)

at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:369)

```

What commit you on? It should not be using native activity

Right now i navigate within the column, but you’re right maybe in a two column setup an action on the left should open in the right

This is hilarious

I couldn't go into any restaurant, take *any plane*, even to another province to visit my family for christmas. this also means I couldn't leave BC at all for the most part, since the US border was also closed.

friends, family, and everyone was calling me a plague rat even though I got covid and was immune and didn't need the shot. wasn't sick for like 2 years after I got covid. they tried to gaslight me into "natural immunity is not enough, you need 10 boosters, you're just an ignorant hick". fuck that.

I'm supposed to just be ok with that... yeah never.

why don't we just make "damus gems" the thing you buy from an in-app purchase. it would just be a signed nostr note from our node with a unique ID. like a lightning IOU. we wouldn't need the full complexity of an ecash node. it would be a small plugin on my core-lightning node.

the iou would have the purchase amount in fiat. you can't really do much with these except melt into your lightning wallet once you set one up. this melting would be a payment from our node to another lightning node (the users wallet). then we would mark the gem as redeemed

I wonder if this would basically allow us to get our zap button back on ios in a sneaky way ?

also since its denominated in fiat we don't have any risk in terms of price swings, and users can't use them as call options lol

this is probably the cleanest way I can think of integrating with the ios appstore without doing kyc nonsense

nazis everywhere

i imagine most c/c++ games just use sdl which handles this i would think

I think it was more the airpods. my favourite apple device of all time.

like being able to quickly jump the bluetooth connection between phone/tv/macbook. They hacked bluetooth or something because it will automagically switch over depending on which device I’m actively using. Android plebs have no idea how awesome this is.

best folding android phone? I want to test damus android to notedeck transformer