Is this the long-term vision of how cross-posting will work? I don't care for it.
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
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
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
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
I agree for the "home" feed (and "top"). I was thinking about how to handle cross posts in the "recent" feed.
reply
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
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
Could be an interesting solution definitely.
reply
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
Nope. This is the short term vision of us throwing stuff at the wall and seeing what sticks.
reply