I guess I'm one of those #vtubers. Having fun talking about general topics, vrchat/similar, and games. Also #indiedev #gamedev. You can call me: Freak فْرِيكٌ フリク (still learning Nihongo). Making: DEG Mods, DEGA, DNN, DENOS #envtuber #podcast #gaming #gamedev #freedomtech
Public Key
npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Profile Code
nprofile1qqsre6jgq6c7r2vzn5cdtju20qq36sn3cer5avc4x8kfru5pzrlr7sqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0ds5wueyd
Show more details
Published at
2026-03-13T10:22:31+01:00 Event JSON
{
"id": "dcb0f65f1fe81b7c655024c1825ffce227ab85433367b96f52a42172ff6f4725" ,
"pubkey": "3cea4806b1e1a9829d30d5cb8a78011d4271c6474eb31531ec91f28110fe3f40" ,
"created_at": 1773393751 ,
"kind": 0 ,
"tags": [],
"content": "{\"name\":\"Freakoverse\",\"picture\":\"https://m.primal.net/HerC.png\",\"about\":\"I guess I'm one of those #vtubers.\\n\\nHaving fun talking about general topics, vrchat/similar, and games. Also #indiedev #gamedev. You can call me: Freak فْرِيكٌ フリク (still learning Nihongo).\\n\\nMaking: DEG Mods, DEGA, DNN, DENOS\\n\\n#envtuber #podcast #gaming #gamedev #freedomtech\",\"banner\":\"https://m.primal.net/HerB.png\",\"lud16\":\"[email protected] \",\"nip05\":\"nabandondelivera\",\"display_name\":\"Freakoverse\",\"displayName\":\"Freakoverse\",\"website\":\"\"}" ,
"sig": "7fff7ac0f38d5c3ddd768d7a6b946acd0066c198393e0257448f626ed108a19a080872c56c4c385c34e8026021b5b123d6f4e8c6fe22e367dd3fd8402435f8a7"
}
Last Notes npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Didn't announce the name yet, in case I change my mind last minute (x3, don't think I will though, testing it by chatting about it with friends seems natural with a good branding) It'll be announced soon probably, almost done with the permissions/roles stuff and creator/mod bans, after that it's medium to small stuff left. Also need to make things clearer with notes clearly shown in places where stuff isn't encrypted (like media uploads). After that, building the promo/landing page. The name is similar to what most of the things i've made/making and named so far (DEG Mods, DEGA, DENOS, DNN, DEMIN), so it'll definitely start with a 'D' x3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Ideally if I'd go with just bitcoin (or second best usdt too), but the fiat part is for those who want a solution with that. Regarding PPs wanting to interfere, they'll try, but they won't be able to stop it, because it'll be a normal flow with their system, as in a normal company setting up a payment gateway for their own accounts. There won't be a middleman (like steam/gog) to centrally attack, and there's no special system, it's just nostr in the background managing this flow that's it. With that said / meaning, if visa/mastercard/etc come to me and say 'stop selling these set of games or we'll freeze your account', my response would be 'i'm not selling it, talk to the seller, i'm just a browser not a middleman' and in case they do unjustly freeze my account, it would not affect any seller, unlike all other platforms which would result in their instantly failure and bankrupcy. So they have to go after each individual seller to stop the sale of a single product, and even if they do, the seller would simply swap to a different payment system and that'd be that. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Aye, it's really weird to me when someone tells me "this thing you're make are bad/dangerous for x reasons that will result in y consequences for everyone, you shouldn't do it", and in my head i'm thinking "if me, a neautral or good-willing creator, makes something that is bad/dangerous for others, and the first reaction is for me to get told not to do it, instead of solving it, then this is a ticking time-bomb for malicious users/creators to harm people without heeding any 'you shouldn't do it' suggestions =/" If there's a problem, solve it, don't sweep it under the rug, and be glad that a good-natured person, not a malicious one, shed light on the supposed problem that might work with you to help solve it. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Never used it, but also yea, this is while I'd eventually want to make a marketplace of people running blossom servers where people pay others to keep the maintaining a specific file (imagine each file has 'fuel' that people see), as well as ads (ads 2.0 i'd want to build) where people see them when they want to download a file to also help maintain the file, all hash verified for tamper-resistance. Will some files disapear? Of course, but that's a result of either A people actually don't care about it enough to either download it (watch an ad or two), or pay to help maintain it, or someone not wanting to go probono to maintain it, but with this system, the chances of stuff remaining online is much higher because of an economic system being there. When will this happen? dunno x3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse For me, this is quick funzies/neat and other project and business usecases, is why i implemented this on my stuff, and I agree it's important to mention to the users the public-ness of this and its potential implications, however, this is also a 'step 1' of a two-stop goal, for me at least, where the other step is 'nostr silent payments (nsp)', so there'd be an option to send to a random address controlled by the receiver. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Yup, though that's why there should also be a check if "what's the recepient's relays?" and only present the qr/address after that has been determined (perhaps with 2-3 fetches from different sources to make sure), otherwise the address wouldn't be derived, or it would but perhaps with clear warnings. Relay discovery is always an issue with nostr, so I'd go with the former. Aside from that current flow that everyone would know, for DNN ID holders (the thing I made), user relay discovery is solved (do a call, you get the receiver's relays, done). Though there's always a fail scenario, both normally and even through DNN, is if the user's relays, even if found, are dead, that's one edge-case, in which case there'd also needs to be a check 'are these relays alive?' along with the first question before anything is generated/presented. With all of that said though, we'd also add more measures on the sender's side as well for recovery/reminding flows and more, but generally speaking, aside from doing the best we can to reduce failure rates, we'd also just be upfront about things and make the user aware of the risks involved in general and what steps they can take for 'just in case' scenarios. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse it's been a while since i thought about it, but basically the client would derive a key based on a random tweak for the sender to send money to. Regarding notifying the receiver (so he doesn't face the same headache of the standard Bitcoin SP), either an automatic operation happens where the client would listen for an incoming transaction and once it gets confirmed then a ephemeral key would giftwrap send (new kind) with the nip44 encryption to the receiver the mentioning the address they received money on with the used random tweak (and for what i mean, the chain used). For a manual operation the user would need to click something like 'yes i've sent the transaction' (because there'd be no chain listening) and then it does the same steps. So in terms of privacy, the public knows (ish) that you're receiving money, but not from who or what or what amount. Only downside is if that automatic operation or manual never happens (technical or UX failure), then it would be assumed as if the sender sent it to the void, however, i did think of a optional fallback recovery hint, adding some info in op_return (squizing it to 40 bytes) where it would then start behaving like Bitcoin SP but only for recovery purposes. There can probably be better ways to recover from notification failure that can be thought of. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Nice. Saw you made a demo out of this months/years ago, which helped produce the idea of DNN (human-readable/memorable IDs and TLDs and solves a bunch of other problems and brings about a bunch of new opportunities), and as a result I also made a desktop (and remote) signer that also has a wallet where it derives a bitcoin (taproot and segwit) addresses to receive/send with, along with recently deriving other compatible chains and utilizing their tokens. https://image.nostr.build/33dbcab84b219e8a0d3b35fc4df2c1f3a56570b1236636cf0bd01d7a4c31e5ab.jpg Later I'll also add what I'm calling Nostr Silent Payments (NSP) for all derived addresses of those different chains and their optional tokens. Then later multi-sig stuff and auto-payments/subscriptions (natively). npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse @npub1cgd…kfex hey, i imagine you were seeing a bunch of garbage text as a poll event here and there, this was from an implementation into a new client, that's a encrypted group chat, so polls are published through it but encrypted. There was no mention of a private poll flow, so that's how it is implemented in that client right now. I can keep it as is, and we'll see a bunch of polls that are gibbers with clients not being able to render them properly without a sort of check if it can be rendered, or perhaps the nip would be updated to consider something like a 'visibility' tag of sorts so clients can what to render or what not to render (not to render ones where the value would be 'hidden' for example, under the assumption that poll would be encrypted), or perhaps a whole new kind specifically for private-encrypted polls. Thoughts? npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse With the discord alt i'm making that'll release soon, hopefully that'll bring it a shitton more gamers and gamedevs and game artists to nostr, as it also has social parts to it (a dedicated tab/page for kind:1 posts like here, and a dedicated tab for public chat, and i may add a dedicated tab for forum posts reddit+traditional-like posting), packaged alongside the private community part of group chatting, so the hope is because of all of this, it'll sky-rocket the number of these types of people on nostr and we'll have more fun on here =3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Japan is fucking back baby xD https://image.nostr.build/5195c47d8014c13e5efb9fbf875196806f1954e74ce67ad9db530983a8235b42.jpg npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse https://video.nostr.build/43251fe510e7f1d2309c548772a6cf56e70d5feaf06bb4e6390fd94a84191fab.mp4 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse DNN fixed, you can play with DNN IDs in denos now = ) npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Multi-chain, multi-token, native and token currencies on nostr, not set up required, just have an npub https://video.nostr.build/7fb7bf62a059e5617ab7c73e105a3a0094fdfda19c8d38f5d2ec446da37db63c.mp4 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I'm hoping with DEGA, over time as the system gets added and more people interact with it, I'd have the public get used to the idea of "if you bought a game from a different platform/store on PC, you'll see be able to play it on DEGA as if you bought it there" (within limits of course to what's possible, considering online games and such). What I'm also hoping to be the norm, is "if you bought a game on one system that's no on PC, you can play it on your PC on DEGA", which would be more difficult and both actually are something non-normies would do, but the idea is that they could. The actual idea of what I'm trying to get at isn't the technicalities, but rather the belief of "I already bought the game, I shouldn't be restricted to a platform or hardware, and I'm not a bad person if I manage to make it work on other platforms or systems, and help other legitamate buyers do it, as it is my right (of logic) to do so" npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I feel like nostr can help speed things up for monero, similar to how i'd use it (eventually when i make it) to speed things up for bitcoin and other crypto similar to bitcoin's signature structure, though because monero is very strict about privacy, whatever the nostr-aid solution would be, it needs to adher to privacy/annonymity standard. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Controlled retardation is a great skill to have, get it x3 https://image.nostr.build/0cb1e419585687332eef2ea0cd96fdfbc83eccdd0560c409c4e02dcc754d80ab.jpg npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Neuralink + AI will be wild x3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Apparently this is a thing now xD (didn't try) https://github.com/GitFrog1111/badclaude https://video.nostr.build/8732877b1f299f9082ba3001d459a2a3e2a9eea880a70b97d749b5cda91d86a8.mp4 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Because relays, from my understanding and experience, aren't built to propagate (discover other relays, store relay addresses, share them with other relays, store and push specific data/events). My relay list is in r1, r2, r3 Someone has my npub in their follow list, and they're looking at relays r4, r5, r6 (and the relays in my relay list aren't the same as that someone) They won't see my posts. --- DNN nodes propogate data with each other (only specific events, one of which would include relays an npub posts to). So assuming I have acquired a DNN ID (meaning my npub is in DNN nodes where they'd fetch and propogate data/events), then when someone follows me/npub, the client would fetch the data from a dnn node of where I'd post to and check those relays > they'd see my posts. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Mainly this link: https://git.nostrdev.com/freakoverse/DNN The docs are there, other than that, this note:#nevent1q…cx4t npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse On my end I've solved the relay discovery and and centralization issue by piggybacking on the ICANN-DNS solution I made (DNN). At the cost of a one-time self-transfer (1 sat v/byte). A decentralized network of these DNN nodes that's used for various DNS purposes, which propagate with each other, hold each user's relay list (and it wouldn't matter if they're popular or not), and users just fetch said relays of the people they follow and the local relay list gets built and you wouldn't miss any of their events. Users would then not worry about needing to post in popular relays so they post to wherever else. (There are other benefits, like no more npubs or the reliance on traditionl fragile domains for nip-05, spam resistant, WoT increase, and more). npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse bro do you even freedom lift? x3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse A bit of anime (Slime, An Observation Log of My Fiancée Who Calls Herself a Villainess) A bit of game (Farlight 84) A lot of Discord alt work =3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Would be neat if at some point there'd be a marketplace on #nostr where people present and rent out a SFU+TURN servers, pay with bitcoin/lightning and other, so I'd present it easily to users on my discord alt. Still exploring/testing my options with this, but I'm adding the following options for the moment: - Centralized: Cloudflare Realtime (free 1k GB bandwidth per month) - Decentralized: Livekit self-host - Future: Marketplace of SFU+TURN servers npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Got a server running or are IPs of participants exposed (assuming they aren't running a vpn or tor?) npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse p2p right? how is hiding IPs of participants handled (if it's being handeled)? npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse p2p? I want to do the same but I don't want to expose the IPs of participants to each other (right now i'm thinking if i can do 1 tor hop) npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse NO, YOU GET A HUG EMOJI + IMAGINE I GAVE YOU A BOX OF HUMMUS x3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse The moment the retro anime gifs stop being posted, is the moment that becomes a real question npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Dunno, perhaps they're just 'normal' people that talk about... i dunno, food? x3 But I'm hoping with the release and marketing push for the discord alt i'm making, we'd fine more of weeb/gamer/gamedev culture in nostr in a social sense =3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Only if they can't be turned off. It's also for the normies + even for advanced users for a no-setup-flow Turning off client servers and user servers should-to-must be possible, and if they get them all turned off then a warning appears "hey, turning all this shit off from the client side and yours will pretty much break things, but hey, u do u we're assuming you're an advanced user at this point and know what you're doing" npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I hope clients are doing multi-server uploads to media files (like random 3 for example, across client list and user list and etc) for redudancy, also doing failover to another server if one fails (or the following), and do hash checks (becomes some like to change the file but keep the hash ID apparently) so on mismatch it considers that a fail so either it tries another server or if it doesn't find the file then give an appropriate error (perhaps even a flow to reupload/fix it if they have the same file still). I've been doing that for my clients/tools. #nostr #blossom npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Best I can do for now is this stock image I found on online x3 https://image.nostr.build/fb69bf5a14fcdd886d4d0711f004fcffe25b78b1b601f6765ab31b4b5353fdb2.jpg npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Almost done with the discord proper freedom alt (public testing probably sometime next month), at least the text chat version. With that said, any 'i wish discord had...' or 'i wish discord didn't...' etc? npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse So what you're saying... I won't have to fear subscription prices going from around $200 to $2k+? x3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I was NOT expecting this game to be $60, maybe like $40, max $50 https://store.steampowered.com/app/2814990/Screamer/ But who knows maybe it is worth $60 on launch npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse There was a major flaw in the cryptography, but a solution was figured out that retains determinism + ownership + public verification of both. And because of this fix + because of processing scalability critism, client implementation and rotation verification processing is now not heavy weight (light weight processing depending on implementation decisions). This is now solid =3 #nevent1q…ymu0 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Aye I know about it, and thought about it but ended up starting from zero as doing it full nostr style pretty much changes almost the whole flow and assumptions, so i thought it'd be better to start clean. With that said, I'm almost done =3 (side note: not using MLS, that was overkill for a discord alt) npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Had a nice discussion with a friend that is generally interested in cryptography, and as a result, I fixed a few issues with the spec and deepend my understanding of it as well, very productive =3 Also, added more text to showcase its flexibility as a tool rather than a full client implementation. NIP-DKR: Deterministic Key Rotation https://git.nostrdev.com/freakoverse/DNN/src/branch/main/docs/NIPS/NIP-DKR.md (also yes, i figured out a way now, regarding when i said before that it was impossible / i've hit a wall / i gave up. Didn't give up, and now there's a solution, my standard was achieved =3 Properly achieved once I've made a reference implementation at some point, perhaps one example demo or actually implement it in DENOS the signer and the jumble fork) #nostr #dkr npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Damn, she's MEGAN 4.6 xD npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Considering what I figured out with NSP (Nostr Silent Payments), I'm not worried about this (as in i'm not worried about an authority of some kind freezing an address, because there wouldn't be a static address through a normal payment flow through NSP).#nevent1q…6t8e npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Assuming I'm not wrong (and hopefully not x3 because this would be gold then), I've figured something out: Nostr Deterministic Keypair Rotation (didn't make a reference implementation yet) Keypair rotation without a trust-me announcement, all deterministic/verifiable https://git.nostrdev.com/freakoverse/DNN/src/branch/main/docs/NIPS/NIP-DKR.md npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse https://git.nostrdev.com/freakoverse/DNN/src/branch/main/docs/NIPS/NIP-DKR.md npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse The wolp's friend-in-the-head is on the side of hoomans x3 https://image.nostr.build/e979810c1b595c53167db140c042a909101ada40f16cc434cb080b1a5701f9f3.png npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Vicar Amelia npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Actually, I agree. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I might have figured something out...! Will write/publish something later and share it to get thoughts on it#nevent1q…40ej npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Tried it. Whoever is making it, please continuing making/improving it, it's amazing! =3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I'm guessing by next week i'd do public testing of the discord alt (at least web view, hoping for pc clients as well) npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse My nsec is safe apparently x3 https://image.nostr.build/0e9a05fea08220b7c86519326fdb97aa115c1297aec61f4cf430628e7cfdfb46.gif npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I tried so hard for 1-3 days trying to figure out a deterministicly publicly verifiable way to rotate keys (without making a 'trust me' announcement/decleration post) without putting a parent key at risk because of child leaks, but couldn't figure out a solution x3 Now as I type this, an idea came into my head i'll juggle... but i'm assuming I won't reach an answer (but hey, won't hurt to think about it for a bit and try, who knows x3) npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Ok cool cool, my nsec didn't leak x3 https://image.nostr.build/3893ee40ae34f1a5440f333a267f29170baec1562644f8031e1899f68ad5b12d.jpg npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Another reason to show why I'm building DEGA and the infra around it https://www.patreon.com/posts/steam-destroyed-152121823 https://image.nostr.build/1f83a94dfcc9d9a1580eddf8649a0532e597032438dc632860f8aafc87a65154.png npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse It's not that one has a better product, it's that it should be overwhelmingly better than whatever current product the users currently have 'and' said current product is getting enshitified at a decent pace that even its general users are getting tired/sick of it. (This is why I choose to develop the products i'm building and trying to make them a success) While yes before when things were slow, "ooooh, new shiny thing!" was more apparent because of the rarity of options, so you'd get an initial bump of users, but general the first thing mentioned above is usually the case imo. There's also the mentality of "i developed this fast and its good, i should market it fast and i'll be successful fast" that came as a result of how fast we're developing products now, when in reality the goal of reaching a sustainable business (aside from the development of the product part) has not sped up, in fact it has slowed down as a result of what you mentioned (basically increased competition) so you still have to go through the normal hoops and effort overtime to accomplish having a successful business out of a product. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Alright... thought of / planned out what I think would be the best structure/flow for a discord alt, time for implementing it then testing to see if it'll turn out to be good or not. Took me some time to realize "wait a minute, i'm not making signal and the like, a bunch are already doing that, i'm making discord, why am i trying to achieve a higher standard than I should?" and continued with that mindset / its underlying assumptions. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse neat. would be pretty neat as well if there was a service out there that either allows users to check if their nsec has been leaked somehow, or even the service DM affected users about the leak with partial proof to alert them. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Got my ICANN-DNS alt working, and aside from improving it and hitting up internet browser teams, I (and all who would use it) now have an option to tell my users to visit a freedom domain rather than a traditional one, if things go wrong and they take my traditional domain away, where nobody can take that domain away or ask me for any information or require permission from someone, and it's human-readable/memorable too. https://video.nostr.build/43921e1b0338d017fdae92a11b36a2cd0a0b4755d6ad70082f79f39cc2d9b22b.mp4 It's nostr+bitcoin based (without adding anything to bitcoin). Hit me up you're interested to learn more / happy to talk about it and/or help =3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Realistically? To be part of a set of relays (in partnership with other clients that do this as well) where members only can write into it and the public can read from it. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Golf is fun again =3 https://store.steampowered.com/app/4069520/Super_Battle_Golf/ https://video.nostr.build/d9145e30ed32bf5bfdf579d5abf4222781a82aa0eebb6ea4423bc0f720555da0.mp4 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Sounds good. Applied 🤘 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Just a quickie https://video.nostr.build/ca29b25b8c4770a3cc52300c749b7f0b984d1652096732a50209a66736dbdb82.mp4 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse kind of understand it, but i don't kind of care for it x3 Let's go with "the sweat is real!" x3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse https://image.nostr.build/7d20cd58f4bd30e454151b0b4674c84820a5488a0aec25fa45048986450c87c7.jpg npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Another "free speech" platform with invite codes x3 https://image.nostr.build/6add3762849e31a0c5b71f8c9cab925565351c45d8cb6c56c1089897f0a88ea7.jpg npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse What's good about new stuff is that it's varying degrees of being magical, but what I'm hoping for, that we won't repeat the same mistake again from the past, is to make the infra not-centralized, at least not completely, so that we'd start to work unbelievably hard again to decentralize it. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse 1. sorry that happened 2. now i'm thinking of a comic "i'm a human rights activist, and here's a taste of the first rule of human rights *punch*, which is that you don't have rights" 3. i'm sorry x3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse i have finished Get To Work I enjoyed playing it =3 (and i finshed-finished it, also got the hat, but not the second hat x3) https://store.steampowered.com/app/2706170/Get_To_Work/ npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Had a similar thought a few days ago. Gist: Don't put much energy into convincing sheep/slaves to become aware/free, but rather make stuff for them to take advantage of them to benefit those who want to be aware/free, or are aware/free. This would result in an all around benefit for all (to the best that one can do. You can't 'force' someone to be aware/free, so that is the limit of what one can and should do.) (typo at the end, meant to say: "solutions for the sheep *where we'd* utilize") #nevent1q…ear3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse - Brought back 'username and password' on nostr, evolved. - PC nostr signer (remote and local), lookin good, because screw makin on on mobile those are caged machines x3 - No need for any setup after keypair generation, start receiving eCash/Lightning, native bitcoin, and (soon) native other cryptos (secp256k1 based only), and no-scanning bitcoin (and other) silent payments, social native bitcoin (and other) sending, and easy multisig flow. - encoded an npub (63 chars of gibberish) to something human-readable/memorable/usable/locally-meaningful (8-16 chars), which also acts as a TLD, and also helps solves day-0 WoT problem, relay discovery and centralization problem too, as well as no need for a CA, and more. - Shortened event addresses (from 150-260 chars to 18-26 chars) #nevent1q…qjdr npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse DNN node code up: https://github.com/Freakoverse/dnn-node (check the DEPLOYMENT.md for installation on a linux server) Here's a quick video guide to installing one on a linux server: https://files.catbox.moe/ez977u.mp4 It's probably rough af and messy, but it's better to put something out there to play around with and improve as time goes on. (I'd honestly want to refactoring everything from the start, but that'd waste a lot of time and not having something out there for others to check isn't a good thing imo) You can read about the DNN project (read me and node-policy) and its NIPs (specifically NIP-DN) here: https://git.nostrdev.com/freakoverse/DNN Couldn't be at #soveng unfortunately for SEC-06 (Identity) and SEC-07 (Network, ICANN DNS/IANA), this project pretty much fits for both cohorts. Identity & Signers (SEC-06): I made a desktop signer, DENOS, that's basically the user's nostr identity manager, that's also a wallet manager (eCash, focusing on nutzap management, and native bitcoin with both native segwit and taproot for two different purposes, DNN ID/TLD acquisition & management, local signing flow and a username/password sign-in flow, and later down the line I'd add what I'm calling Nostr Silent Payments (multi-currency, Bitcoin multisig but with good/clear UX, and a merchant e-commerce POS system (that includes traditional fiat payments). When a new user comes and generates a nostr keypair, they don't have to do anything else aside from that and you can immediatly send them eCash (nutzap focused, so no heavy token management), native bitcoin, or (later) other crypto and their tokens. And if they grab a DNN ID, aside from turning their npub (63 chars of gibberish) into a human-readable/memorable/usable/locally-meaningful ID (8-16 chars), it would also decently add to their WoT score from day 0. The Network Stack (SEC-07): There's a lot here, but focused on the ICANN-DNS problem as well as the Certificate Authority problem. With DNN, you can now have https://example.nabandonaread or https://example.naboutzook , where you acquire a Top-Level Domain (TLD) by sending yourself bitcoin from your bitcoin address that was derived from your npub and publishing a few events (DENOS has this function / as easy as it can be), and after acquring a TLD, you can have many domains at no extra cost. Forever yours, no requiring payments, no auctions, no fomo, and no trading, as simple and as fast and as cost-effect as it can be, and scales well (and it doesn't add anything to Bitcoin). SSL/TLS doesn't require CA as well, the cert would be self-signed (still secure) and you can put a thousand year validity if you want (set and forget). It should also be prepped (i hope, didn't do much testing on this part) for a Tollgate and FIPS future. Other: DNN solves other problems as well, secondary-effect benefits: - Nostr relay discovery problem (solves missing posts/messages, etc) - Relay centralization (no need to post or read from popular relays) - Impersonations (easily identify the correct person to follow) - Long event addresses (shorten event post from 150-260 chars to 18-26 chars) - Unfamiliar login flow (bringing back traditional username/password login flow, but evovled) - More Hit me up with any questions/feedback/topics, publically or privately, text or call (or in VRC, that would be fun y not x3) about any of this, especially if you want to implement DNN support in your nostr client (I forked Jumble and added support for it there, including some of the other benefits/NIPs like username/password login, local signer login, ID resolution, event addressing shortening, but forgot to add node query for user relay to be utilized so perhaps later), check it out: https://jdnn.top/ #nostr #DNS #ICANN npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Nice Had a similar idea a while ago but didn't get around to implement it yet. https://git.nostrdev.com/freakoverse/DNN/src/branch/main/docs/NIPS/NIP-NSP.md Though working on different assumptions than what you've build. instead of having an npub publish a SP address, no one does anything, the sender derives an bitcoin address (or any secp256k1-based crypto) from the receiver's npub and sends to him and then notifies him via a nostr event. https://image.nostr.build/63453e6d17f65db045f752bedd5f3b079068670d11ce6e84b909564397dc8730.jpg npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Good discussion about NIP-29. My opinion of it change from "wtf is this?" based on misunderstood assumptions, to "ok it's not that worrying". Would I use it as it currently is? Depending on what I want to make, and with the mentality of aiming at a target audience that want to 'self-host', then maybe. Would I use an altered version of it (if you read in the discussion what that is)? More towards yes in a general sense but hard to say still for me. For the Discord alt I'd build... there are pros in and cons for different approaches, in regards to reach that Discord quality of everything but with decentralization and censorship resistant / nostr in mind, NIP-29 or otherwise. I'll take a few days digesting everything to everything before seeing what I'd do. Leaning towards something custom but a mish-mash of things existing things... we'll see.#nevent1q…7r7j npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Aye this was a good discussion. I'm not sure if I'll go with NIP-29 as it is or not, or go with something custom, or perhaps a meshmash of things (and present the user with "here are your options with their pros/cons"), to eventually reach discord's level of service, all the while considering the nature of nostr, is definitely a challenge, with different trade-offs depending on what's chosen. It's definitely worth exploring different solutions i'd say, where a bunch would make products based on NIP-29 and advance it, others might build on top of a modified NIP-29, others might try something completely different, and I guess we'll see how it fares as we play with all of them and see what works best in practice. I'll probably spend a few days thinking what I'll do on my end, digesting this discussion before moving forward. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse dumb relay, dumb client, dumb user Chaos! https://image.nostr.build/cb80b01b9e920f8e23ff467a36cc03516a6bd752674e9ccf17cef57090a5854d.gif npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse The reason why I suggested having the pubkey in the d tag is because I'm following along with NIP-29's flow of having the relay as the enforcer/manager keypair, because without that (the pubkey in the d tag and doing a check) then a malicious user create a group a group event with the same d tag then have it everywhere, hogging relays wherever they can which prevents the normal users from having their created group be on other relays as a result of each of the other relays' keypair utilizing the same d tag by the malicious user, resulting in a centralization chocking attack (now that specific group is stuck in the relay or to a small few options, where the only solution now is to create a completely new group). I'm basically trying to push for increasing decentralization as much as I can with the benefits of control brought in by NIP-29's management goals. The desire to have multiple admins that are equal to each other without a creator/super-admin is more complex than having a creator/super-admin above those multiple admins, as that raises the question of who should the relays listen to when there's a dispute? We'd either end up having chaotic battles of constant back and forth changes, or there needs to be a voting system for consensus, and the other issue is if one admin wants to kick another admin, is that respected? what system should handle this? I hope I managed to explain well what the issues of not having a creator/super-admin that relays listen to as the final authority. It's not that there can't be equal admins, but that there must be a super admin (creator) above them to not have such complexities and potentials issues. If there's a desire to fork the group, then that can be done by just mentioning the original group id (d tag) under a new tag, when the new creator publishes their group, and the relay grabs the relavent events. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse If I had to gist each... One piece villians (at least those) (if i'm thinking right): "I'm just evil" (regardless of backstory, those chose to be dicks x3) Bleach (again, if i'm thinking right): "fuck those in power"(aside from Ulquiorra? he's his own thing x3) Naruto: "i suffered in the past, so i'll end the worlds' suffering by force" (aside from Orochimaru, he wants to break life's limits and hungry for power, trying to achieve them by any means necessary) npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse So it seems like things could work with NIP-29 for me (and others?) to build on it, but a bit of changes would be needed in my opinion: I don't see how it's good not to have a link to the practical (actual) creator of a group. The relay can remain an 'action' authority, but the creator needs to act as the higher/'actual' authority as a link of sorts. Meaning I'd publish the creation event (mandetory, not optional, and if privacy is a concern then a deterministic derivation from the creator's pubkey can be used) and whatever i change with the rules, or who is allowed to change the rules (admins, moderators) is published by me, and the relay enforces them. This gives a proper view of who controls what, and it would be visible if a relay misbehaves / becomes malicious (if the relay changes the rules and does other enforcements that they creator did not publish, then it reveals for everyone that the relay is misbehaving / is malicious). Regarding the d tag, it shouldn't be <host>'<group-id> but rather <creator-pubkey>'<group-id> where relays must not create a group without seeing a creation event with that same d tag published by the same author as <creator-pubkey>, this prevents a malicious user(s) from preventing a creator from migrating their group from one relay to another because of d tag colision. The cost of doing this, however, is that it would not allow the functionality of forking a group, but that can easily happen fixed by adding a tag to tell relays "this is a forked group, so grab grab posts with this d tag as well". With that in mind, the h tag would also have to have the <creator-pubkey>'<group-id> value. Considering the removal of <host> from the d-tag, we'd utilize the order of the r tag to identify the current relay authority, if that even matters, where we can just have multiple authorities ("enforced") considering that we'd now have the 'actual' authority being the creator. That [private] part is a protection from the general public, but not from the relays, so the solution here is tree encryption / mls-ish (optional). No new kinds, just tweaking the flows and assumptions. This gives power to the user/creator, while complexity and processing remains with relays and enforcement remains on the relay side as well, and there wouldn't need to be a 'migration' because of this anymore, you'd just add/remove relays from the creation event and rebroadcast events. To me this seems like the best of both worlds, but perhaps i'm not seeing something or have misunderstood aspects of it. Thoughts @npub107j…ncxg @npub180c…h6w6 @npub149p…722q ? npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Took a bit of time to understand what you said in the quoted post, and I think I understand now where you're comming from regarding the design of NIP-29, where the best management and moderation flows happen on a centralized system, but when other protocols tried to do that but in a decentralized manner, they still end up with the flaws of centralization, but because of nostr's unique structure, it allows the possibility of migration from the original relay to another, in case it shuts down or starts censoring the group. Most other protocols (or all?) can't easily do this in comparison. I understand the logic of where you're coming from now, and I'm not against it, however... I guess I would be more of a fan of NIP-29 if there was a good flow for migration steps, and more so if there was less dependancy on one relay (so a group would post on 2-5 relays that enforce admin policies) and decoupling the relay address from the group address. I think at that point I'd be happy to use NIP-29. (and in regards to actual privacy, so not even the relay knows about the content of the group posts, we'd have that tree-based encryption, so i guess no worries there, it wouldn't be that high of a cost even at scale) Also, yes you're correct that what I thought of (or what Niel linked to) has high processing, where the bigger the group the bigger the procesing needs to be done on the client side and that is definitely an issue. I guess that's the cost of if we want to persue the core nostr flow that has been done for most NIPs and what most people love about it. (Moderation management with shared pseudo-powers can be done here, but yea, more client-side processing as a result, and full final actual moderation is done by the creator of the group) I'll explore and think about NIP-29, to understand it more properly but to also see how can it be adjust to improve the hiccups i see in it (addressing the part where i said "I would be more of a fan of NIP-29" in this same post). Basically lossening up NIP-29 a bit more (probably not the correct wording here but i'm hoping I'm understood) would probably make those that don't like it reverse their thoughts on it and embrace it. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Based on my understanding of NIP-29, one thing I didn't like about it is if the relay goes then the created hub goes with it. If the relay doesn't like the hub I created, then they'd just block it and then i have to create the same hub again on a differen't relay as the new home. I'm relay hoping my hub now basically. Unless I misunderstood how NIP-29, that's how I'm seeing it at the moment. In regards to how I'm planning to build that Discord alt differently, when you make a hub, it's an event with relay hints inside it (multiples), and posts reference the hub ID and push posts to those hint relays. For moderation, it'd be based on whitelists and/or blacklists, or rather depending on the hub structure then basically a 'access control' list (in regards to encryption / what can be seen, tree-like access tokens / similar to how MLS works if i remember right), basically client side showing/hiding based on access control list, and encryption/decryption based on who's in the tree and then token always gets updated everytime the tree gets updated and participants would know/get informed of the token. I hope I explained things well, sorry if I didn't. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I figured out how to word my dislike of most turn-based games: Aside from being generally boring to play, there is barely any or no skill involved to the gameplay (keep in mind i said "most turn-based games"). Persona, for example, you can't do decent damage? You're dead. Elden Ring, even if you're naked with one HP and the beginner sword, you can finish the game if you're skilled and patient enough. An example of turn-based games where good skill is involved (unless you're a robot?) where it's not just bigger number = better, that'd be Chess. Another example, though i haven't played it yet, that leans away from no-skill-turn-based, seems like it'd be Expedition 33. #gaming npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Seems like there's discourse with NIP-29 again? Yea it's still bad, at least in the sense of building a product for the general public. I think I don't like it because it makes me thing of ActivityPub/Mastodon (it's not it, but it's decently leaning towards it). The Discord alt I'll be building won't follow this NIP at all.#nevent1q…c0fm npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Had a quick discussion with a friend that recently got into #nostr and provided me with their experience, where he didn't mind the technical hiccups, the shit UX here and there, what he really minded was not finding people to follow that were sharing things he can relate to, where a lot of what he found were people mostly talking about nostr and bitcoin. Basically the same feedback all nostr devs get most of the time. However, the solution most devs get wrong is not, imo, the correct one, where they've made lists of various topics to follow specific people, different types of algos, etc. The solution I told him (and the public whoever is reading this now) are a few things: - Wait and see when companies you're interested in to say "follow us on nostr", where you'd then follow them, see their post, interact with them and interact with others that reply in their posts, and check with those people that are replying to see if they post stuff that interest you and follow them if it passes your interest threshold. - Use nostr products that are of specific industries or topics, where you'd specifically see posts about those industries or topics. - Lastly, use hashtags of things you might be interested in, in terms of search and posting as well (someone might follow you as a result of searching for that hashtag and you'd follow them back if it passes your interest threshold), where you'd search for posts with those hashtags and see who to follow based on their posts. That's how I've been using social media all my life to fill up my follow list enough that it keeps me entertained/satisfied with my feed experience, I did not rely on lists or algorythms at all (as i didn't see a need, not that i was against it, so it was useless to me). Regarding that second point, to expand on it with examples: Primal, Damus, Amythest, Jumble, or even DNN or DENOS that I made, etc, are products that don't bring in culture, they are just general tools or systems. DEG Mods and soon DEGA (game mods and games, games industry) and other things i'd build, as well as others (one that I know is about drinking wine / communities around that. Another is about anime/manga, etc), are cultural products that bring in specific types of people that share the same interests together. Because of the nature of nostr, cultural nostr products will be the driving force of filling the void of 'people to follow', along with the other two points i mentioned, that tool/system nostr products are missing. Building tool/system type products are very important for nostr, but building cultural type products are very important for nostr as well. If you're a dev, build what you want, but keep in mind the difference. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I WAS going to make a post about the DNN node release today, but discovered a bug while recording the installation guide and demoing a ID/TLD aqusition that needed to be fixed. Always demo presentations from A to Z The curse of demo day is always a blessing in disguise x3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse It's a result of a new protocol being built, based on nostr and bitcoin. Basically: from you npub a bitcoin address is derived, then you send yourself money (btc) from it, publish a few events (can be 1 click), and now you have a unique TLD where you can have many domains with at no extra cost forever. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Would this work? https://image.nostr.build/71e32f5cbe1572eee73e1383c31b2af7183f1d158952a41e79b558737b934977.jpg https://image.nostr.build/a60f3933ac360c5e2dd2cac64d2f01c9be508ef44e8c29fab951a9c48b05cb15.jpg https://image.nostr.build/ccabe2277673ceef03c8e2924b1831375836c420a8d8479fb1f051a411cf413f.jpg https://image.nostr.build/7176ec1bf5ddb97fa438fe90ce99ba03db2b91c53843027d57fed92ec3634784.jpg npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Being threatened via namecheap as well but for a different matter (A government is threatening me to take down a post). Will change registrars soon probably, something in Asia most likely. Hopefully I manage to get things rolling with my ICANN-DNS solution so that no one needs to worry about these kinds issues ever again =3 nostree.nareazook could be the potential future domain for example =) npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse As far as I'm concerned, in regards to not seeing reactions / replies almost fully, this is mostly solved through the solution I've made (the cost: an actual cost of a self-transfer on bitcoin), that's a secondary solution to the main problem it solved. The issue: You make a post on one relay, some people may reply on a different relay (assuming they even saw the post in the first place). The wrong solution (that's currently happening): People follow and post on popular relays. In other words: Relay centralization. My solution (which is a solution to the ICANN-DNS problem but happens to solves many other problems as well): You can find someone easily, find their relays that they use and would always be update to date so you don't do anything, so you'd see their posts, and when you reply/react/anything > it sends that info to the relays the post is at. This solves relay events discovery, and as a result resists against relay centralization. Previously it was thought that this issue can't be fixed, turns out it can but at that cost of an initial bitcoin spending. I can remove that initial bitcoin spending cost, but the tradeoff is having no control so this isn't desired. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse https://image.nostr.build/9d4bb63bec56c2ac4947c71634c8c5efa2038070cc4b78543ef193325156a5fc.jpg npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse (Mentioned this because there was also a window of time where his domain was down as well, and there are multiple examples of people having their domain taken away) Regarding patreon, not sure when, but it's already prepped in the nostr desktop signer that i made, where it'll enable decentralized traditional fiat payments to nostr users/creators. Aside from that, regarding video hosts, Blossom is a thing but in terms of achieving good decentralization of large files (media or otherwise) an economic infrastructure needs to be built (and at least for me, i want to build this as well, but considering the complexity of how i want to build it, basically an evolved ads-system that's beneficial for all, it'll be a while until i get to it). npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Yes, I made it / figured it out, and releasing the probably horrible code for it soon, here's a demo: https://video.nostr.build/a2cc23b88527ba5b445ceea7a058a1dfda50679426a644e974e3e748be7cc03a.mp4 And yes, that short domain example, example.nabandonaread is a censorship-resistant permissionless bitcoin-anchored nostr based domain (without adding any junk/spam to bitcoin), that's as cheap as it can be, as relatively fast as it can be, as easy as it can be (send to yourself money, then publish/edit your domain records), and extremely scaleable (you're getting a TLD, so you can have as many domains as you want with zero cost), and self-signed certificate (no need to rely on the Certificate Authority), all the while resulting in secondary-benefits (fixes the relay discovery and centralization issue, enables traditional but evolved username/passwords login method, resulted in the creation of shortenting nostr event/post addresses, and many more). npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse This is great / seems like the best discord alt out there at a glance =3 Though yea there's the issue, 'self host', meaning you could still get banned / account wiped and censored by the self-hoster, and you'd have to register a new account each time you'd want to join another self-hosted instance, and if someone wants to properly have their own server then they have to go through the hassle of getting and settup up the server and convince their friends to make accounts here along with the other times they've done it. So yea, as you said, that nostr-based is the goal that doesn't have any of these issues =3 Well, no issues in regards to text, the only issue is voice/cam/stream, which is at the moment something that must be self-hosted, but already have a solution for that in mind, however, it's part of a much larger project so it'll be a while until I'd get to it. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Here's how that's solved through my own experience on traditional media: 1. I see companies advertise themselves 'follow us on TwiX', then i do, and i see their posts, i see people reply, i engage with the post and replies, i check people out, if i find them interesting from what they've posted in the past I'd follow them. Basically the solution here is is a company/studio/product/influencer/whatever-of-value is announcing that they're posting on XYZ and people would follow. 2. People post with hashtags, i search for those hashtags, engage with posts there, and same process with checking profiles out and following 3. Forums (reddit, etc), i check posts on categories/subs that i might find interest in (gaming, anime, etc), and see what peoples my interest, and engage, and i repeat the processes from the above two points. This cycle repeats for whatever platform you'd be on. You'd get a lot of people to follow and engage with now. 4. The new kid on the block regarding these flow: Algos. Tell it what you like, hopefully it shows you stuff you may like, keeps monitoring your activity and adjusts itself to fine-tune what you may like and hopefully follow/engage with people. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I decoupled the names event from the connection records (like dns records for when you update your domain) in DNN so you don't have to update two places at the same time (not sure why I decided that in the past...). DNN node peer discovery is working (two nodes on two different hosts), but there's a design flaw with it that I'm fixing. After that, I need to make sure that the DNN daemon is working after that decoupling change, along with the forked Min browser, double-check on delegation if it still works along with ssl/tls self signatures, clean up docs, then I'd release the DNN node code (so that people can see the horror, but it's working! x3). I want to also see if I can package it for umbrel/start9/cloudron, but I'll pause that for temporarily. Then I can start poking nostr clients on their thoughts about it, and see if they'd implement it into their clients, then start talking with browser projects/devs for the same purpose, then linux distros, etc. During which, I'd start working on that Discord alt. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse I've tackled this issue with my ICANN-DNS solution (funnily enough) that came as a secondary-effect benefit. It's not 'the' solution, but 'a' solution, one that provides a permanent static short address that's human readable/memorable, that has behind it relay information that can be changed without changing the user address/ID string, which also solves the relay centralization issue. The cost for all these benefits? For the user to do a one-time initial process of: a Bitcoin self-transfer from their Bitcoin address that was derived from their npub address then to publishing 4 events (one click tho). End result example: npub 18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r to nAbandonAreaD (not case sensative. censorship-resistant, permissionless, etc, + have those relays behind it / the benefits i mentioned (plus a lot more benefits) ) npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse For me I was already planning to do this for my game mod platform and the eventual game store/client, so this would definitely help (in the eyes of a company trying to provide a service, but also a step in the future for...), and also to expand the decentralization of those who hold such large files to offer them as a service, there needs to be a an economic infrastructure of varied options to facilitate its growth, in a direct action (pay to download/upload) or automatic (free/watch ads), for a seemless high-quality download/upload experience of large files (it'll be a while until I build that economic infra tho). Torrenting would of course still be an option / fallback. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse We're getting chunks/chunking to Blossom? Nice =3 npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Still not it's final form, but if you want check out (fork?) what I made (desktop signer / bunker + two other login/signing methods + a lot more)#nevent1q…u6nv npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Hopefully I'll remember to add DMs to the forked version of Jumble the way I see it UX wise + with the more private nip17 version of it / zero metadata leaked (that also stops potential spam from being received and processed, but at the cost of not allowing people to cold DM u) I figured out for a client. npub18n4ysp43ux5c98fs6h9c57qpr4p8r3j8f6e32v0vj8egzy878aqqyzzk9r Freakoverse Another perspective to add on to this: If other clients don't want to respect expiration tag, it'd be beneficial for the user to see a tag somewhere, something like "Expired", and tapping it would lead to show more information about the post that was original set to expire on date/time xyz.