@Public_N_M_E and I are trying something new here. It's like an Allen Iverson crossover.
zaps forwarded to @Public_N_M_E (50%)
132 sats \ 10 replies \ @Undisciplined 11 Jan
Is this the long-term vision of how cross-posting will work? I don't care for it.
reply
519 sats \ 8 replies \ @Public_N_M_E fwd 11 Jan
i doubt it, from conversations with devs it seems as though crossposting is something they're looking at. but for now this is more of a workaround so that both communities get notified of where the action is happening and both posters split the zaps using the FWD function. i'm hoping its a temporary work around and the more demand we get for crossposting the higher up the priority lists it'll go.
reply
501 sats \ 7 replies \ @0xbitcoiner 11 Jan
If you implement crossposting, please don't put duplicate posts in the feed. It makes more sense to be a one-to-many system, not many-to-many.
reply
131 sats \ 5 replies \ @Undisciplined 11 Jan
It's interesting to think about how this should work. I'd say it should show up in it's most recent spot out of the territories you haven't muted. Does that make sense?
I think that's roughly how my nostr feed handles reposts.
reply
466 sats \ 3 replies \ @0xbitcoiner 11 Jan
I'm not sure if I understand correctly. A simple solution would be, if you're on the "home" feed, show the post if it's in at least one territory that isn't muted.
reply
110 sats \ 2 replies \ @Undisciplined 11 Jan
I agree for the "home" feed (and "top"). I was thinking about how to handle cross posts in the "recent" feed.
reply
466 sats \ 1 reply \ @0xbitcoiner 11 Jan
Exactly the same way as hot and top. In the "home" feed, we can choose hot, recent, top. Just don't repeat the post. The front-end part seems simple, but then you have the zaps distribution.
reply
200 sats \ 0 replies \ @Undisciplined 11 Jan
Fun problem for the dev team.
I've started several different replies with what I thought were the "obvious" solutions, before seeing problems with them and starting over.
reply on another page
10 sats \ 0 replies \ @Public_N_M_E fwd 11 Jan
Could be an interesting solution definitely.
reply
31 sats \ 0 replies \ @Public_N_M_E fwd 11 Jan
i agree there is going to be a good way of doing collaborative territory posts, but post duplications probably isnt the way. we shall see what the devs come up with.
reply
21 sats \ 0 replies \ @grayruby OP 11 Jan
Nope. This is the short term vision of us throwing stuff at the wall and seeing what sticks.
reply
50 sats \ 0 replies \ @Public_N_M_E fwd 11 Jan
🫡
reply