nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z not all the devs in the split for donating have working wallets it appears. Second time a payment has failed.
#fyi
Same
Had to zap individually
Which might not work with recurring zaps? maybe
I think of it as a library
Reporting is applying a label/category
Books in libraries are categorized
Ppl not interested in science will not visit the science section
That doesn't mean that categorizing books as science is censorship
Censorship would be if the library were forbidden from holding science books
It is up to nostr users how they treat reported content
Some nostr users report their own content for nudity or profanity
Some nostr users may *prefer* reported content -
it would be trivial to write nostr clients and relays that specialize in reported content
E.g. a nostr nsfw app
Web of Trust greatly mitigates false reports
And it's impossible for relays to effectively censor across the network
The most they are likely to do is scan content reported as illegal and remove if it is
This shows how much nostr devs have achieved in a short space of time
All of the features of X Premium+ are on nostr except for analytics, edit posts, and reply boosting (which is an anti-feature)
And nostr devs have built many features not available on X
And they have done most of this in under two years
That means the pace of nostr development is faster than X, which makes it the fastest developing social media ecosystem in existence
X Premium+ features available on nostr:
* encrypted DMs - NIP-04, NIP-17
* bookmark folders - NIP-51 sets (bookmarks, curations)
* highlights tab - DVMs
* long videos - nostr.build , flare.pub
* long posts - NIP-01 'short' text notes 😜
* get paid to post - NIP-57 zaps
* checkmark - NIP-05
* Grok - chat.plebai.com and DVMs with more use cases
* creator subscriptions - creatr.nostr.wine , highlighter.com
* articles - NIP-23 long-form content
* media studio - nostr.build
* no adverts - yup
X Premium+ features not available on nostr:
* edit posts - no, but can delete
* analytics
* boost your replies above the poors - no thanks
Some Nostr features not available on X Premium+
* music publishing & streaming - zap.stream , wavlake.com , wavman.app , stemstr.app , tunestr.io
* selling & marketplaces - NIP-15 plebeian.market , shopstr.store , some notes clients e.g. Amethyst
* DVMs for transcription, image generation, discovery and more - vendata.io , tasktiger.io , next.nostrudel.ninja , Amethyst, any client that supports DMs and zaps
* careers - ostrich.work
* Google maps - go.yondar.me , wherostr.social
* chat - 0xchat.com , blowater.app
* events - flockstr.com
* Web of Trust
* user choice in moderation systems, or no moderation
And the killer feature
* actual freedom of speech
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z slight issue configuring relays for filter.nostr.wine
The relay is pay-to-read and pay-to-write and it broadcasts notes to public free-to-read relays
If I put it in Home which is outbox (I think) then others will try to read from it
So another section, home-but-not-outbox?
Wondering if NIP-65 needs more flexibility
I haven't thought this through much but
This could make NIP-65 more useful as a global relay configuration standard that could configure proxy and aggregating relays with support for the inbox/outbox model
Disambiguate read/write values in kind 10002 relay tags:
aread - author reads from this relay
awrite - author writes to this relay
oread - others read from this relay (outbox)
owrite - others write to this relay (inbox)
So if I have a relay filter.nostr.wine that aggregates from nos.lol and relay.nostr.band and doesn't allow direct writes from unauthorized users, kind 10002 relays would be
nos.lol
owrite
relay.nostr.band
owrite
filter.nostr.wine
aread
If I also use filter.nostr.wine as a proxy relay that broadcasts to nos.lol and offchain.pub:
nos.lol
oread
owrite
relay.nostr.band
owrite
offchain.pub
oread
filter.nostr.wine
aread
awrite
And if as well as reading and writing to filter.nostr.wine I read and write to relay.damus.io in a standard inbox/outbox way:
relay.damus.io
aread
awrite
oread
owrite
nos.lol
oread
owrite
relay.nostr.band
owrite
offchain.pub
oread
filter.nostr.wine
aread
awrite
This way there's no need to put things which are by nature global configuration into client-specific settings
From a UX pov the configuration for each relay is relatively easy: do I read from this? do I write to this? do I want others to read from this? do I want others to write to this?
I feel the current NIP-65 overloading of read/write values with different author/other client behavior will create more problems
And I don't agree with the nudging of clients away from using NIP-65 for global configuration beyond inbox/outbox model:
"kind:10002 events should primarily be used to advertise the user's preferred relays to others. A user's own client may use other heuristics for selecting relays for fetching data."
Nostr is a constellation of compatible apps, it's helpful for the user that everything that is by nature global configuration is supported
nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn dunno is that nonsense?
X taking "freedom is not free" literally
nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn is there a way to configure relays in Coracle to work with both NIP-65 inbox/outbox *and* paid relays?
So for nostr.wine which is free-to-read & pay-to-write I have
*But* I also want to read from nostr.wine
If I enable read others will try to write to it as my inbox (I think)
Similarly for filter.nostr.wine which is pay-to-read and pay-to-write, I don't want others to treat it as my inbox/outbox
Nostrudel & Amethyst work around this with app-specific relay settings
Tbf because NIP-65 ventures into this territory...
"When broadcasting an event, Clients SHOULD:
Broadcast the event to the WRITE relays of the author"
I think perhaps it needs more flexibility to cover client configuration with paid relays
So relays defined in kind 10002 could have separate read and write values for the author vs all others
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z slight issue configuring relays for filter.nostr.wine
The relay is pay-to-read and pay-to-write and it broadcasts notes to public free-to-read relays
If I put it in Home which is outbox (I think) then others will try to read from it
So another section, home-but-not-outbox?
Wondering if NIP-65 needs more flexibility
nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn is there a way to configure relays in Coracle to work with both NIP-65 inbox/outbox *and* paid relays?
So for nostr.wine which is free-to-read & pay-to-write I have
*But* I also want to read from nostr.wine
If I enable read others will try to write to it as my inbox (I think)
Similarly for filter.nostr.wine which is pay-to-read and pay-to-write, I don't want others to treat it as my inbox/outbox
Nostrudel & Amethyst work around this with app-specific relay settings
Tbf because NIP-65 ventures into this territory...
"When broadcasting an event, Clients SHOULD:
Broadcast the event to the WRITE relays of the author"
I think perhaps it needs more flexibility to cover client configuration with paid relays
So relays defined in kind 10002 could have separate read and write values for the author vs all others
Brill thanks Mazin 🙏
Removed broadcast=true
Search, feeds, DMs, notifications all working and fast 💜
Hey nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub18kzz4lkdtc5n729kvfunxuz287uvu9f64ywhjz43ra482t2y5sks0mx5sz nostr:npub1qlkwmzmrhzpuak7c2g9akvcrh7wzkd7zc7fpefw9najwpau662nqealf5y could you suggest how to setup nostr.wine and filter.nostr.wine with Amethyst please? Not sure this is correct ...
The Android ecosystem is becoming awesome
Installed Amber and Citrine by nostr:npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 via zap.store (or Obtainium)
Now I have a local nostr signer and a local nostr relay
Signed into Amethyst using Amber
Added Citrine to Amethysts lists of local and private relays
Now my crappy half finished and libellous thoughts (note drafts) are private as they should be
Lol this is awful
Adobe gives themselves a worldwide license to publish and create derivative works from 'your' content
And sublicense those derivative works
With no constraints
They try to justify this with a service provision use case
Which absolutely does not need an unrestrictive license
Ok this is weird
I was having the same issue
And I have home and inbox relays setup (Amethyst put all my relays into those by default)
So I published a new list on listr and now *all* my lists are showing in Amethyst
nostr:npub1wujmwnq0we8qs44fhxsducavekk3r2y3ln3kplhstk99n4spaqpqpzamjm maybe try that
Not true
Both takeaway points of the article associating fiatjaf with Olavo de Carvalho are publicly available under the fiatjaf pseudonym
* the links to Carvalho's website are on https://fiatjaf.com/
* the attendance of Carvalho's philosophy course is on https://github.com/fiatjaf/life/blob/gh-pages/life.md
There is no justfication at all for doxing him
And revealing someone's name and place of work is considered doxing under standard definitions
"Doxing or doxxing is the act of publicly providing personally identifiable information"
https://en.m.wikipedia.org/wiki/Doxing
"any information about an individual maintained by an agency, including (1) any information that can be used to distinguish or trace an individual's identity, such as name, social security number, date and place of birth, mother's maiden name, or biometric records; and (2) any other information that is linked or linkable to an individual, such as medical, educational, financial, and employment information"
Hmmm I disagree.
People who pay are funding the development of Damus.
People who do not pay are getting the results of that development for free.
Everyone is benefitting.
So I think the arrangement is fair.
Twitter is different & I agree that Twitter is a caste system and an abomination. Twitter boosts visibility based on how much ppl pay. So if you can't afford to pay your voice is worth less. Awful.
Nostr development needs to be sustainable as a business. Aside from donations and merch sales that leaves advertizing and subscriptions. Each has it's pros and cons.