you know that moment when you think of a multi-layered meme that can only be explained by explaining 5 layers of internet humor, and so you start explaining it to someone and they look at you like you're crazy for laughing at this insanity? no? ok....

we need more people to stream on zap.stream

Here's their repo: https://github.com/tailscale/tailscale-android

Yep it works on android, use it all the time both when I need to send files between my own devices and when I need to send files to my family (whose machines are on my tailnet), it's part of tailscale (an app which BTW you guys should put on zapstore 🙏)

The rules are very simple actually, if you're part of the elite you can do whatever you want, if you're a normal person you need to bow down and download the new update, repeat the daily mantra and remember that we've always been at war with Eurasia, and only followers of Goldstein would post memes against The Party.

taildrop, it "just works", but for real

Or MLS, which granted is hard to implement, but fits this problem like a T

Leave it to vitor to take an idea and push it forward to something awesome in less than a day, that's fantastic dude

they are not, they're getting good at the basics, and they're getting good at boilerplate, but thinking is still non-existent from my experience

Haha, yeah no wallet supports this yet, you CAN decode it manually and paste it, but it might not be worth it, haha

But there are here 🥜󠅓󠅑󠅣󠅘󠅥󠄲󠅟󠄢󠄶󠅤󠅔󠅝󠅘󠄠󠅔󠄸󠄲󠅪󠄿󠅙󠄨󠅦󠅒󠅇󠅜󠅥󠅔󠄳󠄥󠅚󠅒󠄢󠅜󠅥󠅒󠄣󠄽󠅥󠅑󠅇󠄩󠅘󠅔󠅇󠄾󠅪󠅉󠅈󠅂󠅘󠅔󠄹󠄷󠅙󠅉󠅇󠅜󠄹󠄱󠄵󠄩󠄦󠄣󠅩󠅟󠄵󠄾󠅇󠅨󠅘󠅓󠄹󠄷󠅛󠅉󠅇󠄵󠄲󠅉󠅈󠄾󠄤󠅁󠄷󠄹󠅧󠅊󠄷󠄽󠅧󠅊󠅚󠅊󠅚󠅉󠅚󠄲󠅚󠅊󠅚󠅓󠅩󠄽󠄴󠅗󠄤󠅊󠄷󠅊󠅝󠄽󠅝󠅁󠄤󠄿󠅄󠅁󠅪󠅉󠄢󠅊󠅛󠄿󠄷󠄽󠄥󠅉󠅚󠅔󠅜󠄿󠅄󠄱󠄡󠄽󠄷󠄶󠅝󠄾󠅚󠄶󠅚󠄽󠅚󠄱󠅩󠄽󠄷󠅉󠄡󠅊󠅄󠄱󠄢󠄿󠅇󠄽󠅨󠄾󠅪󠅁󠄡󠄿󠄷󠅁󠄢󠄾󠅪󠅘󠅘󠅉󠄡󠅗󠅘󠄱󠅩󠅗󠄣󠅡󠅖󠅕󠅓󠄴󠅆󠅪󠅈󠄲󠄣󠄣󠄧󠅗󠄝󠄽󠅤󠄤󠄦󠅣󠅤󠅪󠅗󠅂󠅂󠅧󠅏󠅩󠄤󠄳󠄽󠅞󠅈󠅡󠄠󠄷󠅧󠅜󠅃󠅏󠅛󠅉󠅇󠅃󠅚󠅉󠅇󠅆󠅉󠄹󠄵󠅀󠄥󠄺󠄤󠅛󠅈󠅓󠄴󠄽󠄴󠄼󠅊󠅪󠄾󠅃󠄽󠅃󠄢󠅁󠄸󠄷󠅙󠅛󠅪󠅃󠅔󠅑󠄵󠄼󠄻󠅒󠅘󠅠󠅥󠄶󠄶󠅇󠅗󠅆󠅣󠅄󠅔󠅉󠅈󠄾󠅉󠄹󠄷󠄿󠄝󠄷󠅩󠄠󠅒󠅨󠅦󠅄󠅩󠅦󠅢󠄠󠄠󠅅󠅂󠅢󠄡󠅏󠅉󠄥󠅁󠅇󠄽󠄝󠄧󠅠󠅧󠅣󠅘󠅟󠅧󠄿󠅘󠄷󠅕󠄢󠅧󠅥󠅨󠅘󠄳󠅉󠅈󠄺󠅉󠄹󠄴󠄤󠅊󠅠󠅧󠅃󠅞󠄢󠅊󠅊󠅚󠅤󠄽󠅞󠅒󠄣󠅁󠅘󠅪󠄼󠄳󠄼󠄤󠅗󠅧󠄽󠄶󠅃󠅛󠅑󠄽󠅟󠅥󠅇󠅈󠄷󠄶󠄢󠅟󠅛󠅘󠅕󠄩

I don't have anything written out, but this is how it works in Eve (my community building platform):

- each community is actually a nostr public private key pair

- users run their own relay (built in to the application)

- when they publish a note, it gets saved first to their local relay, then it gets encrypted (using nip44) and published to a bunch of relays, and using a PoW specified by the community

- the relays of other members of the community pull automatically any note sent to the pubkey of the community, and if it has enough PoW (to prevent DoS), attempt to decrypt it, and if it can be decrypted, they store it in their own relay

this has some issues right now:

- all members of the community have full access

- there's no way to kick anyone out

- every member will know the private key of the community

- a compromised key results in the whole community being compromised

I'm currently in the process (almost done) of rewriting this to use MLS instead of just having one key for the whole community, which will solve all the issues I outlined, but the current way it works is perfectly fine if those cons are reasonable for your use case

🥜󠅓󠅑󠅣󠅘󠅥󠄲󠅟󠄢󠄶󠅤󠅔󠅝󠅘󠄠󠅔󠄸󠄲󠅪󠄿󠅙󠄨󠅦󠅒󠅇󠅜󠅥󠅔󠄳󠄥󠅚󠅒󠄢󠅜󠅥󠅒󠄣󠄽󠅥󠅑󠅇󠄩󠅘󠅔󠅇󠄾󠅪󠅉󠅈󠅂󠅘󠅔󠄹󠄷󠅙󠅉󠅇󠅜󠄹󠄱󠄵󠄩󠄦󠄣󠅩󠅟󠄵󠄾󠅇󠅨󠅘󠅓󠄹󠅃󠅛󠅉󠅇󠄵󠄹󠅉󠅈󠄾󠄤󠅁󠄴󠄹󠄢󠄽󠅚󠅉󠄡󠄿󠅄󠄵󠅩󠅉󠅇󠅅󠄢󠄿󠅄󠄱󠄤󠄾󠅄󠅛󠄣󠄿󠅇󠅁󠄣󠅉󠅄󠄶󠅛󠅊󠄷󠅁󠄥󠅊󠅄󠄽󠄠󠄿󠅄󠅗󠄠󠄿󠄴󠅂󠅛󠅉󠅪󠄽󠄢󠄽󠅚󠅓󠅪󠅉󠅄󠅆󠅘󠄽󠅝󠅉󠅧󠅊󠄴󠄲󠅚󠄽󠅪󠅂󠅝󠄾󠅚󠅂󠅛󠅉󠅚󠅔󠅚󠄽󠅝󠅂󠅛󠄾󠅪󠄾󠅘󠅉󠄡󠅗󠅘󠄱󠅟󠅉󠅀󠄾󠅗󠄴󠅈󠄱󠅓󠄸󠅉󠅠󠄽󠅛󠅕󠄝󠅏󠅃󠅏󠅆󠄱󠅤󠅑󠅄󠄿󠅣󠄿󠄝󠅜󠄢󠅟󠄝󠅊󠄝󠄼󠅣󠄠󠄠󠄽󠅤󠅔󠅄󠄠󠅉󠅇󠅃󠅚󠅉󠅇󠅆󠅉󠄹󠄸󠄨󠅊󠄩󠅟󠅪󠅉󠅛󠅖󠅁󠅥󠅤󠄹󠄤󠄷󠅞󠄤󠅢󠄽󠅖󠅁󠄿󠅇󠅅󠄹󠅦󠄼󠅤󠄿󠅃󠄴󠄠󠅦󠄥󠅨󠅇󠅆󠄢󠅅󠅛󠅔󠅜󠄼󠅉󠅈󠄾󠅉󠄹󠄷󠅠󠅦󠅆󠅘󠅧󠄤󠅕󠄤󠄱󠅡󠅙󠅢󠄻󠅈󠅟󠅚󠅇󠅕󠄺󠅚󠅆󠄾󠅟󠅧󠅅󠄥󠅦󠅄󠅩󠄥󠄵󠄣󠄡󠅕󠅊󠄻󠅨󠅧󠄦󠅛󠄡󠅨󠅉󠅈󠄺󠅉󠄹󠄳󠅪󠅉󠄢󠄲󠅪󠅗󠅓󠄤󠄶󠄤󠅜󠄷󠅣󠄹󠄨󠅣󠅘󠅘󠅒󠅗󠅒󠄦󠅢󠅣󠄼󠅅󠄸󠅕󠅑󠅟󠄠󠅜󠄹󠄷󠄿󠅤󠄳󠅠󠅡󠄥󠄥󠅕󠅠󠄷󠄶󠅘󠄳󠄷󠄶󠅪󠅕󠄵󠄱󠅩󠅊󠅚󠅁󠅪󠅊󠅚󠄵󠅩󠄾󠄴󠄲󠅘󠅊󠅇󠅅󠄡󠅉󠄢󠅆󠅚󠅉󠅪󠅜󠅜󠄾󠅚󠅛󠄢󠅊󠅇󠅆󠅙󠄾󠄴󠅉󠄣󠄾󠅪󠄶󠅝󠄽󠄢󠅂󠅝󠅊󠄴󠄽󠅪󠄽󠅄󠅗󠅩󠄾󠅪󠅂󠅚󠄽󠄷󠅁󠄤󠄽󠅝󠅅󠄢󠄽󠄢󠅉󠅪󠅉󠅚󠄹󠄡󠄾󠄷󠄵󠄢󠄽󠄢󠅅󠄠󠄽󠄷󠅆󠅘󠅉󠅇󠄾󠅉󠄹󠅁󠄾󠅦󠅠󠄼󠅁󠅁󠄽󠅪󠅉󠄩󠅆󠅢󠅔󠅊󠅞󠅙󠄱󠄡󠄻󠄧󠅑󠅈󠄩󠄹󠅨󠄼󠄱󠄹󠄡󠅚󠄨󠄝󠅢󠄝󠄳󠅝󠄡󠄳󠄺󠅡󠅓󠅏󠄢󠄷󠄶󠅛󠅟󠄢󠄶󠅜󠅇󠄳󠄱󠅘󠅀󠄤󠅅󠅁󠅝󠅜󠄸󠅘󠅡󠅘󠅕󠅙󠅆󠅢󠅃󠄩󠄲󠅊󠅨󠄧󠅘󠅀󠅗󠅣󠅄󠅉󠅁󠅠󠅄󠄢󠅣󠄻󠄳󠄣󠅊󠅪󠅕󠅑󠅔󠄹󠄻󠄢󠄶󠅪󠅇󠄳󠄳󠅓󠄿󠅡󠅣󠄶󠄸󠅇󠅊󠄦󠅈󠄹󠅅󠄝󠅧󠅃󠄶󠅛󠄸󠄺󠄳󠅧󠄶󠄶󠅣󠅂󠄥󠅞󠄸󠄠󠅆󠅤󠅏󠅚󠅝󠅪󠅄󠅛󠅈󠄥󠅠󠅖󠄨󠄷󠄶󠅩󠅇󠄳󠄴󠅙󠄩󠅒󠄽󠅉󠅀󠅜󠅆󠄝󠅑󠅑󠅀󠅉󠄣󠅟󠄴󠅣󠅀󠅛󠄲󠅗󠅟󠄲󠅉󠅃󠅓󠄨󠄿󠄹󠅔󠅂󠄧󠅜󠄺󠄲󠄱󠅞󠄵󠄨󠅕󠅔󠄡󠅡󠅂󠅘󠅉󠅁󠅂󠅘󠅓󠄣󠅘󠄱󠄾󠅇󠄺󠅝󠄾󠅪󠅁󠅧󠅉󠅇󠅆󠅛󠄿󠄴󠅅󠄥󠄾󠅪󠅂󠅜󠅉󠅚󠄱󠄠󠄾󠅪󠄲󠅝󠄽󠅇󠄺󠅚󠅊󠅚󠄵󠅩󠅉󠅪󠄺󠅚󠄾󠅝󠄶󠅘󠄾󠅄󠅓󠄢󠄾󠅚󠅁󠄥󠄾󠄢󠅊󠅚󠄾󠄴󠅉󠅧󠄾󠅚󠅓󠅧󠅊󠅄󠅂󠅜󠄾󠅪󠅓󠅧󠄾󠄴󠅉󠄥󠄾󠄴󠄶󠅙󠅉󠅪󠅊󠅛󠄿󠅇󠄶󠅚󠅇󠄳󠄵󠄳󠅇󠅓󠅄󠅘󠅠󠄾󠄳󠅏󠅘󠄷󠅚󠅖󠄴󠅝󠅉󠅝󠅊󠄱󠅥󠄦󠄵󠄼󠅛󠅛󠅆󠅁󠅟󠅁󠅝󠄡󠄼󠅒󠅗󠅞󠅂󠅓󠅙󠅨󠄥󠄣󠄾󠅨󠅊󠅘󠅊󠄻󠄾󠅘󠅊󠅆󠅗󠅗󠅚󠅁󠅈󠅤󠅡󠄝󠅇󠄿󠅁󠅡󠄩󠄩󠄼󠄸󠅀󠅔󠄢󠄶󠅙󠄾󠄡󠅛󠅣󠄦󠅊󠅩󠅓󠅜󠅙󠄠󠄳󠅜󠅛󠄽󠅠󠅩󠅒󠅇󠄸󠅪󠄣󠅢󠄶󠅘󠅓󠄡󠅗󠅗󠅅󠅒󠄨󠅆󠄲󠅓󠅑󠄩󠅝󠅙󠅪󠄥󠅄󠅢󠅁󠄝󠄝󠅁󠄠󠄣󠄱󠄠󠅞󠅘󠄴󠅦󠅓󠅦󠄱󠄹󠄷󠅁󠄳󠅇󠅅󠄦󠄸󠄩󠅀󠅒󠅠󠅓󠅂󠅘󠅓󠅜󠅗󠅗󠄥󠅕󠅀󠅀󠄿󠄽󠅙󠅃󠅢󠄝󠅥󠄣󠄼󠅧󠅖󠅦󠅛󠅡󠅑󠅊󠅆󠄴󠅙󠄻󠄢󠅥󠄲󠅕󠅑󠅓󠄤󠅪󠅧󠅉󠄿󠅪󠅨󠄸󠅩󠅊󠅒󠅡󠅙󠅛󠅉󠅇󠄵󠄲󠅉󠅈󠄾󠄤󠅁󠄴󠄽󠄣󠄽󠅪󠄽󠄣󠄿󠄴󠅛󠅩󠄽󠅚󠅆󠅛󠅉󠄢󠄹󠄡󠄽󠅄󠄽󠄠󠄽󠅪󠅜󠅝󠄽󠄴󠄶󠅙󠄾󠅄󠄱󠄣󠄿󠅇󠅅󠅨󠅉󠅪󠄵󠄤󠅊󠅚󠅔󠅝󠅉󠅪󠄾󠅝󠅊󠄴󠄵󠅪󠄿󠄴󠄹󠄡󠄽󠄢󠅉󠄡󠅉󠄢󠄹󠅨󠄾󠅇󠄹󠅨󠄾󠄷󠄶󠅚󠅊󠅇󠅊󠅚󠅊󠄴󠅜󠅛󠄽󠅪󠄲󠅘󠅉󠄡󠅗󠅘󠄱󠄝󠅡󠄿󠅞󠄵󠄲󠄝󠄺󠅅󠅠󠄷󠄨󠄡󠅇󠄵󠄡󠅘󠅔󠅀󠅢󠅡󠄨󠅢󠅜󠄡󠅊󠄥󠄴󠅡󠅆󠅅󠄩󠅧󠅣󠅖󠅃󠅃󠅧󠅪󠅓󠄿󠄺󠄥󠅉󠅇󠅃󠅚󠅉󠅇󠅆󠅉󠄹󠄹󠅔󠅙󠅗󠅙󠅗󠄧󠅀󠅈󠅄󠅉󠅔󠅢󠄧󠅀󠄾󠄹󠄾󠄷󠅘󠅉󠄤󠅂󠅈󠅢󠄦󠄥󠅑󠄱󠄧󠅀󠅣󠅓󠅗󠅛󠅜󠅤󠅔󠅩󠄻󠅆󠅟󠄤󠅉󠅈󠄾󠅉󠄹󠄻󠄷󠄤󠅣󠅓󠄿󠅊󠅆󠄢󠅡󠅧󠄠󠅙󠄣󠄤󠅊󠄺󠄝󠄶󠅅󠅄󠄱󠄢󠄩󠄲󠅉󠅆󠄴󠄨󠄼󠅝󠄻󠄹󠄤󠄶󠅗󠅉󠄲󠅛󠅖󠄝󠄲󠄼󠅉󠅈󠄺󠅉󠄹󠄸󠄹󠅞󠅃󠄻󠅦󠅅󠄧󠄢󠅁󠅥󠅢󠅢󠅕󠄽󠅄󠅙󠄣󠄾󠅗󠅄󠄹󠅣󠅦󠅔󠅂󠄥󠄤󠅪󠅛󠅈󠄧󠄸󠅉󠅚󠅝󠅠󠅙󠄝󠅂󠅇󠅀󠅞

I put up a pull request to do this on cashu.me, it just felt like the right thing to do ~

technically yes, nip-25 allows any string as a reaction, so a client should be able to implement something like that

nice ~ thanks for the 69 sats, gotta make a pull request on cashu.me to automate this tho, haha

Emoji are complicated, unicode has 256 characters called Variant Selectors (U+FE00U to U+FE0F and U+E0100 to U+E01EF), this allows you to change how an emoji looks, technically speaking, but like a lot of things in unicode, it can be "exploited" to do a lot of things, in this case Calle is encoding 965 bytes representing a cashu token in that emoji, you can copy paste it in most applications to send someone an emoji, that's actually a cashu token.

I'm currently not aware of any cashu wallets that support copy pasting the emoji to redeem the token, but it should be pretty easy to implement

haha, if I were I wouldn't be able to tell you 😝 (or something, I don't know)

The solution is, in my opinion, neither of those options, it's relay-agnostic closed community networks that operate independently of any specific relay infrastructure, which is what I'm building :)

You need:

- **Community identity persistence** across any relay infrastructure (if ALL relays go down you as the user should still be able to access your community's data)

- **Full ownership transfer** (no relay should own ANY data about your community)

- **Multi-relay presence** for redundancy and censorship resistance

- **Encrypted communication** for communities (relays shouldn't know they're handling any particular community's data, as all the data should be encrypted and readable only by members invited to the community)

of course!