SN release: gently personalized feeds, self-destructing items, text on links ... \ stacker news ~meta

SN release: gently personalized feeds, self-destructing items, text on links ...

17.1k sats \ 28 comments \ @k00b 23 Oct 2023 meta

zaps forwarded to @rleed (33%) @WeAreAllSatoshi (33%) @ek (33%)

For in what feels like forever we have a new release!

gently personalize feeds
- I say gentle because the effect is really subtle
- most of us will see the same content but it'll be ranked to suit your zapping preferences ever so slightly
- this will be an active area of development for a long time ... this gentle version is just the proof of concept
- this was required for my user generated sub plans
self-destructing items via @WeAreAllSatoshi
- if you want to auto-delete something you can tag the @delete bot and it will delete it for you
- <delete bot mention> in 1 day
- it works for multiple time units: seconds, minutes, hours, days, weeks, months, years
add text description to links now if you open 'options' under a link post via @rleed
set a default max fee for withdrawals in your settings via @rleed
transaction details (preimage, payment hash, etc) via @WeAreAllSatoshi
unsubscribe yourself from your own posts/comments via @rleed
for links more than 1 year old, when we auto title them we now also add the year to the title via @rleed
🚨 new contributor alert GxqoRR on github added youtube embeds to discussion posts and comments

There were also many bug fixes that nearly everyone forwarded contributed to. I'm already noticing a few bugs from this release but if you notice anymore, shout!

view all related items

444 sats \ 0 replies \ @WeAreAllSatoshi fwd 23 Oct 2023

yay new contributor! great work, everyone!

526 sats \ 1 reply \ @aoeu 23 Oct 2023

Is there a way to turn on and off the feed personalization? It would be interesting to turn it on and off and see the changes. My worry about having too much personalization is that it is reinforcing. You get fed certain things because of the personalization, zap them, and then this reinforces getting more of the same kind of stuff and so on and so on. I'd worry I would miss out on the fringes.

121 sats \ 0 replies \ @k00b OP 23 Oct 2023

If you open SN in incognito, you can see the differences. There will be hardly any in most cases.

It'll be configurable eventually though!

31 sats \ 1 reply \ @siggy47 23 Oct 2023

Happy to see the link post text description. Now watch me never use it!

33 sats \ 0 replies \ @rleed fwd 23 Oct 2023

Lol! At least no complaints about not having it 😄

210 sats \ 9 replies \ @ek fwd 23 Oct 2023

@hn stopped working with this error message: error posting link: [{"message":"Cannot read properties of null (reading 'matchAll')"}]

Will take a look later today

edit: or actually, it posted just a few minutes ago but I still got an error in my logs

0 sats \ 8 replies \ @k00b OP 23 Oct 2023

Hmm might be related to delete bot

0 sats \ 7 replies \ @ek fwd 23 Oct 2023

And for some reason I still get empty push notifications even though I thought I fixed that.

Maybe my serviceworker didn't update? But it should update immediately.

Or that is caused by this caching issue you were talking about

0 sats \ 6 replies \ @k00b OP 23 Oct 2023

Cache issue should be fixed

I’d just search for matchall somewhere

210 sats \ 3 replies \ @ek fwd 23 Oct 2023

Mhh, matchAll is literally only used here but I think the default is not applied because we explicitly pass null as the argument:

lib/item.js:

export const getDeleteCommand = (text = '') => {
  const matches = [...text.matchAll(deletePattern)]
  const commands = matches?.map(match => ({ number: match[1], unit: match[2] }))
  return commands.length ? commands[commands.length - 1] : undefined
}

export const hasDeleteCommand = (text) => !!getDeleteCommand(text)

api/resolvers/item.js:

if (hasDeleteCommand(old.text)) {
    // delete any deletion jobs that were created from a prior version of the item
    await clearDeletionJobs(item, models)
  }