This isn't personal Derek Ross (nprofile…0hy6), it's simply a different architectural approach to Nostr:
Correct me if I'm wrong: Plektos uses NIP-52:
👉 Native, interoperable calendar events across clients
👉 Limited to basic RSVP + metadata
nprofile1qyghwue69uhkuvmcvghxjme6xucrqvqpp3mhxue69uhkyunz9e5k7qpq5xd2mmjnh3caykh77djsv73e0zkrp42jp5mwerx8f4m6su40wdvsrlysyl (nprofile…ysyl) takes a different route:
👉 Uses Nostr for identity/sign-in
👉 Builds a fully-featured events platform on top
That design choice allows Satlantis to offer things that are currently outside the scope of NIP-52, such as:
✔️ Ticketing in BTC & fiat.
✔️ Advanced attendee management (all NIP-52 features + guests check-in, co-hosting, auto-follow...)
✔️ Growth and distribution tools for organizers (guest invites via Nostr & email, Nostr dms, calendars, newsletters, email marketing campaigns...)
✔️ Custodial Lightning wallet for every user.
So, to answer to your question: if you are expecting to see all events from Plektos (or any other Nostr calendar client) on Satlantis, it won't work, because they use Nostr differently.
jordi / Jordi Llonch Esteve
npub138…3zeru
2026-03-27 18:17:51 UTC
in reply to nevent1q…ry25
Author Public Key
npub138lktp328xjqvs45zysswzjxu4gxj58uypmlt486nxhek3dry8vsf3zeruSeen on
wss://relay.ditto.pubPublished at
2026-03-27 18:17:51 UTCEvent JSON
{
"id": "9f94861ec58877ddc05627cce7d5755b017085b2b470c4728ddf57b664509c3d",
"pubkey": "89ff65862a39a40642b41121070a46e5506950fc2077f5d4fa99af9b45a321d9",
"created_at": 1774635471,
"kind": 1,
"tags": [
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24",
"wss://nos.lol",
"mention"
],
[
"p",
"a19aadee53bc71d25afef365067a3978ac30d5520d36ec8cc74d77a872af7359",
"ws://n3xb.io:7000",
"mention"
],
[
"e",
"8addb22b861d47dc059e24312acf6708e865d23dfffcfe991a24a9e15394fb82",
"",
"root",
"532d830dffe09c13e75e8b145c825718fc12b0003f61d61e9077721c7fff93cb"
],
[
"e",
"9b2baec48af5ce8c095d3f62d91de6f97cb06d802e61f789514d87be321cf621",
"",
"reply"
],
[
"p",
"a19aadee53bc71d25afef365067a3978ac30d5520d36ec8cc74d77a872af7359"
],
[
"p",
"89ff65862a39a40642b41121070a46e5506950fc2077f5d4fa99af9b45a321d9"
],
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24"
],
[
"p",
"532d830dffe09c13e75e8b145c825718fc12b0003f61d61e9077721c7fff93cb"
],
[
"p",
"604e96e099936a104883958b040b47672e0f048c98ac793f37ffe4c720279eb2"
],
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://nostr.mom/"
],
[
"r",
"wss://nostr.bitcoiner.social/"
],
[
"r",
"wss://no.str.cr/",
"write"
],
[
"r",
"wss://relay.damus.io/"
],
[
"client",
"Primal Web"
]
],
"content": "This isn't personal nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqy08wumn8ghj7mn0wd68yttjv4kxz7fwv3jhyettwfhhxuewd4jsqgplwuxkt5a8vj5utj6s8tsj8e3wcavc45p4mqmw92qs7wrh5azmys9f0hy6, it's simply a different architectural approach to Nostr:\n\nCorrect me if I'm wrong: Plektos uses NIP-52:\n👉 Native, interoperable calendar events across clients\n👉 Limited to basic RSVP + metadata\n\nnostr:nprofile1qyghwue69uhkuvmcvghxjme6xucrqvqpp3mhxue69uhkyunz9e5k7qpq5xd2mmjnh3caykh77djsv73e0zkrp42jp5mwerx8f4m6su40wdvsrlysyl takes a different route:\n👉 Uses Nostr for identity/sign-in\n👉 Builds a fully-featured events platform on top\n\nThat design choice allows Satlantis to offer things that are currently outside the scope of NIP-52, such as:\n✔️ Ticketing in BTC \u0026 fiat.\n✔️ Advanced attendee management (all NIP-52 features + guests check-in, co-hosting, auto-follow...)\n✔️ Growth and distribution tools for organizers (guest invites via Nostr \u0026 email, Nostr dms, calendars, newsletters, email marketing campaigns...)\n✔️ Custodial Lightning wallet for every user.\n\nSo, to answer to your question: if you are expecting to see all events from Plektos (or any other Nostr calendar client) on Satlantis, it won't work, because they use Nostr differently.",
"sig": "e259f86345e84d463124f2ec41b7e414f87646ca04b4bf436b0392609112d6fb289d285b501fbd35c9afe0c4373d6f3bcb73569d8b9d931390a495646d8a2e1a"
}