"very dangerous" is a gross mischaracterization of njump.me

This is nonsense talk.

It WAS Malos who publicly signed notes disclosing information about himself, information that is forever stored in hundreds of relays.

Are all relays now very dangerous because they store potentially identifying information about you?

njump.me isn’t producing any new information other than the one it had access to… provided by no other than Malos himself…

Let’s stop blaming the tool.

What can Malos, avi chand or you do about it? You could ASK the developer of njump.me to provide a facility to opt-out for your pubkey.

nostr:note1ujx8ent7nxwcp5y8t2nx7288ktpqezqayjan6tyaepynny6mgk8sx9d2zq

Reply to this note

Please Login to reply.

Discussion

Gotta love those gross mischaracterizations 😊

Also, I don’t think it’s broken. It just caches the info for a week. Maybe they should reduce the cache for profiles to a day. That seems reasonable.

Clients that fail to update their cache in a timely manner is a broken client in my opinion. This is especially true for lightning address updates and zaps.

When clients retain stale and outdated information in their cache, they themselves are outdated and stale.

It’s important for nostr that clients update to the networks’ current state efficiently and quickly.

nostr:note1p5jqzuz0cuv87kdts2mzr2hq9rhsgqpkfy0ac42zgu8jhmwurnvqszand3

For LN addresses it makes sense

My profile on njump.me is like 6 months or older

The profile events with his info are still out there in relays. Even if njump is fixed his information is still out there.

njump isn’t the source of truth. Even if it has a cache bug my point still stands.

Your ad hominem attacks only serve to demonstrate the frailty of your argument. Do better.

Stop blaming the tools for people’s mistakes. He doxxed himself and that’s a fact.

Why the heck should his profile metadata (name, pfp, banner, NIP-05, NIP-57) be "out there" on hundreds of relays? Doesn't make sense. I can understand if his npub and post nevent are out there, but NOT his profile metadata.

The moment he changes his profile metadata, it should change across Nostr when cache invalidation happens. That's what the poor guy thought.

But njump.me did not change his profile metadata

If nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp says it's a bug, I think your opinion is absolutely redundant, pal

Where and how do you think the metadata is stored?

Surely there should be some way to keep the metadata consistent

It's all buggy otherwise

I think more people should know about nosta.me

And then there's fekkin habla.news

That's not updating metadata either

The fact there’s a bug on njump is a non-sequitur to my argument. The tool is not to very dangerous because a user chose to dox themselves in the past and then wanted to backtrack. The accountability cannot be shifted from the user who consented, signed, and published their own information to a tool that merely displays it.

Lol šŸ˜‚

I like you for using big words like ad-hominem and non-sequitur ... lmao šŸ˜‚

You're still not getting my point though

Why the HECK should different versions of profile metadata (name, pfp, NIP-05, NIP-57) exist on relays? Why? The only data needed to display your notes are npub and nevent

Nosta.me allows you to make your profile metadata consistent across relays and make it current. Pls use that tool

njump.me is the ONLY broken tool that displays your info that's like 6 months old

And I said it's very dangerous because it's broken. There's nothing wrong with the tool otherwise

There's a Greek word for this šŸ˜‚

You-got-owned-uspus

Does nostream delete the previous metadata events when a new one is posted?

Give it a shot and then check how many versions of your profile are there with nosta.me

Backtracking with your profile metadata should be a legit option

It's not notes, it's your profile

Well, fuck you

And go to nosta.me

It will tell you, "there are x versions of your profile on y relays. Pls edit to make them consistent". I wasn't attacking you, just saying you're unaware of this

that's pretty cool. didn't realize nosta.me did that. never did click into where that info is displayed. it found an outdated version of my profile on one relay and i was able to use nak to broadcast my most recent profile to that relay.

nak is a command-line thing?

Yeah it’s awesome https://github.com/fiatjaf/nak

We have an idea for a profile health check that would also point these things out and let you fix them with a click. Hopefully can get around to implementing that soon, it should be very helpful. https://github.com/GBKS/nosta-me/issues/35

There’s probably people out there that cache every version of someone’s profile. The better way to avoid getting doxxed from old events you’ve posted is to create an alt account and start posting from there.

Nostr is your way of signing everything you say - not many understand this

can’t throw a stone and hide your hand

Nope , even if it’s a round the back

When your cache invalidation is dangerous šŸ’€

What does this have to do with relays?? Lol šŸ˜‚. I should be able to change my profile metadata whenever I want to ... not my notes, but definitely my profile metadata

Cache invalidation is not happening on njump.me ... nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp himself admitted it's a bug. He's the developer of njump.me

What nonsense are you talking?

njump.me is NOT serving the latest profile metadata. Cache invalidation is not happening. nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp said it's a bug

It's not about the notes, you clown

At least, the latest profile should be served

Do you realise you just jumped in with your half-assed information?

Fact: Njump didn’t doxx him. He did.

I tried this for my outdated profile on njump and it's not returning my kind 0 anymore for njump.me with nak, but on njump.me it's still loading my outdated profile when I go to https://njump.me/npub1vp8fdcyejd4pqjyrjk9sgz68vuhq7pyvnzk8j0ehlljvwgp8n6eqsrnpsw. It loads correctly on njump.me if I use an nprofile with relay hints though https://njump.me/nprofile1qqsxqn5kuzvex6ssfzpetzcypdrkwts0qjxf3tre8umllex8yqneavspz3mhxue69uhhyetvv9ujuerpd46hxtnfdurp22h6

Thank you. Yes, that's probably because of a secondary Cloudflare-powered HTML cache, but that one should be invalidated soon.

Cache has existed since the inception of the web. Calling old cache dangerous is a gross misunderstanding of web technologies.

Cache invalidation is not happening on njump.me

No one has a problem with cache, genius

Njump.me has a bug as confirmed by nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9us2xuyp

And nostr:nprofile1qqsqqqqqqzp8l74ff0l29zxrml8yggk8jnamje39k6e3ayzf7u5awqqpzemhxue69uhkwun9v4h8xmm4dsh8xurpvdjj7qgnwaehxw309ahkvenrdpskjm3wwp6kytcppemhxue69uhkummn9ekx7mp0sy68x3 is super stupid to assume anyone has a problem with the way njump.me works

The point is cache invalidation is not happening. That bug is the problem, not njump itself

I LOVE YOU 🄰