Would you put a mail server on your phone? web server? file server?
Lightning isn't for them either.
Would you put a mail server on your phone? web server? file server?
Lightning isn't for them either.
Party pooper.
I run my own private email server, self-hosted. I run 2 different servers: on a standard machine and on a NAS.
I think slowly email servers are dying.
Very few communication is done through email nowadays.
Nostr could replace it somehow but corporations will still use it.
BTW, if you really want to send a private message to a peer you can use keysend through LN.
I hope we will see soon an "email like" UI based on nostr.
Just imagine running a private NOSTR relay, for your corporation.
Nostr is like email in many ways, I have thought the same myself... An email client could easily check if an email address is a nip05 and upgrade the message
Spam cat and mouse games would be a problem all over again though, but if Nostr had sufficient traction as a social graph first that would make it a very compelling replacement.
spam can be handle it with some new NIP that will force to pay to the destination a x amount in order to receive the "email like" message.
Call it here nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6
I think that's undue friction and overhead at a per message level, whereas economically sound relays would be part of the social graph and whitelisted for forwarding messages.
Paid relays > paid messages
Same principle though, free doesn't work
I could receive free messages over public free relays.
But important ones could be over private nostr relays, maintained by myself or my trusted peers with which I maintain a certain volume of private messages.
Private relays could be configured also to be free for trusted peers. For others could be configured to be pay-to-send-msg.
Paying to send a message could be a subset of relay whitelisting into a social graph in that context... tiering like this would actually be consistent with QoS principles already used on the internet
my relay already by default (actually, i don't plan on changing this) doesn't allow reading of messages of a sensitive nature without being party to the conversation
yes, such a protocol could exist, i'm not 100% sure yet but i am pretty sure that you can, in principle, make a relay require an immediate zap in order to release an authentication lock
lightning can run a perfectly adequate private outbound only node on a mobile phone, given access to a SPV bitcoin node
i also think that a #nostr relay could be running on the phone perfectly well also, assuming you have a wireguard tunnel that it dials out to so that it has a stable IP address (i've set this up rn with wss://relay.mleku.online which runs on my main workstation)
receiving payments is a bit more tricky with intermittent connectivity... there is a lot in favour of the idea of custodial intermediaries that let you run an LN address and let your devices pick up payments as ecash and then flip them to receive a zap and rebalance your channel accordingly
If you're going to set up all that nonsense just use a VPS. That's even more sovereign than your backdoored phone.
Also ECash for payments is a larp and retarded, introducing a series of pointless new app specs serve only to accommodate the bankers funding that shit... It's a trojan horse.
LN doesn't have an async protocol, it's highly dependent on network liveness (A in the CAP protocol)
the entire design of HTLCs is predicated upon quite rapid propagation of a channel state change across a client-defined path
there is nothing retarded about an async protocol for off-chain payments it's just that it has other trust issues to contend with - it need not be so centralised as the existing solutions, that's the reason why the hype around it
making LN able to do async payments means changing it's fundamental architecture in so many ways... it's currently source routed onions, it needs to be changed to path routed, and then what happens when your message doesn't get through? do you depend on the payer to retry? is there a trustless or low trust way to stall a payment on the last leg to catch up when the users' device is online?
i think designating a trusted, locally based chaumian mint makes a lot of sense for enabling inbound payments to intermittent connected devices
it could even convey your token to you over nostr
i'm about to build an administration protocol that works over nostr right now, i'm sure there is other solutions here but HTLCs have to clear in a short period of time or they fail
You don't need ECash to implement a trusted solution, its all theatre like every other shitcoin.
Nothing on the internet is async, lightning won't be either. Shitcoinery doesn't change that.
yes, the internet has to have async
i am working towards phasing out my phone altogether and replacing it with VoIP based phone and SMS messaging, if that's possible, otherwise i get a dumbphone just for SMS and calls but it's gonna be some rugged thing and i'll want to throw it at the wall a few times
i'm not sitting up waiting for people to respond to me, when i'm at the computer, and not working, i'll check my messages, like i am now
the whole purpose and principle of nostr is exactly like email, you have relays (POP) and clients (SMTP)
currently lightning only has a sender, and the receiver must be alive for the message to send, there is no "try again later" option
people can run their own post offices and it's just like having a mailbox in front of your house, or you can have a post office box
these ideas that things must all be live and immediate is a product of conditioning designed to make obedient internet drones and cult mildcontrol slaves
you aren't one of those so yes you want async
POP and SMTP aren't asynchronous though, if an SMTP server is offline the senders only recourse is reattempts
This is why email servers don't belong on phones and neither do lightning nodes
i think that since you are comparing apples to oranges what about instant messaging clients on phones
sure, most of them use servers
but keet.io you only need to be running the client on your desktop and it picks up your messages and your phone can grab them too
for group chats anyway, i don't think they have (nor simplex) made it easy to share identities but with nostr i could do that tomorrow if i could throw together a quick GUI for a nostr chat client, it's beyond easy on the protocol level
i just osted a screenie of my relay's current memory usage, it's less than an average web app
so yeah... actually, things have progressed a long way since it was necessary to have hosting to run peer to peer services
That's still not async, you're running a daemon and it still has signaling servers
Also keet afaik is another clowny DHT scheme that won't scale
your argument seems to be that you can't run the internet without professional, educated asshats in data centers
or what
you are just a troll, good bye
Your arguments are that you don't understand how anything actually works 🤷♂️