Nostr Web Client

It’s just a binary encoding of the image. You should be able to reconstitute it manually with a command like this on Mac or Linux to see what it is:

base64 -D > image.webp

Derek Ross 1y ago

Oh. Well that makes sense. Any would would we want base64 images? What's the use case? To upload images to relays as base64 blobs?

Yea storing images directly on relays. I personally would block this on my relay. Or drastically limit the size of the data. I don’t want to serve images.

Feel free to block it. Just be sure to tell your users that you are doing so. People are free to move to other relays when they see missing data.

Only paid relays are required to report such things, while free ones operate as-is and are not obligated to do anything.

No one is obligated to do anything. But if they want to build a health relationship with their users, they better do. There is nothing worse then figuring out the relay you like is misleading you with hidden policies, regardless if its free or paid.

Healthy relationships mean not embedding base64 blobs into text notes. Users do not notify some relay owner that they will do this, so he may not notify them either. We don't have a system of contracts and obligations here.

Correct. But users can still hate you if you are hiding posts form them. This has happened many times in Nostr in the past and it is never good for the reputation of the relay operator.

All relay implementations have event kind filtering, and max event sizes with reasonable defaults, 65k for strfry or 128k nostr-rs for example. Those are there to stop misuses just such as this. If this data gets truncated or rejected because you're (IMO irresponsibly) shoving data into a kind 1.... That's not on me.

I don't see how this experience isn't janky in the best case for users.

Error messages are enough. If the user doesn't read them, well... 🙄

Error messages are not hidden. Many of these policies are never communicated, not even in error messages. That's when people get angry and the operator's reputation goes to the trash.

Derek Ross 1y ago

Communication goes a LONG way towards user experience. If you're running a service, tell your users what they can and can't do. Relying on non technical people to figure out what they're able to do is a bad user experience. Nostr benefits as a whole when users have better experiences.

I have a lot of respect for you and what you’ve done for Nostr, and I also don’t need your permission to do whatever I want on my relay. So don’t tell me what to do.

Sure. People are free to shoot their own foot by hiding things from their own users. I couldn't care less.

kojira 1y ago

これになりました

👁️ 1y ago

A Pikachu, but it doesn't appear in the album on the homepage.

are you trying to put relays out of business?

If this will take them out of business, they are already dead.

you know what i'm asking, why send all the image data, esp. in a protocol that basically requires duplication

It's the user's choice. They can add a link or add the image itself. It's not for me to decide.

i think its kinda irresponsible to do it under kind 1

If it is then people will reach the same conclusion that you did and stop using the feature. In the end, it's their choice.

Users themselves do even worse things in kind 1. In any case, the relay can effectively reject or filter it. I don't see a problem with this.

apps enable users

Liberty Farmer 1y ago

aww, what a cute lil pokemon. or whatever.

calle 1y ago

I see something when I squeeze my eyes

frphank 1y ago

Looking good after latest update from Obtainium.

But why though

If people are using them, we will render. The why is the user's problem. If they think it is bad, they should not use it. If they think there is a reason to use it, it's available.

b64 images violates the "human readable" principle. I don't think rendering them is the right approach.

By that standard, every long link violates the principle, including nprofile and nevent links, cashu tokens and ln invoices/withdraws

Yes, but there are two differences:

- Those entities are often provided by the user directly, and are therefore meaningful to users. Clients are imitating natural end-user actions by generating them.

- Entities are references (links, npubs), or content that has no reference (cashu tokens, invoices). b64 images are content that can otherwise be included by reference.

In other words, I've never seen a user paste a base64 encoded image into a note instead of uploading it to a host and referencing it.

Every content can be included by reference. I don't need to type the message, I can just add a link to where the text message is in my server and sign that.

You can search for base64 images on NIP-50 relays. There are 1000s of posts with images before our release went out and those were breaking Amethyst's UX. So, it's a no brainer for me.

VictorieeMan 1y ago

The user void has spoken

So if I start publishing notes from Coracle in rot13'd LaTeX you'll render that too?

if people use it, I would be forced to support it.

https://github.com/vitorpamplona/amethyst/issues/951

Ok, serious question, who is publishing content base64'd images in it? I vaguely remember hearing about a new client doing this but can't remember who.

greenart7c3 1y ago

It was freezing amethyst when seeing a base64

Amethyst issue:

event:

nostr:nevent1qqswccrr8ly99aqe2hr7fvpdasgguhn2lx9spyx8z5dhfvxgu7fkpsgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8lds4tcx0f662pstqexekdmk2zw70hk4nsw6kj45q3lfvrnsrkrgpsgqqqqq4q0e7hkq