SN release: nostr crossposting, symmetric lud18, quote replies, @ autocompletes \ stacker news ~meta

SN release: nostr crossposting, symmetric lud18, quote replies, @ autocompletes

13.8k sats \ 62 comments \ @k00b 4 Oct 2023 meta

zaps forwarded to @WeAreAllSatoshi (45%) @bitcoinplebdev (45%) @rleed (10%)

This one is a honker.

Rewards update

Rewards are now random. Every night I give a cowboy a bottle whiskey and he flips a coin. If it lands on heads, we reward the top 33% of posts/comments. If it lands on tails, we reward the zappers of the top 33% of posts/comments.

Goodies

nostr crossposting (via @bitcoinplebdev)
- requires nip-07 extension
- only applies to discussions currently (more is planned)
- you can set it to repost on a per post basis (in the options pane) or default to crossposting in settings
symmetric lud-18 (via @WeAreAllSatoshi)
- you can now optionally send identifying information when you make a lightning address withdrawal ... assuming the receiver's wallet supports it
- you can also receive such information when someone sends to your lightning address
quote replies (via @WeAreAllSatoshi)
- in the overflow aka ... for items you can now quote the item you're replying to by hitting quote reply
- if you haven't highlighted text in the parent, it will quote the full item
- if you have highlighted text in the parent, it will only quote what you've highlighted
- if you have highlighted text in the parent and hit reply it will also quote it
mention autocompletes (via @WeAreAllSatoshi)
- it's like it sounds ... when you hit @ sn attempts to help you find your boo
date range selection in search (via @rleed)
full url search with the url: filter (via @rleed)
changes to my changes of images (via @ekzyis) ... he'll have the last change
kind of a small one ... but when you switch over to preview, you no longer lose your cursor position in the original text

PR merging vacation

Take a knee contributors. PRs for new features will not be merged (by me at least) until I finish personalized feeds. Please continue to send in PRs, it just might be slightly slower turnaround than usual ... Oh, and one of your moms brought orange slices and gatorade. Help yourselves.

Please shout loud about any bugs you find!

view all related items

3706 sats \ 0 replies \ @WeAreAllSatoshi fwd 4 Oct 2023

Really awesome work everyone! SN gets better every day!

The only downside of being forwarded zaps on a post like this is I can’t zap it for the other folks lol

1831 sats \ 1 reply \ @TheWildHustle 4 Oct 2023

Love to SN's continued development

1696 sats \ 0 replies \ @k00b OP 4 Oct 2023

SN's continued development loves you back! 😄

1388 sats \ 0 replies \ @elvismercury 5 Oct 2023

Badass. Love the @-searching with so much passion, and the reply quoting.

2235 sats \ 1 reply \ @k00b OP 4 Oct 2023

Crossposting works!

15 sats \ 0 replies \ @Natalia 5 Oct 2023

still trying to understand how this one works

edited: just found it!

105 sats \ 19 replies \ @DarthCoin 5 Oct 2023

@WeAreAllSatoshi can you check the LUD-18 and LUD-12 option? I tried to send some tests to chat@blixtwallet.com or darthcoin@ln.tips or darthcoin@getalby.com (all of them support LUD-18 and 12 and the modal for comment and name is not appearing in SN payment screen (using the LN address field).

If I want to send to chat@blixtwallet.com (https://chat.blixtwallet.com/) 10 sats it appear the comment and name but I get an error: Unexpected error value: [400, "expectedPaymentRequestToDecode"]

368 sats \ 14 replies \ @hampus 5 Oct 2023

If I want to send to chat@blixtwallet.com (https://chat.blixtwallet.com/) 10 sats it appear the comment and name but I get an error: Unexpected error value: [400, "expectedPaymentRequestToDecode"]

expectedPaymentRequestToDecode appears to be coming the lightning npm lib, and is decoding an invoice.

https://github.com/alexbosworth/lightning/blob/b05f7d816363c74b31516ffbb73f541970898fe3/lnd_methods/offchain/decode_payment_request.js#L59

Perhaps the invoice request (i.e calling the callback in LNURL-pay) didn't work properly for some reason and did not return an invoice.

5 sats \ 9 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

@hampus I see this in the logs when trying to call the invoice request from my dev machine:

{
  statusCode: 500,
  error: 'Internal Server Error',
  message: 'Could not parse query params'
}

with a query param string of ?amount=10000&payerdata=%257B%2522identifier%2522%253A%2522SatsAllDay%2540stacker.news%2522%257D

An issue decoding the URI encoded param, maybe?

ETA: same thing when you send name, as well. Are we doing the payerdata query param encoding incorrectly?

55 sats \ 8 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

@hampus Taking a look at chat.blixtwallet.com's code, I don't see any explicit decoding of the query param: https://github.com/hsjoberg/lnurl-pay-chat-server/commit/a28f998675a675a835ea1a639be2ec1f1fdae0ec#diff-a2a171449d862fe29692ce031981047d7ab755ae7f84c707aef80701b3ea0c80L226

Perhaps we're double encoding when we shouldn't be?

351 sats \ 0 replies \ @hampus 5 Oct 2023

I don't see any explicit decoding of the query param:

It was some time ago I made this server, but I think Fastify is implicitly decoding the GET params. It makes it into an object.

It will naturally not attempt to decode twice, which is why the JSON.parse() errors out.

351 sats \ 2 replies \ @hampus 5 Oct 2023

Perhaps we're double encoding when we shouldn't be?

Yes, as far as I can tell, it seems to be double-encoded when it shouldn't be.

A quick look. Yours require two decodeURIComponents:

// stacker.news
decodeURIComponent(decodeURIComponent("%257B%2522identifier%2522%253A%2522SatsAllDay%2540stacker.news%2522%257D"));
'{"identifier":"SatsAllDay@stacker.news"}'

// blixt wallet
decodeURIComponent("%7B%22name%22%3A%22Hampus%22%2C%22identifier%22%3A%22hampus%40blixtwallet.com%22%7D");
'{"name":"Hampus","identifier":"hampus@blixtwallet.com"}'

351 sats \ 1 reply \ @hampus 5 Oct 2023

Though I'm not sure who's in the wrong here. I'll investigate some more.

798 sats \ 0 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

We’re probably getting URI encoding for free with the native JS API that constructs the URL

5 sats \ 3 replies \ @hampus 5 Oct 2023

Perhaps we're double encoding when we shouldn't be?

Yes, my understanding after reading the specification again is that it should not be encoded twice.

6 sats \ 2 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

Yea that makes sense. I’ll work up a fix today!

351 sats \ 0 replies \ @hampus 5 Oct 2023

Great! Cheers.

291 sats \ 0 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

https://github.com/stackernews/stacker.news/pull/545

5 sats \ 3 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

I got this too. I’ll debug when at my computer

5 sats \ 2 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

If you don’t include your identifier, it seems to work.

5 sats \ 1 reply \ @DarthCoin 5 Oct 2023

but that is just posting as anonymous

5 sats \ 0 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

Yea, I’m just trying to figure out what conditions cause the error. I’m still on mobile, I’ll dig into it further in a little while

15 sats \ 3 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

I just tried this and it seemed to work?

5 sats \ 2 replies \ @DarthCoin 5 Oct 2023

For me appear for a second the fields and then disappear. Only when I use chat@blixtwallet.com it stays. Maybe after first use is something in the browser cache?

5 sats \ 1 reply \ @WeAreAllSatoshi fwd 5 Oct 2023

We query the ln addr provider every time you change the address, character by character. We probably need to debounce this, because if you're on the second to last character, there won't be valid metadata (e.g. darthcoin@stacker.new), so we default the form state. If these requests resolve out of order, you could end up in a state with no LUD-12 or LUD-18 options in the form. Debouncing should resolve it.

cc @k00b

5 sats \ 0 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

https://github.com/stackernews/stacker.news/pull/545

594 sats \ 0 replies \ @ek 5 Oct 2023

We also squeezed in more push notification types. Everything except job updates now have a corresponding push notification (/cc @WeAreAllSatoshi since you mentioned you eagerly await them. And haha, used you during my first time using mention autocomplete). But there is a bug for the daily rewards type where only the rewards for one type will be shown.

398 sats \ 0 replies \ @Entrep 5 Oct 2023

SN keep making the work looks easy

398 sats \ 0 replies \ @TheBTCManual 5 Oct 2023

Lol I like the drunken cowboy protocol I think it should be the norm and all your reward experiments should stick around and it flips between them to keep us guessing, kinda like monero does with trying to be ASIC resistant

26 sats \ 6 replies \ @WeAreAllSatoshi fwd 4 Oct 2023

Gah I don’t think selecting text for quote reply is working on mobile safari 😾

26 sats \ 3 replies \ @k00b OP 4 Oct 2023

I think it's only broken when doing it in the original post. There's likely some kind of race and deselecting the text is winning. I also noticed in mobile safari that the dropdown will fall behind the selection as if safari doesn't honor the dom hierarchy.

26 sats \ 2 replies \ @WeAreAllSatoshi fwd 4 Oct 2023

Safari doing safari things lol

I’ll experiment with it and see if I can find a fix

1216 sats \ 1 reply \ @k00b OP 4 Oct 2023

It's this generation's Internet Explorer

798 sats \ 0 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

PR opened to fix this

5 sats \ 1 reply \ @ek 5 Oct 2023

Also noticed that the OS on Android may block me from clicking the dots, lol

Not sure if this is fixable. But I think it's also not a big issue.

509 sats \ 0 replies \ @WeAreAllSatoshi fwd 5 Oct 2023

That’s where clicking reply after making your selection can be used! It’s good to have options lol

21 sats \ 0 replies \ @bitcointerest 5 Oct 2023

I'm loving all these updates and the transparency from the team. Thank you @Natalia for the heads-up on the new features.

15 sats \ 0 replies \ @DarthCoin 5 Oct 2023

LUD-18 is fucking awesome! Thank you guys! Now I san send sats to somebody, attaching the name Christine Lagarde.

5 sats \ 2 replies \ @AR0w 5 Oct 2023

I think storing my nsec in sn + adding a password to encrypt it in sn will be much easier for crossposting to nostr ?

adding this as an optional option will be helpful @k00b @bitcoinplebdev

180 sats \ 1 reply \ @03365d6a53 8 Oct 2023

this is not a good idea

would you do that with a bitcoin seed?

0 sats \ 0 replies \ @AR0w 8 Oct 2023

5 sats \ 0 replies \ @ruS7Y 5 Oct 2023

Loving the cross post feature.

LFGGGG!

5 sats \ 0 replies \ @AR0w 5 Oct 2023

1- Is there is a way to crosspost without nip-07 ?

2- Can it crosspost old posts Or batch crosspost what i posted when i use an extension browser ? @k00b

5 sats \ 0 replies \ @Natalia 5 Oct 2023

wow, lud-18! Just tested it, basically, you can send the msg as anyone now.

Mention autocompletes is cool, no more chance of typing the id wrong then 😂😂

5 sats \ 0 replies \ @The_Daniel 5 Oct 2023

I had to try it for myself. First impression? It’s amazing! Second impression? Nostr clients have a lot of work to do to display these posts better. Some do a great job, some have unexpected formatting issues. Some don’t show them at all!

5 sats \ 0 replies \ @2bithits 5 Oct 2023

Interested to try out NOSTR cross posting!

Thanks

5 sats \ 0 replies \ @danieltapa 5 Oct 2023

how can we earn the bottle whiskey?

5 sats \ 0 replies \ @ryu 5 Oct 2023

honk honk

5 sats \ 0 replies \ @fred 5 Oct 2023

The cross posting on Nostr is important feature to have on SN

5 sats \ 0 replies \ @WeAreAllSatoshi fwd 4 Oct 2023

🍊🎉

5 sats \ 0 replies \ @rosivalnonato 5 Oct 2023 freebie

I want to escape too, Satoshi lol

0 sats \ 5 replies \ @Design_r 21 Mar

@bitcoinplebdev @k00b I'm getting this error when crossposting in the past two days. Anything could I try to restore the fucntionality?

submit error: Nostr error: Timeout after 10000 ms waiting for extension

When tried to Unlink (after connecting a secon login option) and Re-link the nostr extension I get this error error: nostr extension failed to sign event timeouted after 5000 ms waiting for extension

21 sats \ 1 reply \ @bitcoinplebdev fwd 21 Mar

What browser are you on? It's possible your browser security is blocking the extension. Sometimes I need ti disable on certain sites

10 sats \ 0 replies \ @Design_r 21 Mar

using chrome and nos2x, it was working until two days ago 🤷

Thanks for the suggestion I checked the settings but can't find a similar option nor in the site settings

21 sats \ 1 reply \ @k00b OP 21 Mar

This means your nostr extension isn't responding to requests to sign messages usually.

10 sats \ 0 replies \ @Design_r 21 Mar

It could be, there's a way I can reactivate? Also tried with flamingo and getting the same results

This is the message I get just before the 5000ms one

10 sats \ 0 replies \ @Design_r 21 Mar

Deactivating and reactivating the nos2x extension after removing SN previous permission look's it did the job

0 sats \ 1 reply \ @go 24 Dec 2023

deleted by author

0 sats \ 0 replies \ @WeAreAllSatoshi fwd 24 Dec 2023

What did it say?!?!

0 sats \ 0 replies \ @DarthCoin 7 Oct 2023

@MoritzK please can you check on alby why is not displaying the alias / sender from LUD-18 (when you receive from SN using an alias)?

0 sats \ 0 replies \ @nemo 6 Oct 2023

deleted by author

0 sats \ 0 replies \ @adexmakai4211 6 Oct 2023

To be honest this is really great work to say the fact.