xChaos on Nostr: I am quite enthusiastic about the toot quoting feature recently announced by ...
I am quite enthusiastic about the toot quoting feature recently announced by nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqdc24kwyq59p57d63dpjr3qruh764dhmn3adh00tker63h6ugzj3qvvjewr (nprofile…jewr) ... yes, very often it just makes sense.
But I am not sure about adding too many new complex properties of toots (statuses). How would inter-platform Fedi compatibility of these new privacy levels be enforced, at all?
It would be much easier to associate "quotability" with certain levels of privacy/publicity, which we already have 4, but still very often use just the 2 extremes (all public/all private). If I mark something as globally public, I am fully aware it may be quoted by someone. However, the next "slightly less public" means often sometimes, I don't really want to promote much (and it means also promote by quoting). But this would mean adding feature to limit privacy retroactively, which is not provided yet (only as "delete and repost").
While allowing quoting to people who follow me is not always good bet, generally I wouldn't mind being quoted by people who I follow (I can still unfollow). Quotability attribute may be useful, but would add more complexity. Not being able to be quoted by people I block is must.
Generally, being quoted is more or less identical to reply and boost used together. So being notified is a must, because we are being already notified about replies and boosts.
Being able to block being boosted by someone is also the same feature as being able to block quoting. Sometimes, "keeping it simple and strong" and avoiding redundancy of features is the best design pattern, I believe...
#tldr #mastodon #fediverse #quote
But I am not sure about adding too many new complex properties of toots (statuses). How would inter-platform Fedi compatibility of these new privacy levels be enforced, at all?
It would be much easier to associate "quotability" with certain levels of privacy/publicity, which we already have 4, but still very often use just the 2 extremes (all public/all private). If I mark something as globally public, I am fully aware it may be quoted by someone. However, the next "slightly less public" means often sometimes, I don't really want to promote much (and it means also promote by quoting). But this would mean adding feature to limit privacy retroactively, which is not provided yet (only as "delete and repost").
While allowing quoting to people who follow me is not always good bet, generally I wouldn't mind being quoted by people who I follow (I can still unfollow). Quotability attribute may be useful, but would add more complexity. Not being able to be quoted by people I block is must.
Generally, being quoted is more or less identical to reply and boost used together. So being notified is a must, because we are being already notified about replies and boosts.
Being able to block being boosted by someone is also the same feature as being able to block quoting. Sometimes, "keeping it simple and strong" and avoiding redundancy of features is the best design pattern, I believe...
#tldr #mastodon #fediverse #quote