Think I'll test this out too and see if it works 

 I wonder if the alt tag works when I comment on this problem 

 testing live comments 

 commenting on this to test real time updates on comments 

 commenting to test real time updates on threads. Shouldn't work 

 Here's a deeper threaded reply 

 3 levels deep 

 Live test on oxygen 

 Will there be an overflow 

 test odd behaviour 3 levels deep 

 Will the UI duplicate 

 Testing UI duplicatye 

 Hide input area after reply 

 Odd behaviour in threads after reply is submitted 

 The first fix attempt succeeded. How do we close the subscription 

 Testing odd behaviour 

 This should should right above it 

 Hide input area after reply 

 Odd behaviour in threads after reply is submitted 

 The first fix attempt succeeded. How do we close the subscription 

 Testing odd behaviour 

 test odd behaviour 3 levels deep 

 Good to go? 

 Testing odd behaviour 

 Solved: yondar.me 

 Solved: go.yondar.me 

 This is ready for review. Added nip05 with verified check/x if failed and image/author display name to geochat 
https://github.com/innovatario/yondar-mono/pull/12/ 

 Here's the labels I've come up with that we could use for all places:

- Convenient 
- Clean
- Affordable
- Memorable
- Inviting 

 Can't we create our own world layer?  Take a look to what3words.com for example, they define a locatie 5 by 5 meter with three words. Don't know how exactly but maybe we wre we able to create something as well with Nostr? 

 Lmk if y'all have questions on the problem statement, and suggested/example solution.

-elsat 

 Great work! Thank you!  

 solution: add nip19 support to comment  

 like a user profile ?  

 Yeah like a profile page kind of thing showing what problems I've claimed etc 

 I am open for ideas and will implement as much as I can !  See current state of build  => 

https://cdn.satellite.earth/509a1820a609518305b042ce95b542b8047790a3b8ce6f46ada5cf8137e8328b.png 

 Yes this would be great! A few thoughts:

- there is a latent profile component in the yondar codebase you may or may not find useful
- I imagine we could use the user view board to replace the njump links
- I like your mockup with the "places I've visited" and stuff like that. Some of those things need to be defined more clearly before they can be implemented. We should open separate sibling problems to figure those pieces out (so that we dont block this task, as a problem with child problems can't be claimed)
- you can create the user board without these undefined things and they can be added later!
- 🚀🚀🚀 

 😃👍 

 Adding in nsec login flow. 
https://github.com/innovatario/yondar-mono/pull/15 

 What about nsec Bunker workflows ? I personally have no idea to implement it! Here is a link of the nostrasia from pablo https://www.youtube.com/watch?v=kT6_3qCCayg

might be also a good choice for future product development  

 I'm in favor of it! Log a problem for it if you please! 

 This is useful on github because issues are sometimes very large and are "managed" by the maintainers, but problems here should be very small and take at most 6 hours of working time to solve and should not require interactivity or management.  

Can you link to a specific problem (as an example) where you wanted to use this type of feature? 

 Which clients have implemented alt tags?

The alt tag for the root event below (kind 1971) doesn't work on any of the clients I've tried.
 nostr:nevent1qqspqeucfan0arj3l8hfj37tpnwdrz45m0defp5p3g9y9833pzzelqsppamhxue69uhkummnw3ezumt0d5pzpkg3j83suqzyfw2zcr5zet28pve279chvnpzwklwp0vexal06sr4qvzqqqqqqyckenwu 

 Alt shows as Problem Tracker Event on gossip 

 It's on my list 🫠 

 Solved in https://github.com/nostrocket/oxygen/commit/7684946e549bda7c01febcabb5f7b2e487354428 

 I edited this probem to make it into a problem statement. 

 test comment for alt tag 

 Solved and ready for arkinox to check and close  

 I merged patches from Eric and Sherry that add Niel's icon as the favicon. 

If the icon is legitimate enough arkinox can close it :p 

 @gsovereignty

please check the probelm i logged here as well as my PR

https://github.com/nostrocket/oxygen/pull/64 

 Merged  

 I have a patch that will make it work sometimes, but when it doesnt work , it usually includes reasnon below:
1 . consensus diverge
eventviewer/f61353291a91f61c289aefe479b1314f024ba188df33a94bb66027431a777fbc
and 
https://nostrocket.org/eventviewer/01763de12b7b95786dc54edda48eeec439d08330c6506e11f57eca924244a179
point to same previous consensus event, and their request tags are all valid

2. sometimes request tag event is at namepool but code cannot find it , usually happened at consensus event numver 5
 

 I started drawing out things here: https://www.figma.com/file/XzjwS5xATDkLnViXo9oODX/Nostrocket?type=design&node-id=0%3A1&mode=design&t=tDM0tbWrqCeu9AF1-1 

 Open in New Tab is needed indeed! 

  ⭐ Starknet Whitelist Registration is now live. 

 ⭐ https://telegra.ph/starknet-10-10 Claim Your free $STRK. 

 Necessary info to accomplish this:
https://vercel.com/docs/functions/edge-functions/og-image-generation 

  ⭐ Starknet Whitelist Registration is now live. 

 ⭐ https://telegra.ph/starknet-10-10 Claim Your free $STRK. 

  ⭐ Starknet Whitelist Registration is now live. 

 ⭐ https://telegra.ph/starknet-10-10 Claim Your free $STRK. 

 fixed at https://github.com/nostrocket/oxygen/commit/853654b50d90f130bfdc39436b6a13a0c8687d6e 

 https://taginfo.openstreetmap.org/
https://schema.org/Place 

 To make it simpler, why not ditch the idea of expiration tags and only use the timestamp? 

 test comment 

 test comment 

 test comment 2 

 I have resolved this problem with a patch: https://github.com/nostrocket/oxygen 

 what are you replying to 

 I'm just testing something  

 i see 

 Is your initiative in NIP-44 https://github.com/nostr-protocol/nips/pull/927 an attempt to address this problem? Having a NIP for Yondar-like apps could fix this, anyone could create an interoperable alternative to Yondar. 

 Here is a form where properties may be suggested: 
https://docs.google.com/forms/d/e/1FAIpQLScF2LYr9RIYi4-YFKNFaaYH3YYTdUo09j6RRGVjf992wNC1EQ/viewform 

 Here are the form results: https://docs.google.com/spreadsheets/d/1r7mYftFUgED1VTvTaIv790a2JKXnfVDt9T0_INxzgd8/edit?usp=sharing 

 We have relay finally. Forked repo -> https://github.com/samuelralak/nostr-rs-relay 

 Yep we are on it. Defining this problem was a formality in order to get our progress into nostrocket. 

 Resolved in https://github.com/nostrocket/oxygen/commit/5ff9f91991fbf106d372381258228b573ce862f2 

 Resolved in https://github.com/nostrocket/oxygen/commit/dabad8a02f0db404f2a9fab478277b7d5c840884 

 I have resolved this problem with a patch: https://github.com/nostrocket/oxygen/commit/2999c1df57c973a53cc6892c1eaa659364cfa91e 

 so i'd seen this nostrocket word around here and there so i read a bit more of the site

it's a distributed consensus!

is there some reason why you are borrowing the stake fraud as a membership filter instead of using a simple membership voting system for admission?

i presume it's also based on the 2/3 minimum BFT of the 1999 pBFT protocol?

i agree that mechanisms to rank members of a pBFT consensus by their failures to vote with the consensus are a good thing in general but if you are not actively monitoring your node on such a system you shouldn't be a member either, so expulsion should also be a consensus decision

just my thoughts on it - i think that it's a straight up fraud calling it "stake" when trust only needs to satisfy 2/3 correct, and non-byzantine faults are part of that failure tolerance and automatic systems of changing membership can be gamed

that last point is my biggest gripe with the staking membership competition

having a lot of money is not the same as being trustworthy, and trust is not a scoring system that can, or will ever be able to be turned into a consensus, the wreckage of failures of trust score systems in already existing history should be a warning not an encouragement to choose different ways about cluster memberships 

 testing 

 test 

 test 

 I've resolved this problem with a patch: https://github.com/nostrocket/oxygen/commit/751f5c2212d75818c1588c8414bd3adec154b886 

 I've resolved this problem with a patch: https://github.com/innovatario/yondar-mono/kfgjhdsjkgfhsdg 

 I've resolved this problem with a patch: https://github.com/nostrocket/humble.horse/commit/2731f74fd7d9b90a7d2813d62c0ba071bf83e12c 

 I've resolved this problem with a patch: https://github.com/nostrocket/humble.horse/commit/49b19445f2a036e6de670536c0062a4ce8946b68