Que dice el error cuando apretas el boton?
GM!
There is an error parsing some app versions. I will be fixing it today.
If you really need to upgrade one of those apps, though not ideal, reinstalling will work.
nostr:nprofile1qqsx8lnrrrw9skpulctgzruxm5y7rzlaw64tcf9qpqww9pt0xvzsfmgprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshssfnq7m
Sure. Please talk to the dev nostr:nprofile1qqsx8lnrrrw9skpulctgzruxm5y7rzlaw64tcf9qpqww9pt0xvzsfmgprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshssfnq7m
Sure, what's the Android app ID?
Because the monkey that is in charge of it is overworked and underpaid
Yes, because there is a hash mismatch. I can't do anything about it. I think they fixed it.
Thanks for letting me know. I need a much bigger budget to fix these things 😅
What was the message?
It's normal. The file is broken. They must do something about it. Zapstore working as expected
For devs who are interested, here's a screencast on how to self publish from a barebones Ubuntu 22.04 installation.
https://blob.satellite.earth/ab8a4285882ffec90ca8d45081675f0dc943ab7dcd7c8d7791f32969c2c3f7b0
Wen app in nostr:nprofile1qqs83nn04fezvsu89p8xg7axjwye2u67errat3dx2um725fs7qnrqlgzqtdq0 ?
We now have nostr:nprofile1qqsth7fr42fyvpjl3rzqclvm7cwves8l8l8lqedgevhlfnamvgyg78spzpmhxue69uhkummnw3ezumrpdejqz9rhwden5te0wfjkccte9ejxzmt4wvhxjmcpp4mhxue69uhkummn9ekx7mqqdtrej signed by the dev on Zapstore!
Who's gonna be the next?
Awesome! I now need to remove the copy we were indexing
Android does not handle trust on first use, as it allows you to install APKs from any source.
This is what I meant for signatures: https://github.com/nostr-protocol/nips/pull/1335
To be honest I do not know. I just tried installing (not updating) and it worked fine.
What zapstore version are you running? Can you send a screenshot/cap of the error? Can you try reinstalling?
I am certainly not asking for permission, these APKs are indexed.
APK certificates are outside the nostr ecosystem (unless we use my proposed linked cryptographic identities PR, which I'll add to zapstore-cli) so that doesn't help with the TOFU issue and web of trust.
I want users to tag them (not me) if they feel it's necessary 😉
Some apps with nostr accounts that do not self publish:
Primal, Minibits, eNuts, Fountain, Aqua Wallet, Nostrmo, Fedi, Voyage, Wavlake, BTC Map, Simplex Chat, Nunchuk Wallet, IVPN
Are you okay with those being indexed/signed by Zapstore?
Would you prefer them to be signed and published by their developers?
If so, poke them to do it! I am happy to guide them through the process
(Bonus: self published apps can be zapped!)
#devstr
You trust the developer on this.
A planned feature is the reproducible builds DVM, where different vendors can vouch for a specific hash when building from source. It would appear like checks or badges in the UI.
This seems very complicated. As a left curve individual I want to query a service and get the stuff I want, very fast, and yes that includes personalized Pagerank.
It's up to the service to cache internally if it can't do realtime, no need to generate a massive amount of events.
As a client, I can ofc keep these signed results cached if I want, put them on a relay, whatever. I just don't think this belongs to a spec
I need to read NIP-85 in full to give my opinion but exporting this data for every single pubkey permutation seems like a waste of resources.
Thanks but Zapstore is already using Vertex, we need this actionable information in under a second.
Early next week (Tue-Wed probably) I will publish our draft DVM specs and I would love if y'all could chime in. I'll ping you
I need relevant follows who follow. How do I use this NIP for that? At a glance I could not figure out
We're moved away from the old centralized API for web of trust data.
Please make sure you're on the latest Zapstore 0.2.3 or it won't work!
Old one is down yes, Vertex on 0.2.3 is up 👀
Please make sure you are running Zapstore 0.2.3, it will work there.
It seems you are on an older version
If all goes well, this year the app catalogs (via multiple relays) will massively increase 🤞
Let me know if you have any questions about it!
Oh ok! Sorry, I need to catch up on those next week
Thank you, will fix
I removed it to give way to them to self publish. Did you manage nostr:nprofile1qqsra2ey033mkdwl5w8q0jss9ak69zafh82xsuvhwsaauw3trkq2amgpz9mhxue69uhkummnw3ezuamfdejj7qgcwaehxw309anxjmr5v4ezumn0wd68ytnhd9hx2tck28qzu ?
Thank you. Yes, that is the plan - we need to build a custom relay for that and figure out how to scale updates, not trivial. Adding multiple relays (that have different policies) is required for that and coming too.
Can't have it all 😂
Probably the stock Android keyboard - GBoard?
There is likely zero reason for your Android keyboard app to have internet access.
Long press on the keyboard app icon, tap on App info and make sure it does not have the Network permission.
Long tap on the app icon. Go to App info. Remove Network permission.
Because Zapstore is spelt all in one word and I liked it more
Thanks Max, this is great to hear!
To address some of the comments: yes, Zapstore is not a full Obtainium replacement for now so they can be complementary.
Managing relays is a priority for this year, and at the same time I started designing a "proxy relay".
Early stages and not an easy task - but the idea is you will be able to add this github-proxy relay and through the usual Zapstore UI find any APK on Github. This approach has important tradeoffs that I'm thinking how to present to the user. (These relays will be signing with their own keys)
And yes, this means we will be opening up for anyone to provide an app relay and easily add it to Zapstore - something that today it's only possible by forking the app.
Can you try again? If it still fails and the file fully downloaded, it's likely nostr:nprofile1qqsvxq03xdev3uxehjqcdkr5lfzl5vawmcf7vm6ps73m6ghwg8y4k2spz4mhxue69uhk2er9dchxummnw3ezumrpdejqz9nhwden5te0dehhxarj9eekcmm5dpujuamfdcq3yamnwvaz7tmsw4e8qmr9wpskwtn9wvuasnac modified the github release. Otherwise there is a man in the middle attack - be careful this is a wallet
How much time is forever? Sometimes connections are not great and it can take a bit longer. Our relay is not always performant.
Can you kill the app and try again? I just did that and it loaded everything in a few seconds, and I'm on a bad cell connection
Have you searched for it?
nostr:nprofile1qqszy58kj62v9fpe98nhuh0q76np4e0r0g0wd44rhth3wphdnyqjfzcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3wamnwvaz7tmjv4kxz7fwwashvmrpddjjucm0d5q3samnwvaz7tmjv4kxz7fwwdhx7un59eek7cmfv9kqurnrls do you want to self publish and get zapped?
Are you receiving zaps for Amethyst?