Here are some thoughts...
I'm not sure a relay dedicated to photography would help much. Relay selection is not flexible enough in most clients. It might make sense to have a dedicated relay in combination with an app (or it could use a new KIND for photos are it's own thing on existing relays).
A marketplace for photographers could go into two directions:
- A public stock photography site that sells images (see istockphoto.com)
- A private client gallery where photographers sell photos from photoshoots/weddings, etc. (e.g. https://pixieset.com/ and hundreds more).
For both usecases there are already a plethora of options.
There are a lot of photography communities already - it would be very hard to build a community on a new platform. Ideally we would have a generic nostr based forum software that could be customized to the usecase (e.g. like www.discourse.org, phpBB, ...). Someone should built that first :)
The Instagram type app is something that comes up every so often. The need for a photo focus app let me to build slidestr.net. The thing is, I'm not sure a generic social photo app will gain much traction today.
It worked in the past with Google+ (a lot of photographers joined there), Instagram (fixed square format + filters), 500px / flickr, ... but it needs some clear advantage
over the existing solutions for people to switch.
Today most photography is done on mobile phones, i.e. I think people expect to use a (native) mobile app. All the PWA / web app stuff is to cumbersome for people.
A combination of the community and the app idea, could be a place for photography challenges (e.g. like https://52frames.com/albums/2024/week-42-on-the-ground/challenge ) where people post their work for daily/weekly/monthly challenges or projects regarding a specific topic. This would be a kind of learning community with image galleries.
Opt-In Advertising coming to nostr?
"1. Create an app that activates the Attention Marketplace enabling users to pool, price and sell their attention to advertisers."
nostr:nevent1qvzqqqqqqypzpuepsnh8hpwj6a50llwmcvk8twlddkfw9h2rw9p27hzsppk3c9alqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqh8sdzepydv7aeehpyzm0n50xfq8l4lsmqv67k9skp44dmkdw7tlqtj6wn4
You can create a https://npub.pro/ site and set it to "long form posts" only. Then you have a hosted website that shows your longform content. It's just limited to a single npub.
- I like the idea. Especially making the process fun!
- If there a standard for mapping seed words to emojis (couldn't find it)?
- Most users might take a screenshot to remember the key - not sure if that is what we want.
- We also need a similar UI to be able to enter the emojis to restore a key.
No it’s its own thing … https://github.com/hzrd149/blossom
The idea is that the hash in the URL is always the hash of the content to allow reuploads/mirroring which NIP96 does not ensure (for server side transformations).
Exactly… NIP96 always uses the original file’s hash in the url even when the content was transformed, I.e. then the content returned does not match the hash in the url. Mirroring/Reupload with the same hash is therefore impossible.
When transforms are disabled (there is an option) then NIP96 behaves very similar to blossom in terms of hash usage (except for paths and auth events).
Kieran nudged me to implement both on bouquet.slidestr.net and they play along nicely when not using server side transformations.
Oddbean new post about login | logout
Notes by florian | export