Bisq and robosats are DNMs because they are marketplaces on the darknet. They compete directly with other DNMs on products such as cash parcels, gift cards, and currency swaps.
I doubt any of the commonly used silk road descendants (good term!) support LN yet but I suspect they are looking since their competitors are doing it and seeing millions in volume. Their incentive is to attract those users to their platforms.
Three that I know of so far: Bisq, Robosats, and Shopstr
Link for Robosats: http://robodexarjwtfryec556cjdz3dfa7u47saek6lkftnkgshvgg2kcumqd.onion/
Link for Shopstr: http://iftfujvg3tv6v5fcilgswbkkntdfd7bphyuth6zfyghqrwj3kowxwbad.onion/
Monero bros down bad as *yet another* DNM adds lightning
LN has better privacy than monero
Standard caveat: do not use either one for serious privacy needs without also adopting additional defense in depth strategies
Is Bankify the first app I've made with an actual user? 
For more details, I encourage readers to listen to this debate I had with Luke Parker (monero dev):
Re: #3, the last hop doesn't know the amount being sent because of multipath, etc., and he does not know the recipient because he does not know he is the last hop. Onions are padded at each step so that they are always 1300 bytes. So the last hop thinks he might be the first hop with up to 19 more to go.
Re: "by default," lightning nodes don't expose your IP address to the public by default because the only way that happens is if you (1) configure your node to route payments (it doesn't do it by default) and (2) choose clearnet instead of tor.
Re: the podcast, we recorded it a few days ago and I am excited for its presumably looming release. I made this chart in part based on things I learned while preparing for the de ate, like the fact that monero does not encrypt peer to peer traffic. Dandelion++ is nice but if several of your peers are fednodes logging all of your IP traffic they can learn a lot.
(1) Regarding the left side of your charts, you write that monero does not (red x) publish all transactions by default, but it does. Here they are: https://localmonero.co/blocks/
(2) Still on the left side, you write that monero encrypts the sender and the recipient, but it does not. If it did, you could name the encryption standard it uses for that. But it doesn't, so you can't. (Lightning uses the Sphinx encryption standard for that.)
(3) On the right side of your chart, you write that lightning does not (red x) encrypt the recipient or the amount from all nodes. It does. It uses the Sphinx encryption standard for that. Not even the last node in the route knows who the recipient is or what amount the sender sent.
(4) Still on the right side, you write that lightning does not (red x) hide your ip address by default. It does. Lightning wallets and nodes do not reveal their ip addresses by default. To reveal your ip address, you first have to set up port forwarding on the standard lightning port (or pick a different one), and then you have to make a choice: do you want to reveal your *real* ip address or use tor? Most people choose to use tor which is why over 70% of lightning nodes are on tor:
Found another transparency chain shill! Have fun staying public bro. Maybe someday people will use your useless altcoin and pump your bags
I made it into NOBS this week! Mission accomplished
reminds me of Nostr Terminal:
I feel like Sean Parker would tell me "drop the 'un' -- it's cleaner that way"
My latest invention is Bankify: turn any cashu mint into a lightning wallet with NWC support
Maybe robot A has a chicken and robot B wants it. But robot B has wheat and robot A wants that. If robot A and robot B can trade with one another right then and there, great, but what if robot A doesn't want wheat *right now*? He won't trade. And maybe when he *does* want wheat, robot B won't want a chicken anymore. With money (i.e. bitcoin) that both robots accept for all goods, robot B can trade *money* for the chicken and robot A can *save* it, and when he wants wheat later he knows robot B wants money (because you can buy *anything* with it) so he has confidence he can buy the wheat with it.
"Brooklyn bathhouse heats water with Bitcoin mining"
Source: https://www.datacenterdynamics.com/en/news/brooklyn-bathhouse-heats-water-with-bitcoin-mining/
Alternative headline: "Brooklyn bathhouse cools bitcoin miner with human bodies"
There's only one way this goes...
I don't know what you featureset is so it's hard to say
I suspect if more services add support for login-via-dm then it will be easier to add sign-via-dm next, send then I can just use one client to interact with all supporting services. Sign-via-dm also needs clients to support it though. But I nag client devs and server devs equally so let's get to it!
š„š„š„ nostr:nprofile1qqszy58kj62v9fpe98nhuh0q76np4e0r0g0wd44rhth3wphdnyqjfzcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3wamnwvaz7tmjv4kxz7fwvd6hyun9de6zuenedyq3yamnwvaz7tmwdaehgu3wwccxctnfduyrnr5s help this man to get to the 58k ladies š¤£
yes, let them hear me croon!
not yet afaik, that's an nsecbunker feature though. I would love to see support for that added to, including in more clients. I should be able to give a website on the desktop my public key and when it wants me to sign a message with my *private* key, it asks the client I use on my phone, which then prompts me to approve the signature request. In the background the two devices can talk over nostr to share the signature requests and signature approvals and such.