It also has tons of stuff like management, moderation, 7 moderation kinds! All of this is not necessary in my proposal
NIP-29 is tied to specific relays? This is not a public chat spec. Its still threads
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.
This effectively enables a *market* of moderation for any community.
you can have moderated views of the community if you want, but that is up to the users choosing which moderated relays they want to use for that community.
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
Using nostr:npub18m76awca3y37hkvuneavuw6pjj4525fw90necxmadrvjg0sdy6qsngq955 on my iPhone SE on iOS 15.8.3
i don't think we support 15. that would be a really old version
I'm pro label/relationship status. probably more relationship status. labels seems a bit too generic ?
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.
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
Starting to write some ideas here:
Then basically the largest community for a given name would be the defacto “reddit community” for that identifier
I think the community name changing would be confusing, i think immutable is good for the community creation anchor. Description could be overridden with the addressable event, but name can’t change
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)
Someone please help me build this:
**Text-to-Speech reader app for Android**
**Instant Playback**: Integrates seamlessly into Android’s share menu, enabling one-tap access to convert text from any source (web, PDFs, EPUBs) into spoken audio. Opens shared text immediately, using the device’s **local TTS engine** (no cloud dependency, using Sherpa TTS) to read content aloud while dynamically highlighting words for visual tracking.
**Queue Management**: “*Share to Queue*” option lets users compile a playlist of text snippets, articles, or documents for continuous listening. Prioritize, reorder, or remove items, with playback resuming automatically between entries.
**Podcast-Style Background Export**: Convert text to MP3 in the background, saving files to a user-designated folder for later listening in a podcast app. Ideal for commutes or offline use.
**Lightweight & Private**: No subscriptions, ads, or data mining. Processes all text locally, ensuring speed and privacy.
This is similar to this non-free app: https://hyperionics.com/atVoice/
This would be great. Closest thing to this is speechify on iOS which I use a lot, but its very cloud based and paid
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

yeah his insights started hitting diminishing returns awhile ago
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
i imagine most c/c++ games just use sdl which handles this i would think
you can zap notes via https://zap.army
penis butter nostr:npub1jcjxjg92200kdp8guw8sysg8gr0ez29hahrfdy49h30hgnkpa4kqfvmtwx
shower girl
nostr:npub1el3mgvtdjpfntdkwq446pmprpdv85v6rs85zh7dq9gvy7tgx37xs2kl27r hellthreads
nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 nak posts
nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m posting weird shit
nostr:note12vkzjt6mscx9luyqxg6prtk4uafa82zz6f3zgr4jt26nu9w0n9ese5gzy0
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.
i have a Galaxy tab S9 which covers that I think. very nice tablet
best folding android phone? I want to test damus android to notedeck transformer
