Subnostr

It's self-hosted nostdress, so I didn't think would be a problem. Are you aware of any other reason you shouldn't sign your own zap receipts??

Vitor Pamplona 2y ago

No idea why signing your own zap receipts could be bad :(

Replying to

fmar

It's self-hosted nostdress, so I didn't think would be a problem. Are you aware of any other reason you shouldn't sign your own zap receipts??

Vitor Pamplona 2y ago

See if it's fixed on the version released today 0.74.2

Vitor Pamplona 2y ago

### #Amethyst v0.74.2: Many changes, much wow

- Adds support for Stemstr's kind 1808

- Adds a waveform visual to audio playback when available

- Creates a Quartz Module for Nostr Events

- Creates a Benchmark Module to test Performance

- Migrates from GSon to Jackson for Performance gains, adapts all serializers accordingly

- Automatically activates NIP24 chats when users have received NIP24 messages from the counterparty

- Implements contextual rounded corners for images and videos

- Caches NIP-44 shared key for performance.

- Improves BechUtils encoding performance.

- Recreates Hex encoding/decoding classes for Performance.

- Migrates NIP24 to the new ByteArray concat encoding.

- Fixes Zap Notifications when the Zap payer is the logged-in user

- Fixes ThreadAssembler when there are two roots to a conversation branch

- Fixes the color of the historical chart to follow the chosen theme in settings

- Fixes chatroom names when clients send the same user twice in the p-tags.

- Removes support for lenient choices in the. events.

- Refactors TLV's, Events, and NIP-19 dependencies.

- Adds a large set of events as a test case for signature validation

- Adds new translations for cs/de/se by nostr:npub1e2yuky03caw4ke3zy68lg0fz3r4gkt94hx4fjmlelacyljgyk79svn3eef

- Fixes url regex pattern for URLs with a dash by nostr:npub1l60d6h2uvdwa9yq0r7r2suhgrnsadcst6nsx2j03xwhxhu2cjyascejxe5

- Fixes image uploading tests without an account

- Adds account info to image uploads test suites

- Moves navigation's top bar to use the Arrow Back UI Concept

- Trims display names when possible

- Don't display the username if the display name is available.

- Moves Relay List to a composable surface

- Migrates the use of pubkey prefixes in filters from 6 to 8 because more relays seem to work with this

- Adds read support for NIP-65

- Adds UI Improvements to the Settings Interface

- BugFix: Highlight event builder using the wrong kind

- BugFix: Avoids displaying a NIP-94 event without a url tag

- Updates SDK and dependencies to the latest

Download:

- [Play Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.74.2/amethyst-googleplay-universal-v0.74.2.apk)

- [F-Droid Edition](https://github.com/vitorpamplona/amethyst/releases/download/v0.74.2/amethyst-fdroid-universal-v0.74.2.apk)

Replying to

fmar

Ok finally I found out what was wrong. I'm using nostdress connected to my LND node to generate the invoices and publish the zap receipts (9735). And I was using my own private key to sign the receipts. I didn't pay attention to nostdress config doc which said to not use your own. I quickly checked nip-57 and didn't see anywhere mention to not use your own privKey to sign the receipt. Since Amethyst's NotificationFeedFilter has a filter condition to exclude events which author is the loggedInUser it explains the behaviour I was getting. After changing to a new generated privKey to sign the receipts everythingd seems to be working. Do you know the reason it shouldn't use its own privKey to sign the receipt?

Vitor Pamplona 2y ago

Ohhh that makes sense. I can fix that user check.

You should probably not use your main key for security reasons. They might not have everything in place to keep it safe.

Replying to

ben

🤔 …what if I make our relay replicate the 1808s everywhere by forwarding to blastr?

Vitor Pamplona 2y ago

Not as pretty as yours, but getting there.

Replying to

ben

🤔 …what if I make our relay replicate the 1808s everywhere by forwarding to blastr?

Vitor Pamplona 2y ago

Or just to the write relays of the author.

Replying to

Jingles

Na. They won’t.

Only people who care about NOSTR will build around and for NOSTR.

I care about NOSTR, thus I’m building.

and signing using Vault is currently half completed. nostr:note1ezy5m7p9q09ma9za6mx0z3tyydn4xsr34w9v9xrlt79f5ud2uj3saht6d4

Vitor Pamplona 2y ago

My point is that they will have to. :)

There is no ignoring Nostr.

Replying to

ben

you thinking like a download_hash tag or something?

our download_url values actually already include a hash - that’s how we identify files, by their content hash. but ultimately we want the media api to be user configurable so I think this makes sense.

Vitor Pamplona 2y ago

Or just an `x` tag with the hash as the NIP_94 does

Also, which relays do you have your content on? I can barely find it.

Replying to

ben

good call out. in the meantime here’s the spec we use

https://github.com/stemstr/sips/blob/main/01.md

Vitor Pamplona 2y ago

Any chance you can add a hash to every download file? I would love to show that the file hasn't changed since the author posted.

It doesn't work for m3u8, but for the download it definitely does.

Replying to

Marty Bent

How do we change user behavior when it comes to value for value content on the web outside of calls to action?

IMO this is the biggest hurdle monetizing digital content on the web faces right now, but once that hurdle is overcome it will be a massive unlock.

Vitor Pamplona 2y ago

Help us figure this out. How do we make this better for content creators? Where do we start?

Replying to

hodlbod

A question for fellow devs that I'm surprised I've not come across before: how do you encode a replaceable (not parameterized) event? As a naddr? What's the value of the identifier, an empty string?

Vitor Pamplona 2y ago

https://github.com/nostr-protocol/nips/issues/657

Replying to

Giraffe

1password has been hacked once already, why supporting them instead of any other (not already hacked) password manager?

Vitor Pamplona 2y ago

Feel free to support any other. I just don't know anyone actually coding it. So, I will support when I see it.

Replying to

Derek Ross

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk

what do you think?

Vitor Pamplona 2y ago

We have some of this in specific features. For instance, when users request a share link, it comes in on of these partner apps. But we could do more. It's usually a matter of finding good matches for the feature set in the other app.

Replying to

RealJohnDoe

I never have and never will use closed source proprietary software or hardware for security.

This is the main reason I could never own an iPhone. Or a hardware wallet with a so-called secure element for security.

They all have back doors. To this day iPhone claims they don't. But they have had one from day one lol..🤔

Vitor Pamplona 2y ago

I agree with you. But let's see if they will actually implement.

Replying to

RealJohnDoe

A closed source proprietary password manager is an absolute no go. Use keepass. Or one of its many many excellent open source cross-platform clients.

It's a thousand times more secure and more powerful than anything else out there. Just the facts..🔑

Vitor Pamplona 2y ago

You can use it if they don't build support to native Nostr signing. Let's see who will do it first.

Replying to

Derek Ross

Someone, people that are much smarter than Derek, should submit PRs to AuthPass, Bitwarden, Buttercup, Clipperz, KeePassXC, LessPass, Padloc, and Passbolt.

nostr:nevent1qqsv3z2dlqjs8ja7j3wadn83g4jzxe6ngpc6hzkznpl4lz56wx4wfgcppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj78slkrh

Vitor Pamplona 2y ago

Let's see who can beat them to it.

Replying to