It’s another #damus TestFlight Friday! We need your help Purple Subscribers! Please try out the new stuff and let us know if there’s any feedback before the next release. Here’s a quick overview of what’s new and a ton of what’s been fixed for everyone’s sanity: https://cdn.jb55.com/s/damus-1.12.mp4
What to Test:
Added:
- Render Gif and video files while composing posts (Swift Coder)
- Add profile info text in stretchable banner with follow button (Swift Coder)
- Paste Gif image similar to jpeg and png files (Swift Coder)
Changed:
- Improved UX around the label for searching words (Daniel D’Aquino)
- Improved accessibility support on some elements (Daniel D’Aquino)
Fixed:
- Fixed issue where the "next" button would appear hidden and hard to click on the create account view (Daniel D’Aquino)
- Fix non scrollable wallet screen (Swift Coder)
- Fixed suggested users category titles to be localizable (Terry Yiu)
- Fixed GradientFollowButton to have consistent width and autoscale text limited to 1 line (Terry Yiu)
- Fixed right-to-left localization issues (Terry Yiu)
- Fixed AddMuteItemView to trim leading and trailing whitespaces from mute text and disallow adding text with only whitespaces (Terry Yiu)
- Fixed SideMenuView text to autoscale and limit to 1 line (Terry Yiu)
- Fixed an issue where a profile would need to be input twice in the search to be found (Daniel D’Aquino)
- Fixed non-breaking spaces in localized strings (Terry Yiu)
- Fixed localization issue on Add mute item button (Terry Yiu)
- Replace non-breaking spaces with regular spaces as Apple's NSLocalizedString macro does not seem to work with it (Terry Yiu)
- Fixed localization issues in RelayConfigView (Terry Yiu)
- Fix duplicate uploads (Swift Coder)
- Remove duplicate pubkey from Follow Suggestion list (Swift Coder)
- Fix Page control indicator (Swift Coder)
- Fix damus sharing issues (Swift Coder)
- Fixed issue where banner edit button is unclickable (Daniel D’Aquino)
- Handle empty notification pages by displaying suitable text (Swift Coder)
amazing !!! so excited for this feature ...
... and #Litecoin is for those who want a backup for all their blockchain based experiments 🎉
sometimes it takes using the code to realize its written wrong ... my life is all refactoring at this point ... no app building ... just realizing better ways to write code.
Who would fly the rockets, drive the cars & bot the robots?
I used to laugh at the devs for constantly refactoring their code …
Now I’m that dev.
#sadTrombone
11 years ago today, the term “hodl” was created as a result of a drunken rant.
Please notice that the **person who created the term** pronounces it correctly: “HODL” not “hoddle.”
I rest my case.
Cc nostr:npub1rtlqca8r6auyaw5n5h3l5422dm4sry5dzfee4696fqe8s6qgudks7djtfs https://v.nostr.build/EeqqazdRh6SYITTB.mp4
... be UN-governable ... call it whatever you want ...
just keep stacking ...
sadly ... the edge cases Ive always had to account for are financial transactions based. the easy answer (IMHO) ... as long as its stated upfront that any financial losses that occur from a service disruption or other error from a missed scheduled post are bore by the account holder & not the service ... you're covered.
... my last big project was a stock trading app ... so this sort of stuff rang in my ears from the devs to the product manager. and now it's something i think about often.
I am in that hell as we speak 🤡🥂💯🎉
From a risk & responsibility pov … if the scheduled post doesn’t go through & it creates a “lost opportunity” … you might be on the hook.
I know on some of the bank messaging projects I’ve worked on … this was a reoccurring concern … even with a strong TOS explicitly covering our butt
… ya I’m wondering if this is as much a NodeRed service as much as a simple node/express server that uses Postgres (or Supabase) for data management & just listens to a handful of relays & performs an action as configured by the user / request maker.
Eg. listen for user nPUB on kind # containing #keyword trigger #action
So … if a service had a server that you request a DM magic link from … and it provided you a URL login to a dashboard … might that work?
With the underlying headless NodeRed service open sourced & available… would that be sat worthy?
If there are any board JavaScript developers out there that want to build a nostr thing and earn sats. I'm officially putting up a bounty to integrate rx-nostr into node-red
I'm offering 100k sats to anyone who will build and publish a working rx-nostr -> node-red integration
It needs to fulfill the following requirements
- Easy to install ( should be searchable in the UI )
- Support for all options in `createRxNostr` including signer and default relays
- Support for creating subscriptions using `createRxForwardReq`
- Events returned from subscriptions should be node-red messages
- A node for easily publishing an event to the default or custom set of relays ( using `rxNostr.send` )
50k bonus if you can also create a package that integrates applesauce EventStore into node-red
- Configuration node for creating a global EventStore
- Query node for subscribing to the store using one of the Queries
I don't know if I'm asking too much but I really want to see this built. I think we could do a lot of bot / DVM prototyping if we had a way to use nostr in node-red
For example. if we had both of these integrations it would be easy to setup a node-red flow that would
- Connect to a set of relays and listen for events (kind 1 mentions)
- Do some work with new events
- Easily respond using applesauce factory to create a reply event
- repeat... ( profit? )
sites:
rx-nostr https://penpenpng.github.io/rx-nostr/
node-red https://nodered.org/
applesauce https://hzrd149.github.io/applesauce/core/event-store.html
so this node flow ... what are we thinking for Access Options?
- Headless: flows can run as backend services without any UI
- API Endpoints: an exposed HTTP endpoints from a pre-configured flow
- Custom UI: including a built frontend that communicates with your flows
- Dashboard: a node-red-dashboard with all the state / config views?
... if were talking fast and dirty, I'd probably try and do a headless / API version ... but I'll need a bit of context on what ya'llz thinking.
so would a couple of useful usecases for this be ...
Event Archival - Archive specific types of Nostr events for later analysis.
-Flow Description
```
[Nostr Subscribe] → [Event Filter] → [Transform] → [EventStore Save] → [Query API]
```
### Implementation Details
- Subscribe to multiple event kinds
- Filter events based on content or tags
- Transform events into desired format
- Store in Applesauce EventStore
- Provide query endpoints for data analysis
-- or something like --
Automated Response System - Create automated responses based on event patterns.
### Flow Description
```
[Nostr Subscribe] → [Pattern Matcher] → [Response Generator] → [Nostr Publish]
```
### Implementation Details
- Define trigger patterns (keywords, commands)
- Create response templates
- Support for dynamic content insertion
- Rate limiting and spam prevention
- Store interaction history
I'm starting to mock something together and from the top of my head ... these seem like useful actions.
Now let’s do it again … but with #Litecoin
If there are any board JavaScript developers out there that want to build a nostr thing and earn sats. I'm officially putting up a bounty to integrate rx-nostr into node-red
I'm offering 100k sats to anyone who will build and publish a working rx-nostr -> node-red integration
It needs to fulfill the following requirements
- Easy to install ( should be searchable in the UI )
- Support for all options in `createRxNostr` including signer and default relays
- Support for creating subscriptions using `createRxForwardReq`
- Events returned from subscriptions should be node-red messages
- A node for easily publishing an event to the default or custom set of relays ( using `rxNostr.send` )
50k bonus if you can also create a package that integrates applesauce EventStore into node-red
- Configuration node for creating a global EventStore
- Query node for subscribing to the store using one of the Queries
I don't know if I'm asking too much but I really want to see this built. I think we could do a lot of bot / DVM prototyping if we had a way to use nostr in node-red
For example. if we had both of these integrations it would be easy to setup a node-red flow that would
- Connect to a set of relays and listen for events (kind 1 mentions)
- Do some work with new events
- Easily respond using applesauce factory to create a reply event
- repeat... ( profit? )
sites:
rx-nostr https://penpenpng.github.io/rx-nostr/
node-red https://nodered.org/
applesauce https://hzrd149.github.io/applesauce/core/event-store.html
Oh Yaah? I’m looking to earn Sats to dev … been sharpening my skills on some utilities so I can build stuff useful for our world here.
#nostrDev question … let’s say someone uses a DM magic link to login to a site … they still need to step up auth with an nsec to be able to post … like there’s no way around it is there ?!?
Still messing around with some crypto utilities type things ... i noticed that Seedphrase needed a couple of crypto things that i also needed in other services ... so i abstracted it and made it its own thing.
if you're #nostrDev & muddling through events and key management... worth taking a look.
anyone whos wanted to add NIP-49 (seed phrases) to their app. I think this repo is finally ready for the big leagues ... been working at it on and off over the past weeks.
I'm still pretty new to the whole #GitHub & #nostrDev experience ... but an as an oldschool coder & UX person ... it should be of value.
... and if anyone wants to shoot a couple of #ZAPS or #SATs my way ... I'm always happy to accept them.
https://github.com/HumanjavaEnterprises/nostr-nsec-seedphrase
... fyi ... this all started because i wanted a 1 click installer for building a server and having it create its own nsec/npub identity. So that it would make deployment a bit easier ...
... and the more i looked into it ... the more i saw #nostrUX needed a bit of a pivot to support other more known / already existing #UXdesign patterns like #bitcoin #seedphrase flows etc.... and hten trying to convert keys across different formats for use ... ugh ... the whole thing just made me want a plug-n-play utlity...