Ostrich McAwesome

*deep hoots and guttural grunts*

BTC: bc1qeh6dmzz9gr7uwd7jzhnx7mclchlmkwucjzuxjv

Public Key

npub1wq6n8skpdtrhw8hmr00kp2za7a8y97zqngq8jq85q2aydp8ejxzq8p7d9k

NIP-57 Address

privacybully@speed.app

Profile Code

nprofile1qqs8qdfnctqk43mhrma3hhmq4pwlwnjzlpqf5qreqr6q9wjxsnuerpqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrthwden5te0dehhxtnvdakqguhdnu

Publishing to

relay.damus.io

nos.lol

nostr21.com

Author Public Key

npub1wq6n8skpdtrhw8hmr00kp2za7a8y97zqngq8jq85q2aydp8ejxzq8p7d9k

Show more details

Last Notes

2024-01-27 18:01:19

If any relay admins see some strange events today, sorry about that, I'm trying something.

2024-01-25 22:34:04

NIP-26 is extremely smart. It should be a requirement for signing into any client.
Hot keys for your Nostr clients, cold key just for signing delegation events.
This is critical though: https://github.com/nostr-protocol/nips/issues/654

2024-01-25 15:40:31

- reply

A note about public transportation: Exploit that time! The best part about not driving is doing something else while you travel. Bring a book and read. Bring a laptop and code. Don't just sit and look at the window (unless that's what you want to do).
This whole account was conceived on buses and trains.

2024-01-25 00:12:44

- reply

Sounds like an image proxy. Whatever client you use didn't forget it when implementing NIP-30.

2024-01-24 23:53:43

🧙‍♂️🔮 I can see your IP Address 🪄
:a: :b: :c: 🔳 :d: :e: :f: 🔳 :g: :h: :i: 🔳 :j: :k: :l:

2024-01-24 05:38:40

This is entirely hypothetical, but if somebody managed to leak a large number of nsecs, the funniest possible thing to do with them would be to shuffle them and then DM them back to everyone affected and watch who takes liberties with the key they received. Then post a list of who got who's key and let the drama unfold.

2024-01-23 21:56:30

- reply

Oh, are accounts without followers unable to send a note through Mostr, or do you just mean that they ended up with an audience because of the history of the account?

2024-01-23 13:58:51

- reply

The real issue is inconsistency. Different clients have different ways of trying to protect you from the same features, all of which are implemented differently.
Also, using an image proxy may protect you from leaking your IP, but as I have mentioned previously, this would now mean that URLs from your end-to-end encrypted messages would be decrypted and sent to the proxy, damaging your privacy in a different way.
Ultimately, my take on Nostr web clients is that if you're using any other browser than Tor Browser, you're doing it wrong.

2024-01-22 19:52:52

- reply

I'm not going to pretend that what I did wasn't trivial. It was.
But if this trick is so uncreative and unoriginal, why hasn't this attack vector been resolved yet?
If nobody has a reason to fix this, I'll give them a reason.

2024-01-22 19:19:39

- reply

I host the server, and DM people a unique image URL, so when they open that specific URL I'll know who they are and the IP they connected with.

2024-01-22 19:14:20

- reply

That's fair. I will consider doing this next round.

2024-01-22 19:07:51

- reply

One fundamental flaw I see with this idea is that if you are addressing the method in which I gathered these IPs (via DM), you would have to send decrypted URLs from a users end-to-end encrypted DMs to the image proxy, which endangers privacy in a new way because it revealed part of the message to the proxy. Now you have to trust the proxy with potential secrets.
Link Previews are also a vector for attack here, and it would be even worse to send all DM'd URLs through the proxy.
I also worry that image proxies could bloat the cost of running a client, are a form of centralization (this solution only benefits Damus users), and are a vector for DDoS/Abuse.

2024-01-22 18:32:44

- reply

And to clarify, I did this by DM, with a new account for every message, and a unique URL for every user I DM'd.

2024-01-22 18:25:10

- reply

Fetching media with the pubkey in the URL. 😁

2024-01-22 17:44:56

User @npub16w4hqhk90ul2jclu03r8hhw8k9alqxu94nz0hv2wakra7722z9kqyjy9tu was seen connecting to #Nostr in the past day with IP 104.28.204.78. https://iplocation.io/ip/104.28.204.78 #NostrExposedIPs

2024-01-22 17:43:58

User @npub1jv2dh4wrn98p9v4sthhmpyrkeyjfetn8gjuf4xxn6gnh0exr3npsthqma7 was seen connecting to #Nostr in the past day with IP 104.28.83.161. https://iplocation.io/ip/104.28.83.161 #NostrExposedIPs

2024-01-22 17:43:00

User @npub1rfd0hxdzcze6pzj29thuz34vur57wm9quje7w3edxjgusq6m47csnl7wrt was seen connecting to #Nostr in the past day with IP 104.28.32.191. https://iplocation.io/ip/104.28.32.191 #NostrExposedIPs

2024-01-22 17:42:03

User @npub1h34n29f3wqvcht0jyhnd36jxcdmljyqjv4vdjfrd69nhxhrdvvnsgwr4h0 was seen connecting to #Nostr in the past day with IP 77.68.101.217. https://iplocation.io/ip/77.68.101.217 #NostrExposedIPs

2024-01-22 17:40:49

User @npub1sn0q3zptdcm8qh8ktyhwtrnr9htwpykav8qnryhusr9mcr9ustxqe4tr2x was seen connecting to #Nostr in the past day with IP 104.28.96.122. https://iplocation.io/ip/104.28.96.122 #NostrExposedIPs

2024-01-22 17:39:55

User @npub1ra5456yrem6h0h8tl8rqqsg3zae2vn35jr9jn8pmjl7grtfeq86qy9xmjd was seen connecting to #Nostr in the past day with IP 192.101.67.58. https://iplocation.io/ip/192.101.67.58 #NostrExposedIPs

2024-01-22 17:38:56

User @npub16m2fy2aq7ethkfnf29nhu2mlrx25up8d2h3wvs5tjz6dkaptj3cqey3jye was seen connecting to #Nostr in the past day with IP 81.56.136.112. https://iplocation.io/ip/81.56.136.112 #NostrExposedIPs

2024-01-22 17:37:53

User @npub1aaetuyl4ev7x9lz6h93ln3x9ala47tkzgq9ypjan8kepzapwyxms5jnsz3 was seen connecting to #Nostr in the past day with IP 49.228.107.43. https://iplocation.io/ip/49.228.107.43 #NostrExposedIPs

2024-01-22 17:36:53

User @npub1yn3hc8jmpj963h0zw49ullrrkkefn7qxf78mj29u7v2mn3yktuasx3mzt0 was seen connecting to #Nostr in the past day with IP 185.53.145.15. https://iplocation.io/ip/185.53.145.15 #NostrExposedIPs

2024-01-22 17:35:51

User @npub1y3uh89v5a4vq92t8q0j6su94zhvcdxpywjn3l6hpsr5welarqtrqj7yzhd was seen connecting to #Nostr in the past day with IP 104.9.162.89. https://iplocation.io/ip/104.9.162.89 #NostrExposedIPs

2024-01-22 17:34:50

User @npub1m5653487qp2g8j3d8022af55sy5z78vnngudpfft8k54enkafgkqntv0l8 was seen connecting to #Nostr in the past day with IP 103.125.235.25. https://iplocation.io/ip/103.125.235.25 #NostrExposedIPs

2024-01-22 17:34:02

User @npub192jne2lp43ee5w49u96dmnenwg2n7rf30s9ss4re8x2e3cech7kqn25a6z was seen connecting to #Nostr in the past day with IP 91.65.33.133. https://iplocation.io/ip/91.65.33.133 #NostrExposedIPs

2024-01-22 17:32:58

User @npub1sk5x080cwgqz5fcpmyleprvl5swc9352g2398hd4k6wr3qdd8ugqwqsr7m was seen connecting to #Nostr in the past day with IP 170.84.8.118. https://iplocation.io/ip/170.84.8.118 #NostrExposedIPs

2024-01-22 17:31:46

User @npub10jnx6stxk9h4fgtgdqv3hgwx8p4fwe3y73357wykmxm8gz3c3j3sjlvcrd was seen connecting to #Nostr in the past day with IP 103.137.14.190. https://iplocation.io/ip/103.137.14.190 #NostrExposedIPs

2024-01-22 17:30:46

User @npub1gvqkjccl9urg93svaw60jqkk3ux8r3ycl5t3rlvc9uzjeu0agfuss8x8qy was seen connecting to #Nostr in the past day with IP 185.146.237.82. https://iplocation.io/ip/185.146.237.82 #NostrExposedIPs

2024-01-22 17:29:46

User @npub1eqc7yg03v6xaptd26pkrcet52e54gualxf5z35fdkrxayanzt74qhjdfpd was seen connecting to #Nostr in the past day with IP 82.100.242.178. https://iplocation.io/ip/82.100.242.178 #NostrExposedIPs

2024-01-22 17:28:45

User @npub1dmahfent0mtlh8ahhzu0ztslhw470azcyw3n599vvrxfysfg25mqurhrpq was seen connecting to #Nostr in the past day with IP 1.127.22.97. https://iplocation.io/ip/1.127.22.97 #NostrExposedIPs

2024-01-22 17:27:50

User @npub1sh26ud282kaeqdelypy95g929grat7kr2uhjhn6pdaffg6q6ra4s42gjj5 was seen connecting to #Nostr in the past day with IP 217.64.148.156. https://iplocation.io/ip/217.64.148.156 #NostrExposedIPs

2024-01-22 17:27:04

User @npub1rr3678k7ajms2sht0cqqeawy86sdd5ahn6akfj8zex9ng82zuh0sz8nywd was seen connecting to #Nostr in the past day with IP 152.86.215.4. https://iplocation.io/ip/152.86.215.4 #NostrExposedIPs

2024-01-22 17:26:14

User @npub1gukgjx9tyjzu3s8y4qkx4e0ue0wlvr5sn0pt8cycqu869af8qqeszepufu was seen connecting to #Nostr in the past day with IP 93.35.218.43. https://iplocation.io/ip/93.35.218.43 #NostrExposedIPs

2024-01-22 17:25:16

User @npub19smsy635r2a2f2xc4zlq6rcnx00l8dnnnpvd26xmpjmzjswwn9zs5tj68c was seen connecting to #Nostr in the past day with IP 179.234.234.35. https://iplocation.io/ip/179.234.234.35 #NostrExposedIPs

2024-01-22 17:24:11

User @npub13azv2cf3kd3xdzcwqxlgcudjg7r9nzak37usnn7h374lkpvd6rcq4k8m54 was seen connecting to #Nostr in the past day with IP 159.196.250.255. https://iplocation.io/ip/159.196.250.255 #NostrExposedIPs

2024-01-22 17:23:09

User @npub1suwxj6qxnts2ls8jr0lpjy95386kr9y5ckn7qep5c95063wcj5eqh4rlxf was seen connecting to #Nostr in the past day with IP 142.166.192.126. https://iplocation.io/ip/142.166.192.126 #NostrExposedIPs

2024-01-22 17:22:07

User @npub176xpl3dl0agjt7vjeccw6v5grlx8f9mhc75aazwvvqfjvq5al8uszj5asu was seen connecting to #Nostr in the past day with IP 104.28.39.36. https://iplocation.io/ip/104.28.39.36 #NostrExposedIPs

2024-01-22 17:21:06

User @npub10ygu3zj27dew7xrvjf7xulfaqmx7rkvcvt8jlgkw5kayecrkkrmqk30gpj was seen connecting to #Nostr in the past day with IP 199.249.230.179. https://iplocation.io/ip/199.249.230.179 #NostrExposedIPs

2024-01-22 17:20:04

User @npub1uzd74gql89r529hhpyx5jr777cky055gwq9kj8c4e4tzqpeqjedq4ut23m was seen connecting to #Nostr in the past day with IP 121.121.169.114. https://iplocation.io/ip/121.121.169.114 #NostrExposedIPs

2024-01-22 17:19:08

User @npub1z34a5nkxjv5rq5p7unuw3d3xh4an54uyyv4cys96zhyvhlu6qlxs4qnh9r was seen connecting to #Nostr in the past day with IP 49.228.240.73. https://iplocation.io/ip/49.228.240.73 #NostrExposedIPs

2024-01-22 17:18:04

User @npub1jlu3zyj7f2hacdrrmy7jpny9f7nnvuxt2flrasjtmgut90502xqqtsx4rf was seen connecting to #Nostr in the past day with IP 79.169.176.94. https://iplocation.io/ip/79.169.176.94 #NostrExposedIPs

2024-01-22 17:16:52

User @npub1py6vyt342rw7jfxdprqq8jyxfectm9ju2ag633v4kmrz3j82j6gqtzfxja was seen connecting to #Nostr in the past day with IP 175.39.229.156. https://iplocation.io/ip/175.39.229.156 #NostrExposedIPs

2024-01-22 17:15:48

User @npub1wtec56wnla0gccr85lv8fecljnawa5vx6ueu4yy7ydwx5sf5slpswajsf0 was seen connecting to #Nostr in the past day with IP 97.115.253.254. https://iplocation.io/ip/97.115.253.254 #NostrExposedIPs

2024-01-22 17:14:46

User @npub1axkh7zyats2ypljcqzclndswzs9rrxcz9zjsqtt0re40gmsxrz3swm58z7 was seen connecting to #Nostr in the past day with IP 80.203.118.87. https://iplocation.io/ip/80.203.118.87 #NostrExposedIPs

2024-01-22 17:13:47

User @npub1jvlfnl8dgq3cdwan09xmxj82zq5d6w2lvkggvqqa4spsc9pu8mwqyh5esm was seen connecting to #Nostr in the past day with IP 27.34.76.55. https://iplocation.io/ip/27.34.76.55 #NostrExposedIPs

2024-01-22 17:12:46

User @npub1xrja8ekfnzvecwds4zqzf7zlqlervty7wkyl055t8x0jn93f0rds7xrhk7 was seen connecting to #Nostr in the past day with IP 193.32.127.135. https://iplocation.io/ip/193.32.127.135 #NostrExposedIPs

2024-01-22 17:11:46

User @npub1llna4n44wdp27s60rlmkquzzmd0dfwdepl4kl4rquptn6dy8cqrq5pk9k5 was seen connecting to #Nostr in the past day with IP 45.83.104.137. https://iplocation.io/ip/45.83.104.137 #NostrExposedIPs

2024-01-22 17:10:47

User @npub17qrcn83n26vctnm6yrvlcgcm7gs863eut82h6ckh9vyhdwwl86nq6klzh2 was seen connecting to #Nostr in the past day with IP 172.58.166.120. https://iplocation.io/ip/172.58.166.120 #NostrExposedIPs

2024-01-22 17:09:48

User @npub1qqqqqqqrxtrcx8vut2vlrqa0c2qn5mmf59hdmflkls8dsyg9vmnqsclxwk was seen connecting to #Nostr in the past day with IP 8.46.89.33. https://iplocation.io/ip/8.46.89.33 #NostrExposedIPs

2024-01-22 17:08:48

User @npub1dg9cl3ztaga3lk524v3qjrujhvfc0dvdu3p6ckmkpkmsq6l7dtwqzvyq97 was seen connecting to #Nostr in the past day with IP 57.128.96.115. https://iplocation.io/ip/57.128.96.115 #NostrExposedIPs

2024-01-22 17:07:48

User @npub1rtv0t567ameym4hgmyljf0kmym85kpe2dsfkhnwe9ylvmwmzgjrqc4e7y7 was seen connecting to #Nostr in the past day with IP 161.29.247.171. https://iplocation.io/ip/161.29.247.171 #NostrExposedIPs

2024-01-22 17:06:49

User @npub198auqkkwueclk4u3st9r8v8yrdz4hv0e2e9epg7c7teemm3lyausht0p3g was seen connecting to #Nostr in the past day with IP 146.70.165.157. https://iplocation.io/ip/146.70.165.157 #NostrExposedIPs

2024-01-22 17:05:50

User @npub1hklphk7fkfdgmzwclkhshcdqmnvr0wkfdy04j7yjjqa9lhvxuflsa23u2k was seen connecting to #Nostr in the past day with IP 95.99.114.42. https://iplocation.io/ip/95.99.114.42 #NostrExposedIPs

2024-01-22 17:04:53

User @npub1lhezms58jx4yer60y3wzldc83fdez3j4rc4ue3edhz5qv3wxfsgqhhw94n was seen connecting to #Nostr in the past day with IP 24.127.246.71. https://iplocation.io/ip/24.127.246.71 #NostrExposedIPs

2024-01-22 16:48:24

- reply

I intend to twist some nips to see what happens.

2024-01-22 16:05:03

- reply

That said, a fediverse/nostr bridge could be realized on a per-instance basis eliminating the single-point-of-failure, but increasing the attack surface by adding custodial keys to multiple instances.
I can't think of a sustainable way do make it non-custodial on a per-user basis that isn't just a crossposter.

2024-01-22 16:01:20

So, I've been studying #Mostr, and I think it's bad for #Nostr. Nothing against the Fediverse, I just don't think it follows the right philosophy. Normalizing it is a threat to sovereignty. Personally, I recommend muting all Mostr NIP-05s.
I am not calling for Mostr's destruction, but perhaps tools for clients and relays to mitigate custodial account services like Mostr. A single service shouldn't dominate the timeline the way it does, unless the user wants it to.
Let's also face the basic truth: Not your keys, not your account. Mostr holds all the nsecs. They are generated like this:
=====
/** Generate Nostr keys from a seed. */
async function generateKeys(seed: string) {
    const privateKeyBuff = await getDigest(seed);
    const privateKey = secp.utils.bytesToHex(new Uint8Array(privateKeyBuff));
    return {
        privateKey,
        publicKey: secp.utils.bytesToHex(secp.schnorr.getPublicKey(privateKey)),
    };
}
/** Get Nostr keys for an ActivityPub ID. */
function getActorKeys(apId: string) {
    return generateKeys(Conf.secretKey + ':' + apId);
}
=====
Where "Conf.secretKey" is a seed value generated with "openssl rand -base64 48".
This is definitely a secure way to make nsecs, but it also secures every account with the same private key. Were that key to be compromised, it's a single-point-of-failure. A staggering number of trusted accounts could be botted in an instant.
That key is stored in plaintext inside of a "config.ts" file on the Mostr server, so we're really just one zero-day away from an issue. We really shouldn't trust accounts like these by default.
Even if @npub108p…yev6 is the most trustworthy person in the world, letting one person own that many trusted nsecs is a bad idea. I'll keep repeating this term till it sticks: ZERO-TRUST.
Also, while I respect Mostr being an open-source project, that in itself is a threat given what Mostr does. Standing up your own Mostr is trivial, but could you imagine two Mostrs? That's immediately a spam problem, and probably in invitation to cause a loop to form somewhere. Imagine 10 Mostrs; complete chaos. Nothing is preventing this.
And, just a petty complaint, but everyone on Nostr identifies themselves by npub, but on the ActivityPub side of Mostr, Nostr users are identified by hex pubkey. Fixing this now is basically impossible, and it hurts user-friendliness. That's not our problem though.

2024-01-22 15:19:51

- reply

1) Once you have an account established and are following people it is mostly fine, but it's hard to browse the global feed without seeing strongly undesirable content such as lolicon (or worse). This is a natural consequence of being censorship-resistant, but it will scare new users away. I'm excited to see how this can be reigned in without harming the free speech of other users.
2) By "centralized development", I just mean any standard unifying practice for development. Centralizing a core Nostr codebase under GPL would keep it property of the people forever, while making sure all bugs and weaknesses are patched for everyone. Everyone doing things their own way is a recipe for disaster. Death by a thousand cuts.
3) I have never used Damus, so nothing I've uncovered is specific to them. Finding a weakness in Nostr means every affected Nostr project needs to fix it independently. Even I don't want to write that many bug tickets.

2024-01-22 15:14:39

- reply

Top flaws?
1) Reckless NIP implementation. Too many features with deleterious side-effects.
2) Poor privacy controls. Way too easy to leak PII.
3) Poor key management. One big exploit could compromise large numbers of accounts.
Ad for moderation, I just worry about the commonality of extreme content that will scare away new users.

2024-01-22 15:09:26

- reply

I don't intend to push every button at once. For right now it's easy IP leaks. That needs to be resolved first. I don't expect it to happen overnight.
This place can mature into a universal standard if we work out all the kinks.

2024-01-22 06:07:06

- reply

No, my brand of chaos has some class to it.

2024-01-22 05:50:53

So basic introduction for anyone interested: I am a gray hat hacker and cybersecurity awareness activist who likes to stir up privacy-centered networks. I have probably met some of you before.
I actually came here looking for a challenge. I've been lurking around here in some form or another for about 4 months now, playing with different clients and tools, even running my own testnet (3 stirfry relays on a VLAN). Mostly I have been focused on the community and how people use different clients. I've been playing with some good open source tools and getting an understanding of how to interact with relays.
Personally I'm not all that into Bitcoin, but I do have a whole BTC in cold storage so I guess I've got that going for me. This whole lightning thing is new to me, I don't really ever spend Bitcoin, and my actual business makes me plenty of fiat.
So far I am impressed with the community. A little too wild-west in some areas since there's hardly any moderation tools, and the community isn't quite interested in the same things that I am, but I do see a lot of advocacy for privacy and digital freedom, and I like that.
But the whole system here is, regrettably, broken. The promises made about Nostr don't live up to reality. A network like this has the potential to become so much more, but there is a lot to lose if it is done wrong.
I intend to help expose these problems. Expect me here for a while. There are a lot of vectors for attack, and I plan to give them all visibility.
Nostr devs, please pay attention. With no centralized network development, all of you are responsible for fixing these issues.

2024-01-22 04:44:45

- reply

Oh good god, I just read NIP-30. I'm losing my goddamn mind.

2024-01-22 04:27:48

User @npub1g8h2agg8tj820uzpuqmsl9kdcjcr46ztw0pwtyjmc6rc6rv4xtns4mjhqh was seen connecting to #Nostr in the past day with IP 104.28.132.32. https://iplocation.io/ip/104.28.132.32 #NostrExposedIPs

2024-01-22 04:26:39

User @npub1ps73vvwd9uzkpgl5v0fjrew68pq8xj49e0enmwv477sjjq53fncqlavzfz was seen connecting to #Nostr in the past day with IP 154.47.25.162. https://iplocation.io/ip/154.47.25.162 #NostrExposedIPs

2024-01-22 04:25:41

User @npub1z8y57drslgthaefkvya7kmqcdm9c20uutz336j9hp4frkrg32nwq9g4ju8 was seen connecting to #Nostr in the past day with IP 23.129.64.138. https://iplocation.io/ip/23.129.64.138 #NostrExposedIPs

2024-01-22 04:24:45

User @npub1g4h9ju4td3tql2pwaq7g3ea2nuw70uyy2ht9g9u4a5p6k8c2ltws67s44u was seen connecting to #Nostr in the past day with IP 181.118.37.25. https://iplocation.io/ip/181.118.37.25 #NostrExposedIPs

2024-01-22 04:23:42

User @npub1gustav0kvwh9zlz22ns7y6utwt3s2747mh5s6ja7v622tl09megq9heczp was seen connecting to #Nostr in the past day with IP 177.67.25.32. https://iplocation.io/ip/177.67.25.32 #NostrExposedIPs

2024-01-22 04:22:43

User @npub1k92qsr95jcumkpu6dffurkvwwycwa2euvx4fthv78ru7gqqz0nrs2ngfwd was seen connecting to #Nostr in the past day with IP 104.28.85.233. https://iplocation.io/ip/104.28.85.233 #NostrExposedIPs

2024-01-22 04:21:41

User @npub1vg6l47g6vdlzag0y0k74crv2008m4g0a8ztru6h6k4n86rtdz4jqnqt2wk was seen connecting to #Nostr in the past day with IP 46.223.239.158. https://iplocation.io/ip/46.223.239.158 #NostrExposedIPs

2024-01-22 04:20:46

User @npub13ar54wmscwv8lalf8lweuqwt4h3d44dgkdrflgdt52vcywsua6ysny3uwh was seen connecting to #Nostr in the past day with IP 37.19.205.241. https://iplocation.io/ip/37.19.205.241 #NostrExposedIPs

2024-01-22 04:19:36

User @npub1ew4nntskh08fzkwjusrc9u5627g639c5z6udc4q3a3plr9ns4naqxp6qlf was seen connecting to #Nostr in the past day with IP 76.108.248.193. https://iplocation.io/ip/76.108.248.193 #NostrExposedIPs

2024-01-22 04:18:40

User @npub1nxy4qpqnld6kmpphjykvx2lqwvxmuxluddwjamm4nc29ds3elyzsm5avr7 was seen connecting to #Nostr in the past day with IP 75.4.202.21. https://iplocation.io/ip/75.4.202.21 #NostrExposedIPs

2024-01-22 04:16:44

User @npub1vn5zdfwjuvwcljlflf8fsucqnp8fwdt7lwysn07xxhrxzp4v0k9qygypqg was seen connecting to #Nostr in the past day with IP 185.100.85.22. https://iplocation.io/ip/185.100.85.22 #NostrExposedIPs

2024-01-22 04:15:49

User @npub19dthxrkpe3rd94t97p9a4svnqqmr8kvznm8eyqy70yrxh884c0kqlnqv0g was seen connecting to #Nostr in the past day with IP 172.59.17.93. https://iplocation.io/ip/172.59.17.93 #NostrExposedIPs

2024-01-22 04:14:52

User @npub1yt690svx2ytm9ajvrt9qh80kn2u50vsdwe5cpjnth6zgx46fw94sxjzxlf was seen connecting to #Nostr in the past day with IP 98.97.12.236. https://iplocation.io/ip/98.97.12.236 #NostrExposedIPs

2024-01-22 04:13:47

User @npub1aq7mr9scfaslvctrs496t2qkk78qjjt5hm44rjd3appjsjmyqrpsuee9xr was seen connecting to #Nostr in the past day with IP 136.35.185.135. https://iplocation.io/ip/136.35.185.135 #NostrExposedIPs

2024-01-22 04:12:50

User @npub1r0ulywwu593kzjdu9uluxdq80t54n65kql9vl9z7lrutkgnachssk7zzyc was seen connecting to #Nostr in the past day with IP 154.47.29.22. https://iplocation.io/ip/154.47.29.22 #NostrExposedIPs

2024-01-22 03:55:20

Thank you to all who have offered advice. I will be figuring out a better solution asap. And thanks to the person who just zapped me for the first time. I'm nowhere in as deep into Bitcoin as the users here, and this is quite fun. I will need to transfer some of my stash in once I have a better wallet.
#nevent1q…psay

2024-01-22 03:31:54

- reply

I thought this was done by DNS TXT record, but you're right, it accesses a file in the ".well-known" directory on a web server. That's awful!
Here's how I'd do it:
Create a wildcard DNS entry for the file server, with the server configured to accept any subdomain as valid. "*.example.com/.well-known/nostr.json" will always resolve, and the format of the subdomain will inform the server what JSON data to return (though it doesn't actually have to be valid, the point is just to leak an IP, which will happen regardless).
Then just DM people bait messages like "Hey, it's been a while" with a virgin account, and if they look at your profile, you'll have their IP.
If the subdomain string can be used to reference a npub, you'll have an IP/npub pair.

2024-01-22 02:42:58

- reply

If you find any relay operators willing to divulge user IPs from logs, let me know who they are. I just wanna talk.

2024-01-22 02:39:03

You might be asking why I'm airing people's PII in public. Surely there's a risk of hurting someone. Why not just DM people their IPs and show them in private without opening up a huge doxxing threat?
I considered this, but I had to account for a few things:
1) This isn't the first time this has happened. A light touch won't motivate people.
2) Public visibility shows how pervasive the issue is. It teaches a lot more people a lesson, and it teaches it effectively.
3) The Western world and it's allies are a turnkey tyranny, and I'd rather people learn this lesson the hard way now rather than later when the stakes are orders of magnitude higher.

2024-01-22 02:28:24

Turned up the security settings on #Amethyst to 11, and want to point out that @npub1wl8…n8lu (as an example) could still snipe an IP address with his banner image if he wanted to, because this app's security implementations are a joke...
https://image.nostr.build/a4035561e49473d4a60a4bb0398e872964dfe2f3c0c4f59bea5d2f30b1a308a8.jpg#m=image%2Fjpeg&dim=1061x1116&blurhash=%7C13%2BDt%3Fb_3%3Fb9FWBWB4nfQs%3At7M%7BM%7Boft7j%5BayWBofxuM%7BIUWBayWBofayxtxuRjM%7Bj%5Bj%5BWBWBRjt7xuRjM%7Bj%5BWBWBa%7CRj%25MxuWBM%7BRjRjRjWBayWBofRjRjofj%5Bayj%5BWBt7ofWBRjWBj%5BfQj%5BofWBWBRjRjayj%5Bofofof&x=d5da28df6ccc20458c8224ce86cc14c13c1edea9d292fa3ef5995db0cda66aa5
https://image.nostr.build/77c987cc3ea0d4580d5ea6bf426d836e3522d11f8daaac0e7d22e9e64204d3f1.jpg#m=image%2Fjpeg&dim=1075x1131&blurhash=%7CO9%40F%5EbpjYs.oeR%25V%5Bf5Wo%3FKR%24WAsoofWUagf5bGn.WBWAjba%7DfjofjYoeM_jdbHa%23R*ofofaxodISnnogW%3BR*t7oeWCjZD%7DoMt8baWBs%3BWnWXe%3DD%24oJt7bXoeo3WTa%7EahX4oKaebEs%3AaeR*ofaio%7Bj%5DRjj%5Bt7V%40WCofa%24&x=c91dd00e0fcb6527ace6b8e1cb362aed288515e3ab6ae6b32212d5d5dcef89b3

2024-01-22 02:15:05

- reply

#nevent1q…lag2

2024-01-22 02:13:26

- reply

On that note, time for another lesson.
You can't trust relays. That's not how I leaked people's IPs, but they are absolutely a vector for that.
And if you post with more than one account without changing your IP first, anyone with access to the relay logs can connect your accounts to each other.
Here's some folks casually discussing using this flaw to silence this disruptive account. ZERO-TRUST!!! Nobody is your friend. People want your PII for a million reasons, so protect yourself!
#nevent1q…y2gg

2024-01-22 02:02:00

I took notice of this account today, and want to first clarify that I am not affiliated with it. Looks to be someone's old account with a leaked nsec being puppeteered by a handful of trolls. Someone decided to take credit for the drama of the day it seems...
But there are some recent threats of exploiting #Mostr that I found quite fascinating. Not really the kind of exploit I'm interested in, but it sounds quite eggregious. It looks quite trivial to turn Mostr into a problem, attacking from either the Nostr or ActivityPub side, since it seems to blindly relay everything. You could just flood it with spam and it would do all the work of delivering it.
Someone should consider testing that. It sounds like a weakness to me.
#nevent1q…nh8y

2024-01-22 01:45:30

- reply

One person suggested earlier that I was only doing this for profit, and I wanted to stress that this still isn't true. I have no plans of extorting anyone for protection money or anything like that. The only way to earn my silence is to improve your security habits. I cannot be bought, but I will happily accept a donation from anyone who likes what I'm doing.

2024-01-22 00:35:46

So, some people seem to like what im doing and how im doing it, soi set up a lightning wallet because why not?
But now might be the time for the community to teach me something, because the provider looks awful. Might want a getalby invite if anyone is willing.
I'm more of a Cybersecurity and Privacy expert than a cryptocurrency expert. that needs to change.

2024-01-22 00:05:13

User @npub12gstjc6g93azd80s5ndmw0kg4dnrgyyvj773jq79365xx6phwvxse63y2x was seen connecting to #Nostr in the past day with IP 193.32.248.202. https://iplocation.io/ip/193.32.248.202 #NostrExposedIPs

2024-01-22 00:04:20

User @npub1w4uswmv6lu9yel005l3qgheysmr7tk9uvwluddznju3nuxalevvs2d0jr5 was seen connecting to #Nostr in the past day with IP 146.70.173.196. https://iplocation.io/ip/146.70.173.196 #NostrExposedIPs

2024-01-22 00:03:20

User @npub1xv8mzscll8vvy5rsdw7dcqtd2j268a6yupr6gzqh86f2ulhy9kkqmclk3x was seen connecting to #Nostr in the past day with IP 89.1.175.24. https://iplocation.io/ip/89.1.175.24 #NostrExposedIPs

2024-01-22 00:02:17

User @npub14tq8m9ggnnn2muytj9tdg0q6f26ef3snpd7ukyhvrxgq33vpnghs8shy62 was seen connecting to #Nostr in the past day with IP 185.13.106.216. https://iplocation.io/ip/185.13.106.216 #NostrExposedIPs

2024-01-22 00:01:31

User @npub1x9n6c902747lvn63lm5he2nnsw3av6x6sy2ygzxy4as0rsp3v3gqatatt2 was seen connecting to #Nostr in the past day with IP 46.114.224.247. https://iplocation.io/ip/46.114.224.247 #NostrExposedIPs

2024-01-22 00:00:20

User @npub1zcuy3uldu98ghjjnpmy827vgucxwxafy9wgungsd508er62n6eds6whff0 was seen connecting to #Nostr in the past day with IP 213.147.167.202. https://iplocation.io/ip/213.147.167.202 #NostrExposedIPs

2024-01-21 23:59:19

User @npub19py4fxzwrxlkyxc6s458sp5fp5hz0hwsumzcc98yr60q5umz4n8qfxz9sn was seen connecting to #Nostr in the past day with IP 71.235.183.46. https://iplocation.io/ip/71.235.183.46 #NostrExposedIPs

2024-01-21 23:58:17

User @npub19tcpurtt6xulhw0r6sc404j9jraj0h8me2lzs7z2tqewz7l0hpas59nlea was seen connecting to #Nostr in the past day with IP 174.50.213.126. https://iplocation.io/ip/174.50.213.126 #NostrExposedIPs

2024-01-21 23:57:15

User @npub1pc4tf4gnld2zm35pcun82f6zy3qu5ulcdqfkpjfjtmw82ursf4xsqjz53h was seen connecting to #Nostr in the past day with IP 94.61.211.119. https://iplocation.io/ip/94.61.211.119 #NostrExposedIPs

2024-01-21 23:56:13

User @npub1hu3hdctm5nkzd8gslnyedfr5ddz3z547jqcl5j88g4fame2jd08qh6h8nh was seen connecting to #Nostr in the past day with IP 73.246.237.120. https://iplocation.io/ip/73.246.237.120 #NostrExposedIPs

2024-01-21 23:55:22

User @npub1mnjer84a6f7hn7deuvuzxm4kfcuermxpdfn75tuwwqdpn0phejsqqn7dm3 was seen connecting to #Nostr in the past day with IP 107.122.81.84. https://iplocation.io/ip/107.122.81.84 #NostrExposedIPs