Si, ya está released; fue la primera en salir, pero estuve teniendo muchos problemas con zapstore por el cambio de dominio que hizo @franzap ; me dijo que ya está resuelto así que hoy voy a probar deploy it de vuelta a ver si va bien 🤙
Will do! If I publish the event changing the URL to my blossom server manually would that work or does zapstore expect files to be served from its own URL?
The funny part is that the TestFlight public link was a super early version, literally the first thing I uploaded into TestFlight to see if I could generate a public link for it; all the feedback I was getting was for a super old totally broken version! 😵
How is it true? My clients just show me what the people I follow publish; or do you mean that popular accounts get more kind:6s thus the people I follow give some popular pubkeys a disproportionate amount of visibility?
Yeah, there’s a fine balance; solely using kind:20 is hard because literally there was not a single kind:20 in any of the relays I checked; going forward it’ll be easier once we populate some content in it.
I still think there’s a place for getting kind:1 with images for the general feed (not on the profile) if the kind 1 is the root.
Awesome to hear!
I literally just get the kind:1s and filter out the ones that don’t have an image URL, excluding gifs since those tend to be lower quality.
I think there’s more heuristics that could be used like amount of text, root vs reply, etc, but I think ideally more clients would use kind:20 when the focus is the picture, I just don’t think that’s going to happen.
I might end up allowing the user to filter for this; let’s see how it plays out.
Announcing Olas 0.1!
Olas is an Instagram-like client for iOS and Android.
Olas 0.1 provides a feed of videos (like those on flare/highlighter/zap.stream), picture events (kind:20, a new kind that no client had implemented yet) and the classical short notes with images attached we are all used to.
When publishing images, Olas uses the new kind:20, in a future release you’ll be able to control whether to publish as a short note so that it appears in microblogging clients too.
Some more features already available:
✅ blossom uploads 🌸
✅ NIP-22 replies
✅ Reels (still quite buggy though)
✅ Edit your preferred blossom servers
✅ Edit your nutsack mint list
✅ Image download optimization (to be gentle with mobile data plans)
Coming next:
- NIP-55 (Amber) Logic
- Fix NIP-46 (bunker) login
- complete NIP-60 (nutsack) wallet
- Add NIP-57/61 zaps + nutzaps
- Bookmarks
- NIP-29 support: you’ll be able to create private or public communities where to share photos and videos with; imagine creating a private group just for your family or friends where you can publish pictures you don’t want to share with the world; or a community for artists.
Android users got a chance to get a glimpse of it already since nostr- active app stores like Zapstore are 100x easier to work with than permissioned stores.
EXPECT BUGS, this is an alpha release.
TestFlight link:
https://testflight.apple.com/join/2FMVX2yMnostr:note1jza65mj3ndamfump9ppr02duawv98k2e83ppeh832j6tfg8euwtq3gzj5r
Ooooh shit; I know what happened, apparently after deploying I need to push explicitly to the general tester group the new version; the version everybody installed is like 1 day old!!
my first time releasing something on Testflight, looks like I needed to be explicit about which version the link points to; I just thought it would point to the latest one 😅
Apparently I need to now wait for the central planners at Apple to approve the fucking release; I thought in TestFlight you could just deploy and the review bullshit was just for the App Store…
Yes, TestFlight link, funnily enough, what’s making me doubt whether to wait to release is that the icon is a horrible contraption I made with DALL-E 😂
Yeah, the bunker sign in is not working, not sure why, must have fucked up something very dumb
The zap store release is very old, almost 20 hours, so it’s quite different now 😂 but @franzap keeps censoring me
Ah ok! Well, my plan is to enable NIP-29 into Olas, which means you’ll be able to have a private community where you can publish stuff into, so it sounds like functionally it would be like what you’re saying?
Kind 20 as per @Vitor Pamplona ‘s recent NIP
But I’m debating whether that’s a good idea or just use kind 1
I think I will introduce a way for users to choose based on what type of audience they want to reach with each post; it’s a new approach pretty unique to nostr so I think it’s worth exploring whether that UX makes sense
all nostr apps should immediately come with a fully functional frictionless wallet that is available in any nostr app
#nutsack
https://m.primal.net/MYVB.png
Yes! This is one of the directions I want to explore; a mix of a NIP-29 (simple groups) + instagram client.
Right now I’m building the Instagram part in Olas 🌊 and this audience-scoping will soon follow.
Oddbean new post about login | logout
Notes by PABLOF7z | export