看UP主拍 vlog, 要么就是独臂杨过, 要么就是多人作战, 多请一个人拍 vlog 是有点怪的. 更极端点的直接上头上长单反的那个头盔.

有没有一种能把云台和运动相机架在肩上的单兵设备? 或者类似死亡搁浅里的那个BT探测头一样的背包式?

PS: 肩炮警告.

#asknostr how to I see what hashtags I’m following⁉️ I don’t believe I am but I may be mistaken… #nostr #grownostr #bitcoin

Let's build it here:

Gossip

Coracle

NoStrudel

Loure

Nozzle

Camelus

Snort / Iris

Lume

Others?

Did you write the lyrics?

The first 10 people to respond to this note with a nostr.build Account AI Studio generated image gets 2,100 sats.

The one with the most legitimate likes by EoD gets an extra 21,000 sats.

Be creative.

Go!

It’s super fast. So cool, thanks!

giftwraps without the spam issues? I think it makes sense to establish an approved channel before you should be able to send private notes to someone. Then you can start building a private network of friends without metadata leakage. This is very cool 👀 #privatenostr nostr:note1pwkvjh3ytef58wzmugqmrpc4s6870vtsw4cesh7nw5c57ma4f49scstjke

Yes, the client logs into the User's Private DM relays. Ideally, private DM relays auth and only send GiftWraps if the authed user is p-tagged.

The relay shouldn't know the alias to your key. You can auth with the alias key instead of the private key to download the GiftWraps to the alias key.

How can you do time based sync when you randomize the created_at ? Unless you pull everything with a 2 day granularity

It's the same spam we see on NIP-04. Anyone that just send tons of messages from random keys. The only difference is that relays can't do anything about GiftWraps. It must be resolved at the Client level.

Someone sent a bunch of GiftWraps to me a few months ago. Amethyst just ignored them all, deleted the event contents but kept the ids to avoid downloading them again.

We tested key aliases to hide the main pubkey of the user from the p-tag. You could give an alias to your friends and just download those messages instead. Something like a priority inbox. You can even rotate that key periodically to improve privacy.

Not yet. I need to go back and improve it. The feature is technically out there, but there is no way to create the private kind1 yet (and thus the visual is just very basic).

But I agree. It should be clear that this is a private note.

That's how I did it on Amethyst. Inner events are just regular notes with empty signatures. You can query them with regular filters. Becuase they are empty, even if there is a bug in the code and they end up being broadcasted, relays won't accept them.

Though if you have support for multiple accounts, you might want to make sure the decrypted conversations of one account are not mixed with another account.

I will, it's been under my radar for a while but haven't tested it yet

Nostr clients need to get serious about efficient bandwidth usage, specially on mobile. Caching as much as possible, only requesting new data, using the outbox model to minimize open WebSocket connections... Ideally built into SDKs or libraries like nostrdb so the average dev doesn't need to worry about it and efforts are not duplicated. This is no easy task and it takes a lot of careful engineering work but it's fundamental if we want the world to be able to use the protocol. It's easy to churn out new features or implement NIPs but building solid foundations is way more important.

We are working on this now, but need to use AI to tag and label everything. We have found the models to use, but need to update our DB and some other major components..

Testing Amber + Amethyst

🙇‍♂️