pull down to refresh

Ask SN - option to split tips
83 sats \ 14 comments \ @DarthCoin 18 Apr 2022 meta
@k00b What about having in SN a split stack? Let's say I start a thread or post a simply link to a video, podcast or whatever, that is not mine, created by me, I am just the poster. And I want that a % of the tips sats received on SN for that post to go to the original creator of that video and he deserve a % of my tips for that.
So something like LNbits have the SplitPayment where user can define to which SN user will go a % of the tips, or even a LN address (if the creator is not yet a SN user).
Or just a simply split cut with somebody the OP wants share.
I saw many posts here (I post myself too) some others content creation and is good that they will get back something for that. I am just the messenger, I don't deserve all the credit for that content.
Not sure if this is doable in SN, just an idea...
write
preview
related posts
90 sats \ 4 replies \ @based 18 Apr 2022
Isn't the most obvious and simple solution adequate; content creators with an interest in SN posts here?
reply
11 sats \ 3 replies \ @k00b 18 Apr 2022
Yes but often a creator will forget to post here or the poster feels weird about receiving tips so maybe they forward to HRF’s account.
reply
32 sats \ 2 replies \ @kr 18 Apr 2022
this idea of splitting payments is interesting, but it really does introduce a lot more complexity to the site in the way it’s being described in this thread. i think @based has a really good point.
splits would need to be shown on the main page, would create more clutter, and new fields that users would need to enter in order to create splits.
what if the person i want to split with doesn’t have a lightning address? what if they’re not a SN user? it’s a painful process to try and find someone’s lightning address by contacting them on email/twitter just so i can split 50 sats with them.
what if people start creating lightning addresses to impersonate people in attempts to attract more boosts? would stacker news verify lightning addresses belonging to certain prominent individuals?
here’s a simple solution that might help stacker news attract & support bitcoin developers, while also letting users split boosts with bitcoin devs.
any bitcoin devs who have contributed to bitcoin or lightning protocols via the mailing list can opt-in for a stacker news grant, by becoming SN users.
any SN users that want to share a % of their boosts with bitcoin developers can do so with zero overhead costs, and in a single setting change on their profile page.
reply
0 sats \ 0 replies \ @0391398253 19 Apr 2022
Scammers impersonating other people would not be solver by Bitcoin neither stacker news, you must accept that is something that is going to happen whatever you do.
Also splitting should be automatic to make the process easier. If an address isn't found, then the amount is divided among those address working.
  • Someone post content and the address of the creator.
  • someone respond by "tip 100"
  • 100 sats are send to that direction.
  • If more than one address is posted, then tip is splitted between the number of address.
  • if one address fail, payment es splited to the others ones working.
The part about splitting should be the more complex. Eventually could be simplified by "tip 100" where 100 sats are sent to every address.
reply
0 sats \ 0 replies \ @DarthCoin OP 18 Apr 2022
fair points. we are still so early.... :)
reply
33 sats \ 0 replies \ @uco 18 Apr 2022
my 2 sats opinion, make the split a fixed percentage for simplicity and ease of use. 50/50 sounds reasonable to me. 50% to original creator and 50% to reposter.
reply
36 sats \ 2 replies \ @k00b 18 Apr 2022
Yes this is something I'm looking to do soon. The biggest question I have: should it be a percentage the user sets or always just be fixed to 50% or 100% forwarding.
reply
13 sats \ 1 reply \ @k00b 18 Apr 2022
Working on this now. Maybe 80% forwarding is a nice happy, pareto-referencing medium?
reply
21 sats \ 0 replies \ @k00b 19 Apr 2022
Just shipped tip forwarding on posts ...
  1. It's hidden in the options pane
  2. It's 100% only
  3. can only forward to SN users
It's pretty basic support but I'll refine it over time.
All the other schemes are too complicated to start with - sending 1 sat at a time to lightning addresses is not simple. If lots of users end up forwarding, we'll refine it, but I suspect it'll see limited use.
reply
10 sats \ 2 replies \ @0391398253 18 Apr 2022
How could work?
  • content creator got a ln-address
  • user post content and quote creator with their ln-address
  • tip goes to content creator using their ln-address
reply
0 sats \ 0 replies \ @uco 19 Apr 2022
Yes! this will also incentivize content creators to obtain and publish a ln-address. What a fantastic onboarding tool since their audience will see the ln-address and ask "what is that?"
reply
0 sats \ 0 replies \ @0391398253 18 Apr 2022
Hey, look this video www.youtube.com
Credit to user@lndomain.com
If you put more users on credit then tips would be split among them.
Eventually you could attach the messages of the user to the content creator.
Being able to monetize your content is the more interesting aspect of lightning, second one is able to share that monetization among those help you to create that content. Just like breeze do with podcasting 2.0.
reply
0 sats \ 0 replies \ @Undergotten 19 Apr 2022
Sounds like a fine idea. I'd probably use that for the few videos, podcasts I post. Be kind of a sneaky (muuuahahaha!) way of on-boarding no-coiners, too.
reply
0 sats \ 0 replies \ @jeff 18 Apr 2022
Back in October, I suggested generalizing these kinds of threads into a protocol implemented via some kind of standard implemented via serverless code deployed to AWS or GCP.
Users could register these endpoints with the site, then select them from a drop down.
The endpoint would just need to take context in a standard form and return who got what sats. The site could expose these results for analysis to the community.
Those logs would show who's voting for what and how much they spend. And the responses could be analyzed as well.
Super simple example...
Request: { 'user' : @jeff, 'vote_sats' : 30, 'post_id' : 20807}
Response: { 'recipients' : [[15, @DarthCoin], [10, @k00b], [5, @SomeCharity]] }
It gets waaaaay cooler, the more context SN could inject into the request. (Eg. current vote count, total sats voted, current comment count, trust score? content URL? Age of post? Age of voter? Age of OP?)
reply