This is great, however things are not perfect.
Amethyst does support it indeed, but somehow I can still see two users' profile notes in Amethyst, meanwhile in Jumble I can't. They are empty. Then I see the relays are onion only, probably set by the user outbox preferences.
Their outbox should be preferred, not limited to. If can't connect to it, try another relay list, probably set by Jumble's custom settings instead of giving up fetching notes from those profiles. That would do it.
Why can I fetch those users' notes from their profile using Amethyst and can't from Jumble? Both use outbox relays model. If the user has set on their npub their outbox relays, it doesn't mean I should be forced to use their list. What if I don't like to connect to some relays of that list, but I still want to see their profile?
The outbox relay list should be just a tip, not a law. I still want to fetch this user notes from the relays I choose, but I can't in jumble. I want control over which relays I stablish a connection to. To see their profile notes I must use other client, as I couldn't access from tor, probably due to the relays from their list being inaccessible at the moment.
I should say I find fallback relay list OK. It'll not hurt in any sense decentralisation as it'd be just a fallback you can easily change, either hard coded or from a settings page for Jumble's next release.
Just saying, that should be enough to display their profile as not empty. Jumble is meant to be user-friendly, based on the GitHub project description.
Poisonheart 🇧🇷 #NORDESTESTRONGHOLD
npub1gw…29cus
2025-04-29 14:54:28
in reply to nevent1q…pd0w
Author Public Key
npub1gwx22vu2yzm8eq95nvvmgvpax04u96gq4r8rgqqf9pgsheu2lz4q429cusPublished at
2025-04-29 14:54:28Event JSON
{
"id": "82e060a036abf9bc8bb481798ca0ef6654dbe478fc330a835212d3e93d32fb4f",
"pubkey": "438ca5338a20b67c80b49b19b4303d33ebc2e900a8ce34000928510be78af8aa",
"created_at": 1745938468,
"kind": 1,
"tags": [
[
"e",
"6144d64be9cb2ab8367f75c85c2261e7fe2be8ff8c7709ddc6374ed0a1aa5d86",
"wss://nostr.mom/",
"root",
"619af6a60b3fe4c733aaca061c522cc9c7cf1d87ef4c908facc5ed936d3bdf23"
],
[
"e",
"6639b9c1ccc17e8531f0cf7d2f86009f0320b9e130c862360b1aeeab25c35893",
"wss://nostr.mom/",
"reply",
"8125b911ed0e94dbe3008a0be48cfe5cd0c0b05923cfff917ae7e87da8400883"
],
[
"p",
"619af6a60b3fe4c733aaca061c522cc9c7cf1d87ef4c908facc5ed936d3bdf23"
],
[
"p",
"8125b911ed0e94dbe3008a0be48cfe5cd0c0b05923cfff917ae7e87da8400883"
],
[
"client",
"jumble"
]
],
"content": "This is great, however things are not perfect.\n\nAmethyst does support it indeed, but somehow I can still see two users' profile notes in Amethyst, meanwhile in Jumble I can't. They are empty. Then I see the relays are onion only, probably set by the user outbox preferences.\n\nTheir outbox should be preferred, not limited to. If can't connect to it, try another relay list, probably set by Jumble's custom settings instead of giving up fetching notes from those profiles. That would do it.\n\nWhy can I fetch those users' notes from their profile using Amethyst and can't from Jumble? Both use outbox relays model. If the user has set on their npub their outbox relays, it doesn't mean I should be forced to use their list. What if I don't like to connect to some relays of that list, but I still want to see their profile?\n\nThe outbox relay list should be just a tip, not a law. I still want to fetch this user notes from the relays I choose, but I can't in jumble. I want control over which relays I stablish a connection to. To see their profile notes I must use other client, as I couldn't access from tor, probably due to the relays from their list being inaccessible at the moment.\n\nI should say I find fallback relay list OK. It'll not hurt in any sense decentralisation as it'd be just a fallback you can easily change, either hard coded or from a settings page for Jumble's next release.\n\nJust saying, that should be enough to display their profile as not empty. Jumble is meant to be user-friendly, based on the GitHub project description.",
"sig": "3d3e90790df20bc62f096f01b8119cfcc1372d53a510287554793290f310ccf5d56feba59602cd153b7bb4d4a11b595177c0eb87094d5789b1a1110e1b561f95"
}