Thanks for the feedback.
1. Yes, we are looking into ways to speed up the initial load, as well as the app in general. Storing more data locally will be a part of the solution.
2. Are you able to repro this reliably? If so, we'll reach out over DMs to get more info.
3. Good idea. We are considering something along these lines for our next update.
Primal.net has a new look; check it out. 👀
We wanted a clean design that makes the content pop. Let us know how you like it, and what we can do to further improve Primal. 💜🤙
https://m.primal.net/HQaI.mp4
Yes, of course. Here’s how you can get the follower count for a given pubkey:
{ echo '["REQ","subidblabla",{"cache":["user_infos",{"pubkeys":["76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa"]}]}]'; sleep 1; } | websocat wss://cache1.primal.net/v1 | grep '"kind":10000133' | jq -r '.[2].content' | jq .
Please keep this in mind:
1. This API is not standardized and is subject to change. We are planning to go through a NIP process to standardize the caching service in the coming months. Happy to help those who are wiling to suffer through these growing pains and wish to utilize the caching service now.
2. Rather than calling our instance, we encourage client developers to stand up their own caching service instances. That way Primal won’t become the source of truth and your stuff won’t break as we evolve the API.
We store the nsec encrypted locally. Uninstalling the app doesn't remove it, but it probably should. Added this to the to-do list for the full release.
We said two releases today, right? Well, here comes iOS. This is a pretty beefy release too. Should be cleaner, smoother, and much more reliable. Almost ready for prime time; targeting full App Store release in the coming weeks.
New Features
- Visual overhaul
- Settings: network
- Improved startup time
- Notifications tabs
- Profile tabs
Fixes
- Trending 24h feed now works
- Video sound handled properly
- Solidified posting & replying
https://primal.net/downloads
Primal for Android just got a major overhaul. The whole app is a lot more mature and almost ready for prime time. We are planning the official Play Store release in the coming weeks. In the meantime, please try the latest build and let us know your thoughts:
New Features
- Visual overhaul
- Direct messages
- Muted accounts
- Settings: Feeds
- Local db encryption
Fixes
- Edit profile screen now reports errors correctly
https://primal.net/downloads
Hey Marie! The short answer: no, you are not.
The full answer: we curate spam and NSFW filter lists which people can subscribe to. Primal users have complete control over the content they wish to see. The system is transparent because you can easily check if an npub is on any of the filter lists (Settings / Content Moderation). You can learn more about our content moderation system here:
https://habla.news/u/miljan@primal.net/1693416828339
This looks very promising @PABLOF7z.
Something like this would need to be deployed with a fully functional key rotation system. If somesite.com gets owned we are in a world of pain.
But overall, I think you might be onto something big here for the normie onboarding use case. Of course the advanced option where people hold their keys directly always needs to be present.
FYI, the app respects the relays you setup elsewhere. We just don't yet have the settings UI on Android to do this. You can use the Primal web app or another Nostr client to manage your relays.
Oddbean new post about login | logout
Notes by miljan | export
Yes, of course. Here’s how you can get the follower count for a given pubkey: { echo '["REQ","subidblabla",{"cache":["user_infos",{"pubkeys":["76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa"]}]}]'; sleep 1; } | websocat wss://cache1.primal.net/v1 | grep '"kind":10000133' | jq -r '.[2].content' | jq . Please keep this in mind: 1. This API is not standardized and is subject to change. We are planning to go through a NIP process to standardize the caching service in the coming months. Happy to help those who are wiling to suffer through these growing pains and wish to utilize the caching service now. 2. Rather than calling our instance, we encourage client developers to stand up their own caching service instances. That way Primal won’t become the source of truth and your stuff won’t break as we evolve the API.