a
4 months ago
JBN
jbnevin@tunestr.io
npub1v89n...30cc
I can see birds flying happily in the sky through the window. It is good.
#gm
Noobstr.me 1.3
See an example of what gets posted on NOSTR in one click!
Intuitive onboarding website that functions as a basic read-only client for NOSTR.
Q: "What is NOSTR?" A: "I dunno. Look @ noobstr.me and see."
New in 1.3:
- Removed some dead code - declarations for unused variables
- Better nesting and tabbing, Alt-4 now works in Notepad++
- Optimized a DOM clearing loop that was taking at least one unnecessary action, IIUC
- Fixed potential memory leak issue in lightbox function
- Images may load more reliably on slower devices
- Reuse existing websocket connections to get usernames rather than create new
- Removed duplicate css declarations
- Alert at top of nooblanding text updated and renders more nicely than it really did earlier
- Soft whitelist for URLs: Links all render, most common are labeled, otherwise say [unknown web]
- Stricter event / note check, only shows strictly formatted notes (size, type, hex, timestamp, tag validation)
- Only checks for images at nostr.build, rather than only rendering them if they are from nostr.build (whoops)
- Even display of date/time
Bugs that still exist:
- Code comments are AI generated, some may not be relevant, some more may be needed to be added by human, and some (most) are commenting on code that I don't understand well enough to audit :D
Best Practices Improvements:
- Ask AI to further help me optimize and enhance security / remove vulnerabilities
- rearrange code blocks to convention / sensible order
- implement actual cryptographic schnorr signature verification
- outbox model
- Contributors much smarter than me that can tell me how I or AI has bungled the code, help with convention, sanitize, reduce vulnerabilities, optimize the code, etc
Enhancements planned:
- Ability to click on note to see it on njump.me
- 'See whole conversation' button on each note… linking to one of a set of random web clients that displays conversations well
- clicking 'just go' with a feed already there, and with the same settings, should only load new notes without disturbing the reading order. right now it's refreshing the whole page.
- see most zapped posts (with explain about what zaps are) possibly call it 'most popular' or 'trending' and then alert at top of page explains proof of work stored as value vs gamable fiat. Fetch posts until 50 that have zaps are found, and then sort them by amount zapped? Not on slow connection mode
- Spoiler Alert! … text 'Self sovereignty means hosting your node and owning your keys… learn how now..' what's hilarious about this is I don't know how to do this yet.
- Secondary options for user to find npub/follows and relays aside from nostr.directory and nostr.watch
- Options to choose variables, # of notes to fetch or since when
- Instead of repeating messages in the debugger log, keep a count next to it (?) of # of times, for instance, images or notes were rejected
- Securely fetch thumbnails or any other previews that are possible without increasing attack surface
- Add to homescreen / desktop / install app / pwa
- lite.noobstr.me full.noobstr.me ?
Questions:
- Hosting considerations?
- Who to talk to about getting this listed at places like 
or grownostr.org at the appropriate time? 
<- can add on github
- Are there better links to use for 'Ready to go full NOSTR?' The ones I have are more like 'learn more' than 'get started now' and don't clearly begin with signers for nerfers
- NOSTR IS NOT PROPRIETARY! Look at all the apps that can be used with NOSTR! and - other resources?
- more options and features vs mission creep / maintenance burdens
🤙
New in 1.3:
- Removed some dead code - declarations for unused variables
- Better nesting and tabbing, Alt-4 now works in Notepad++
- Optimized a DOM clearing loop that was taking at least one unnecessary action, IIUC
- Fixed potential memory leak issue in lightbox function
- Images may load more reliably on slower devices
- Reuse existing websocket connections to get usernames rather than create new
- Removed duplicate css declarations
- Alert at top of nooblanding text updated and renders more nicely than it really did earlier
- Soft whitelist for URLs: Links all render, most common are labeled, otherwise say [unknown web]
- Stricter event / note check, only shows strictly formatted notes (size, type, hex, timestamp, tag validation)
- Only checks for images at nostr.build, rather than only rendering them if they are from nostr.build (whoops)
- Even display of date/time
Bugs that still exist:
- Code comments are AI generated, some may not be relevant, some more may be needed to be added by human, and some (most) are commenting on code that I don't understand well enough to audit :D
Best Practices Improvements:
- Ask AI to further help me optimize and enhance security / remove vulnerabilities
- rearrange code blocks to convention / sensible order
- implement actual cryptographic schnorr signature verification
- outbox model
- Contributors much smarter than me that can tell me how I or AI has bungled the code, help with convention, sanitize, reduce vulnerabilities, optimize the code, etc
Enhancements planned:
- Ability to click on note to see it on njump.me
- 'See whole conversation' button on each note… linking to one of a set of random web clients that displays conversations well
- clicking 'just go' with a feed already there, and with the same settings, should only load new notes without disturbing the reading order. right now it's refreshing the whole page.
- see most zapped posts (with explain about what zaps are) possibly call it 'most popular' or 'trending' and then alert at top of page explains proof of work stored as value vs gamable fiat. Fetch posts until 50 that have zaps are found, and then sort them by amount zapped? Not on slow connection mode
- Spoiler Alert! … text 'Self sovereignty means hosting your node and owning your keys… learn how now..' what's hilarious about this is I don't know how to do this yet.
- Secondary options for user to find npub/follows and relays aside from nostr.directory and nostr.watch
- Options to choose variables, # of notes to fetch or since when
- Instead of repeating messages in the debugger log, keep a count next to it (?) of # of times, for instance, images or notes were rejected
- Securely fetch thumbnails or any other previews that are possible without increasing attack surface
- Add to homescreen / desktop / install app / pwa
- lite.noobstr.me full.noobstr.me ?
Questions:
- Hosting considerations?
- Who to talk to about getting this listed at places like Explore Nostr Apps
Awesome Nostr Resources
A comprehensive collection of Nostr resources, tools, clients, and protocols for developers and users.
Awesome Nostr Resources
A comprehensive collection of Nostr resources, tools, clients, and protocols for developers and users.
Explore Nostr Apps
View quoted note →
What sort of #proofofwork , exactly, is rewarded, anyway, and by whom, if not this, and not you.
Asking #AI to remove security vulnerabilities, recursively.
I'm going to stop before it tells me to unplug my computer.
I can see that's where it's headed.
#vibecoding
Noobstr.me 1.2
See an example of what gets posted on NOSTR in one click!
Intuitive onboarding website that functions as a basic read-only client for NOSTR.
Q: "What is NOSTR?" A: "I dunno. Look @ noobstr.me and see."
New in 1.2:
- Event signature validation
- Comprehensive NIP-11 relay information checks
- Content length protection to avoid memory crashes / performance issues
- No longer renders note at all if it includes a malformed url
- Fixed lightbox memory leak vulnerability
- Improved websocket error handling
- DOM updates more efficient
- Lazy load debugger console
- URL, nostr identifier, protocol validation / sanitization
Bugs that still exist:
- Code comments are AI generated, some may not be relevant, some more may be needed to be added by human, and some (most) are commenting on code that I don't understand well enough to audit :D
Best Practices Improvements:
- Ask AI to further help me optimize and enhance security / remove vulnerabilities
- rearrange code blocks to convention / sensible order
- implement actual cryptographic schnorr signature verification
- outbox model
- Contributors much smarter than me that can tell me how I or AI has bungled the code, help with convention, sanitize, reduce vulnerabilities, optimize the code, etc
Enhancements planned:
- Ability to click on note to see it on njump.me
- 'See whole conversation' button on each note… linking to one of a set of random web clients that displays conversations well
- clicking 'just go' with a feed already there, and with the same settings, should only load new notes without disturbing the reading order. right now it's refreshing the whole page.
- see most zapped posts (with explain about what zaps are) possibly call it 'most popular' or 'trending' and then alert at top of page explains proof of work stored as value vs gamable fiat. Fetch posts until 50 that have zaps are found, and then sort them by amount zapped? Not on slow connection mode
- Spoiler Alert! … text 'Self sovereignty means hosting your node and owning your keys… learn how now..'
- Secondary options for user to find npub/follows and relays aside from nostr.directory and nostr.watch
- Settings menu to choose variables, how many notes to fetch or since when
Questions:
- Hosting considerations?
- Who to talk to about getting this listed at places like or grownostr.org at the appropriate time? <- can add on github
- Are there better links to use for 'Ready to go full NOSTR?' The ones I have are more like 'learn more' than 'get started now' and don't clearly begin with signers for nerfers
- Want to find more you can do with NOSTR? and - other resources?
- options features vs mission creep / outlived usefulness
#vibecoding
I used every bit of what I know about computers and software, and what I would assume will be uncommon due diligence in computing best practices, and leaned on AI to answer questions heavily - but I can see there will never be such a thing as 'code written correctly' without someone who knows how to 'write code correctly,' unless the AI gets so good it can do it itself. There's just too much specialized knowledge necessary. Looks to me like the future for the expert developer is the last leg.
See an example of what gets posted on NOSTR in one click!
Intuitive onboarding website that functions as a basic read-only client for NOSTR.
Q: "What is NOSTR?" A: "I dunno. Look @ noobstr.me and see."
New in 1.2:
- Event signature validation
- Comprehensive NIP-11 relay information checks
- Content length protection to avoid memory crashes / performance issues
- No longer renders note at all if it includes a malformed url
- Fixed lightbox memory leak vulnerability
- Improved websocket error handling
- DOM updates more efficient
- Lazy load debugger console
- URL, nostr identifier, protocol validation / sanitization
Bugs that still exist:
- Code comments are AI generated, some may not be relevant, some more may be needed to be added by human, and some (most) are commenting on code that I don't understand well enough to audit :D
Best Practices Improvements:
- Ask AI to further help me optimize and enhance security / remove vulnerabilities
- rearrange code blocks to convention / sensible order
- implement actual cryptographic schnorr signature verification
- outbox model
- Contributors much smarter than me that can tell me how I or AI has bungled the code, help with convention, sanitize, reduce vulnerabilities, optimize the code, etc
Enhancements planned:
- Ability to click on note to see it on njump.me
- 'See whole conversation' button on each note… linking to one of a set of random web clients that displays conversations well
- clicking 'just go' with a feed already there, and with the same settings, should only load new notes without disturbing the reading order. right now it's refreshing the whole page.
- see most zapped posts (with explain about what zaps are) possibly call it 'most popular' or 'trending' and then alert at top of page explains proof of work stored as value vs gamable fiat. Fetch posts until 50 that have zaps are found, and then sort them by amount zapped? Not on slow connection mode
- Spoiler Alert! … text 'Self sovereignty means hosting your node and owning your keys… learn how now..'
- Secondary options for user to find npub/follows and relays aside from nostr.directory and nostr.watch
- Settings menu to choose variables, how many notes to fetch or since when
Questions:
- Hosting considerations?
- Who to talk to about getting this listed at places like Explore Nostr Apps
Awesome Nostr Resources
A comprehensive collection of Nostr resources, tools, clients, and protocols for developers and users.
Awesome Nostr Resources
A comprehensive collection of Nostr resources, tools, clients, and protocols for developers and users.
Explore Nostr Apps
@𝕾𝖊𝖗 𝕾𝖑𝖊𝖊𝖕𝖞
An idea
#GM
Noobstr.me 1.1
See an example of what gets posted on NOSTR in one click.!
Intuitive onboarding website that functions as a basic read-onlly client for NOSTR.
Q: "What is NOSTR?" A: "I dunno. Look @ noobstr.me and see."
New in 1.1:
- Debugger remains in slow connection mode
- Images render + lightbox so long as they are under 300kb and are from nostr.build
- Settings modal buttons fit and look better
- Settings modal has more information for noobstrs that are ready to onboard
- all urls render more readably
- notes over 500 characters have 'show more'
- avatars render larger, limit on avatar filesize reduced to 50kb
- timeout and error handling for images in case wrong image size is reported
Bugs that still exist:
- Code comments are AI generated, some may not be relevant, some more may be needed to be added by human, and some (most) are commenting on code that I don't understand well enough to audit :D
Best Practices Improvements:
- Contributors much smarter than me that can tell me how I or AI has bungled the code, help with convention, sanitize, reduce vulnerabilities, optimize the code, etc
- Ask AI to further help me optimize and enhance security / remove vulnerabilities
- Add @hodlbod 's book Building Nostr, , 
, and other 'nostr best practices' information / primary sources into ai and ask it to look at code and make suggestions
- rearrange code blocks to convention / rationality
Enhancements planned:
- Right now it connects to one relay, and falls back to others if the first doesn't work. However, any one relay may not have all the notes it's searching for. We would want the relay to reach out to a) multiple relays, or b) whatever relays it needs to find the notes it is looking for
- Ability to click on note to go see note on njump.me Also, a 'See whole conversation' button on each… linking to one of a set of random web clients that displays conversations well
- clicking 'just go' with a feed already there, and with the same settings, should only load new notes without disturbing the reading order. right now it's refreshing the whole page.
- see most zapped posts (with explain about what zaps are) possibly call it 'most popular' or 'trending' and then alert at top of page explains proof of work stored as value vs gamable fiat. Fetch posts until 50 that have zaps are found, and then sort them by amount zapped? Not on slow connection mode
- Spoiler Alert! … text 'Self sovereignty means hosting your node and owning your keys… learn how now..'
- option to choose how many notes to fetch or by time / since without limit
- Secondary options for user to find npub/follows and relays aside from nostr.directory and nostr.watch
Questions:
- Hosting considerations?
- How much should i rate limit happy clickers on the load button, given it also calls out to fetch usernames and avatars?
- What size of image should I limit displayed avatars to for general purpose?
- how should I monitor or accept feedback about performance? It's hosted on a 3rd party vps right now with other websites.
- Who to talk to about getting this listed at places like or grownostr.org at the appropriate time? <- can add on github
- Are there better links to use for 'Ready to go full nostr?' The ones I have are more like 'learn more' than 'get started now' and don't clearly begin with signers for nerfers
- Want to find more you can do with NOSTR? and - other resources?
- options features vs mission creep / outlived usefulness
#vibecoding #grownostr
Noobstr.me - The Read Only Nostr Noobstr Slow Connection Soft Landing Client
Building Nostr - A Guide for Developers
GitHub
GitHub - nostr-protocol/nips: Nostr Implementation Possibilities
Nostr Implementation Possibilities. Contribute to nostr-protocol/nips development by creating an account on GitHub.
Explore Nostr Apps
Awesome Nostr Resources
A comprehensive collection of Nostr resources, tools, clients, and protocols for developers and users.
Awesome Nostr Resources
A comprehensive collection of Nostr resources, tools, clients, and protocols for developers and users.
Explore Nostr Apps
Ground beef
Red onions
Green salsa
Pepper jack cheese
1 egg
Mix, shape, bake.
Garlic and salt optional
Approximately my 10th day of practicing only this shot (the longest that can be executed with normal stance and bridge) without applying new chalk (with a decent tip, it won't miscue so long as contact is center center.)
No matter what is happening fundamentally, or what is going through my mind, if the shot works this way, everything is fine.
In other words, leveraging cause and effect, repitition, and observation to force fundamental mechanics into place.
Displays better on smaller screens now. Curious if 'slow connection' mode is tuned to reasonable tradeoffs.
View quoted note →