Zaps and replies are high signal, true, but you need relative measuring here which they don't provide.
You might have an excellent app that got 2x 21 sats, vs a mediocre app that got 10x 5 sats but simply because it was discovered a bit earlier. The computation will give 2 stars to the former and 5 to the latter?
Plus, you introduce another thing to trust (the computation). Ratings are signed by users and are incredibly low friction - in the context of wanting to rate something, write, zap, etc
Well, it's easy to implement and simple to understand. You could add those into the subjective, overall score.
Where are you writing the ⭐⭐⭐⭐⭐ nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9
In a label? I'm assuming that zapstore will let us rate repos.
Not writing ratings yet, we were just talking about it. nostr:npub149p5act9a5qm9p47elp8w8h3wpwn2d7s2xecw2ygnrxqp4wgsklq9g722q is totally against them. I'm not, I think it's a short way of expressing an otherwise written opinion (plus its low friction).
I would use NIP-32 (on a NIP-94 file metadata) for rating a release. I don't think it's equivalent to rating a whole repository. First because it's fine grained (release) and because it's the actual product the user is using. The repo is way more general and upstream.
Bienvenido, somos unos cuantos latinos por aca
Those of us who are interested in DVMs for CI on nostr should start collaborating.
nostr:npub1hw6amg8p24ne08c9gdq8hhpqx0t0pwanpae9z25crn7m9uy7yarse465gr nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 nostr:npub1mgvwnpsqgrem7jfcwm7pdvdfz2h95mm04r23t8pau2uzxwsdnpgs0gpdjc
eg. building artifacts, running tests and deploying code.
there is an open invitation - comment on this note and we will loop you in
I'm in! nostr:npub1zafcms4xya5ap9zr7xxr0jlrtrattwlesytn2s42030lzu0dwlzqpd26k5 will be interested too I'm sure
I was going to mention Tor but I wonder how many exit nodes are also known. It's gotten much better after they implemented PoW
Cypherpunks don't give a fuck about dietary bullshit, tradwifes, seed oils, sunning your balls, etc.
Avoiding seed oils is more important than bitcoin
Definitely! Will add as issue
Would be great to hear your take on the potential of this:
the binary at the url location is correct. see:
```
$ curl -o ./ngit.tar.gz -L -0 https://github.com/DanConwayDev/ngit-cli/releases/download/v1.4.3/ngit-x86_64-unknown-linux-gnu.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 8844k 100 8844k 0 0 2511k 0 0:00:03 0:00:03 --:--:-- 3133k
$ tar -xzvf ngit.tar.gz
ngit
$ sudo rm /bin/ngit
$ ngit
bash: /usr/bin/ngit: No such file or directory
$ chmod +x ngit
$ sudo cp ngit /bin/ngit
$ ngit --version
ngit 1.4.3
```
Ugh I know what happened. I have ~/.cargo/bin/ngit too (that one is 0.0.1) - for some reason that one was loaded before in $PATH. But weird that loads the zs version (1.4.3) in other terminal session. So the zapstore cli is working correctly. I'll look at the publishing hanging issue
That is so strange. I'll dig deeper
Use this tool: https://github.com/zapstore/zapstore-cli/releases/tag/0.0.4
You need a zapstore.yaml file, I can help you write it. Is the APK on Github?
When I try that yaml snippet on 0.0.4 I get this:
It correctly pulls 1.4.3. What did you see when publishing? Can you try again?
Damn you're right. I've tried lots of other package and always pulls the latest release, wth? I'll have a look
Oh nvm. I see it works now!
There is no zapstore cli for windows yet. I have nowhere to build or test.
I know, the relay will check event validity but not specific tags. I'll add the validation client side
Official Release #Wherostr
.
Wherostr (แวโรสเตอร์) is the only social media client on the free world (Nostr) that now supports native location pinning and check-ins, developed by Thai developers. With Wherostr, you truly own your account. You can transfer it anywhere, anytime. You won't encounter ads from the platform, and no one can delete your posts or account.
.
Main Features:
- Post: Share your content with others
- Check-in: Share your location in a post
- Reaction: Express your emotions by reacting to posts or comments
- Zap: Support content creators by sending Bitcoin in sat (satoshi) units
- Relays: Control or choose your own network connections
.
For more details and to meet the developers, join us at #TBC2024 on September 14-15, 2024, at True Digital Park, organized by nostr:npub1ejn774qahqmgjsfajawy7634unk88y26yktvwuzp9kfgdeejx9mqdm97a5
.
This is just the beginning. Stay tuned for more exciting features in future releases.
.
Experience true freedom on social media that you truly own. Download Wherostr today on the App Store and Google Play
.
Download via App Store:
https://apps.apple.com/th/app/wherostr/id6503808206
Download via Google Play:
https://play.google.com/store/apps/details?id=th.co.mapboss.wherostr.social.wherostr_social
#siamstr #devstr #nostr
Do you have an APK release?
I see, the YAML is the issue. Try the following:
```
ngit:
cli:
identifier: ngit
name: ngit
repository: https://github.com/DanConwayDev/ngit-cli
artifacts:
ngit-aarch64-apple-darwin.tar.gz:
platforms: [darwin-arm64]
ngit-x86_64-unknown-linux-gnu.tar.gz:
platforms: [linux-x86_64]
```
Fixed: platforms (they need to follow a specific format, will document later), no need to specify executable because the tarballs have ngit (package name == executable name) at the root
Can you retry with this snippet? You may have to use the env var OVERWRITE=true
Platform is an array and roughly based on `uname -sm`
I see, the YAML is the issue. Try the following:
```
ngit:
cli:
identifier: ngit
name: ngit
repository: https://github.com/DanConwayDev/ngit-cli
artifacts:
ngit-aarch64-apple-darwin.tar.gz:
platforms: [darwin-arm64]
ngit-x86_64-unknown-linux-gnu.tar.gz:
platforms: [linux-x86_64]
```
Fixed: platforms (they need to follow a specific format, will document later), no need to specify executable because the tarballs have ngit (package name == executable name) at the root
Can you retry with this snippet? You may have to use the env var OVERWRITE=true
Probably something like https://safing.io/spn/
But on nostr and micropayment-incentivized
Good point. There are likely workarounds but blocking IPs from the top 20 VPN providers will leave most of current VPN users vulnerable
VPN IPs are well known and already blocked by many sites.
ISPs are few, heavily centralized and will comply with any regulation.
It's just a matter of time until countries demand blocking connections at the ISP level, on the basis of whatever the "current threat" is.
Are we preparing for that?
Very odd behavior considering they forked a social client
Does the dev have an npub?
I'm working on WalletScrutiny.com and I'm trying to move all that could be called "attestation" to nostr with several goals:
* WalletScrutiny should not be the only authority on what we attest to. Others should be able to equally chime in and potentially provide alternative opinions.
* In nostr, events are signed by an author, with the signature being verifiable by the visitor.
* The author has followers or otherwise a web of trust which gives the visitor something to go by when judging whose attestation is worth something and whose not.
* Nostr is a protocol. Attestations could be integrated in other apps that ascribe value to them. zap.store for example could show attestations in the app store where available. bitcoinbinary.org could collaborate on these attestations given the very similar focus.
* Nostr is social. Building on nostr, WalletScrutiny might get more visibility, especially if the integration is not disruptive to others.
My question is which nip or nip proposal should I build on? https://github.com/nostr-protocol/nips/pull/1336/files looks relevant but that's only on the per app level and not on the per artifact level. For example build reproducibility is a property of each binary. Which are the kinds we should use for attestations?
nostr:npub1wf4pufsucer5va8g9p0rj5dnhvfeh6d8w0g6eayaep5dhps6rsgs43dgh9 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1az9xj85cmxv8e9j9y80lvqp97crsqdu2fpu3srwthd99qfu9qsgstam8y8 #askNostr
We need a NIP for attestations that should be linked to NIP-94! (Not the applications NIP you linked)
Watch nostr:npub1mygerccwqpzyh9pvp6pv44rskv40zutkfs38t0hqhkvnwlhagp6s3psn5p 's great talk without any of the Youtube BS.
https://cdn.satellite.earth/6224244d716e4274438c6246e8bbf6285d458045a00b343f91f5ed8a057f470c.mp4
Great to meet you Marty. We're gonna win.
After a week of nonstop talk with my fellow nostriches and bitcoiners, I'm more white pilled than ever.
Our dopamine and energy levels are unmatched by the black pilled majority.
We're building the world we dream of and there is nothing more motivating than working on a long lasting legacy.
It won't be easy, but we're gonna win.
Thank you Riga.