#replycontrols — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #replycontrols, aggregated by home.social.
-
"Add Comment Controls"
Love seeing Loops prioritize people's safety!
https://github.com/joinloops/loops-server/releases/tag/v1.0.0-beta.10
-
"Add Comment Controls"
Love seeing Loops prioritize people's safety!
https://github.com/joinloops/loops-server/releases/tag/v1.0.0-beta.10
-
"Add Comment Controls"
Love seeing Loops prioritize people's safety!
https://github.com/joinloops/loops-server/releases/tag/v1.0.0-beta.10
-
"Add Comment Controls"
Love seeing Loops prioritize people's safety!
https://github.com/joinloops/loops-server/releases/tag/v1.0.0-beta.10
-
"Add Comment Controls"
Love seeing Loops prioritize people's safety!
https://github.com/joinloops/loops-server/releases/tag/v1.0.0-beta.10
-
Just an occasional reminder that disabling replies is the #1 requested feature from Mastodon.
https://github.com/mastodon/mastodon/issues?q=is%3Aissue%20state%3Aopen%20sort%3Areactions-%2B1-desc
(EDIT: Direct link, in case the above doesn't work for you: https://github.com/mastodon/mastodon/issues/8565)
Limiting who can reply is also worth giving a thumbs-up to, currently at #10.
https://github.com/mastodon/mastodon/issues/14762
#mastodon #fediverse #ReplyControls #SocialMedia #TrustAndSafety
-
Just an occasional reminder that disabling replies is the #1 requested feature from Mastodon.
https://github.com/mastodon/mastodon/issues?q=is%3Aissue%20state%3Aopen%20sort%3Areactions-%2B1-desc
(EDIT: Direct link, in case the above doesn't work for you: https://github.com/mastodon/mastodon/issues/8565)
Limiting who can reply is also worth giving a thumbs-up to, currently at #10.
https://github.com/mastodon/mastodon/issues/14762
#mastodon #fediverse #ReplyControls #SocialMedia #TrustAndSafety
-
Just an occasional reminder that disabling replies is the #1 requested feature from Mastodon.
https://github.com/mastodon/mastodon/issues?q=is%3Aissue%20state%3Aopen%20sort%3Areactions-%2B1-desc
(EDIT: Direct link, in case the above doesn't work for you: https://github.com/mastodon/mastodon/issues/8565)
Limiting who can reply is also worth giving a thumbs-up to, currently at #10.
https://github.com/mastodon/mastodon/issues/14762
#mastodon #fediverse #ReplyControls #SocialMedia #TrustAndSafety
-
Just an occasional reminder that disabling replies is the #1 requested feature from Mastodon.
https://github.com/mastodon/mastodon/issues?q=is%3Aissue%20state%3Aopen%20sort%3Areactions-%2B1-desc
(EDIT: Direct link, in case the above doesn't work for you: https://github.com/mastodon/mastodon/issues/8565)
Limiting who can reply is also worth giving a thumbs-up to, currently at #10.
https://github.com/mastodon/mastodon/issues/14762
#mastodon #fediverse #ReplyControls #SocialMedia #TrustAndSafety
-
Just an occasional reminder that disabling replies is the #1 requested feature from Mastodon.
https://github.com/mastodon/mastodon/issues?q=is%3Aissue%20state%3Aopen%20sort%3Areactions-%2B1-desc
(EDIT: Direct link, in case the above doesn't work for you: https://github.com/mastodon/mastodon/issues/8565)
Limiting who can reply is also worth giving a thumbs-up to, currently at #10.
https://github.com/mastodon/mastodon/issues/14762
#mastodon #fediverse #ReplyControls #SocialMedia #TrustAndSafety
-
@Rob Ricci @caterpillar @Stefan Bohacek @Ericka Simone This is exactly the problem.
I'm on both Hubzilla and (streams) with multiple channels, and I've been on Hubzilla under various guises for longer than the vast majority of Mastodon users have been on Mastodon. I guess you can say that I know both very well.
I can tell you that the possibilities of Hubzilla's permissions system are staggering. It works on up to three levels: for the entire channel (that's "account" in Mastospeak), for individual connections (that's "followers and followed" in Mastospeak), for individual content (posts and and entire conversations, but also images and other uploaded files and documents).
For example, you can grant or deny permission to- see your public profile (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- see your connections (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- see your public posts in your stream (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- send you their posts (this means public posts that aren't replies because replies are not posts on Hubzilla)
- like (that's "fave" in Mastospeak; you know, the star), dislike and comment on your posts
- send you DMs
- see your uploaded files (this requires OpenWebAuth magic sign-on which Mastodon has rejected, but this also extends to images and other media embedded into posts, comments and DMs)
All in all, Hubzilla has 18 such permissions, but these are the ones that matter from a Mastodon point of view. They can be granted or denied for your entire channel at seven or eight levels, and if they're denied at channel level, they can be granted for individual connections. Imagine that, on Mastodon, you could allow only certain followers to see your profile and your toots. Or you could only allow certain followed accounts to send you their toots. All of this is reality on Hubzilla right now.
Better yet: You know that you can send toots only to mentioned accounts on Mastodon. Hubzilla exceeds and improves upon this in three ways. First of all, you can send posts to individual connections. Or to a certain privacy group (from a Mastodon POV, that's a list on steroids). Or to a custom selection of individual connections and privacy groups while even being able to exclude certain other connections or privacy groups. This goes way beyond Mastodon's "mentioned = allowed to see".
But this doesn't only define who will receive your post. It also defines who is permitted to see your post.
And: The permissions of a post are inherited by the entire conversation. Comments always have the same permissions as the top post. There's no restricting the permissions in a comment, and there's no relaxing the limitations of a comment. It's impossible to pull other Fediverse users into a private conversation by mentioning them if the top post wasn't targetted at them.
Even better yet: You can allow or disallow comments on individual posts (remember that a post on Hubzilla is only a post if it starts a conversation, not if it's a reply).
On top of all this, Hubzilla's filters are both vastly more powerful than Mastodon's filters and easier to use. Mastodon requires you to set up one new filter for each word that you want filtered. It's always blocklisting. And it's always account-wide.
Hubzilla covers Mastodon's entire filter functionality with one or two text fields. You have one blocklist for the whole channel. And you have an optional extra feature named "NSFW" with its own filter list that generated individual, reader-side content warnings for you. The equivalent of defining a new filter on Mastodon is to add a new line to one of these filter lists. Want to back them up? Just copy-paste them into a text file.
But wait, there's more: Hubzilla also has a channel-wide allowlist. If you only want to see certain content in your stream, you can allowlist certain keywords.
Hubzilla even optionally has one blocklist and one allowlist per connection. Imagine you could filter individual followed accounts on Mastodon.
Hubzilla's filter lists support regular expressions. There is also a "filter syntax" that lets you filter by whether a message is a top post or not, whether a message is public or private, whether it's a repeat (that's "boost" in Mastospeak or "retoot" for those of you who still have Twitter on the brain). The filter syntax even lets you use Boolean operators.
(streams) and Forte are similar. Their permissions are somewhat different (you don't need permissions for wikis and websites if you don't have wikis and websites). The permissions system is vastly easier to use because it's no longer template-based. You can simply switch permissions on and off for your channel as well as for connections. And you can choose to have even more options for reply control.
Again, all this exists in the Fediverse right now. And most of it has existed for longer than Mastodon. Some of this dates back to the earliest days of Friendica in May, 2010.
Unfortunately, next to nobody knows.
For most Mastodon features, the features that Mastodon has are the features that the Fediverse has. If Mastodon doesn't have it, the Fediverse doesn't. Not only is Mastodon the default, but there's nothing that strays from this default. That's why Mastodon users keep wishing for "the Fediverse" to introduce features which Friendica has had for almost 16 years already. Or which Hubzilla has had for over a decade.
In addition, probably not even 10% of all Mastodon users have ever heard of Hubzilla. Probably not even 1% of all Mastodon users know what Hubzilla can do. And even only the existence of (streams) and Forte is almost entirely unknown outside of (streams) and Forte themselves and Hubzilla.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hubzilla #Streams #(streams) #Forte #Permission #Permissions #ReplyControl #ReplyControls #Filter #Filters #MastodonCentricism #MastodonNormativity -
@Rob Ricci @caterpillar @Stefan Bohacek @Ericka Simone This is exactly the problem.
I'm on both Hubzilla and (streams) with multiple channels, and I've been on Hubzilla under various guises for longer than the vast majority of Mastodon users have been on Mastodon. I guess you can say that I know both very well.
I can tell you that the possibilities of Hubzilla's permissions system are staggering. It works on up to three levels: for the entire channel (that's "account" in Mastospeak), for individual connections (that's "followers and followed" in Mastospeak), for individual content (posts and and entire conversations, but also images and other uploaded files and documents).
For example, you can grant or deny permission to- see your public profile (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- see your connections (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- see your public posts in your stream (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- send you their posts (this means public posts that aren't replies because replies are not posts on Hubzilla)
- like (that's "fave" in Mastospeak; you know, the star), dislike and comment on your posts
- send you DMs
- see your uploaded files (this requires OpenWebAuth magic sign-on which Mastodon has rejected, but this also extends to images and other media embedded into posts, comments and DMs)
All in all, Hubzilla has 18 such permissions, but these are the ones that matter from a Mastodon point of view. They can be granted or denied for your entire channel at seven or eight levels, and if they're denied at channel level, they can be granted for individual connections. Imagine that, on Mastodon, you could allow only certain followers to see your profile and your toots. Or you could only allow certain followed accounts to send you their toots. All of this is reality on Hubzilla right now.
Better yet: You know that you can send toots only to mentioned accounts on Mastodon. Hubzilla exceeds and improves upon this in three ways. First of all, you can send posts to individual connections. Or to a certain privacy group (from a Mastodon POV, that's a list on steroids). Or to a custom selection of individual connections and privacy groups while even being able to exclude certain other connections or privacy groups. This goes way beyond Mastodon's "mentioned = allowed to see".
But this doesn't only define who will receive your post. It also defines who is permitted to see your post.
And: The permissions of a post are inherited by the entire conversation. Comments always have the same permissions as the top post. There's no restricting the permissions in a comment, and there's no relaxing the limitations of a comment. It's impossible to pull other Fediverse users into a private conversation by mentioning them if the top post wasn't targetted at them.
Even better yet: You can allow or disallow comments on individual posts (remember that a post on Hubzilla is only a post if it starts a conversation, not if it's a reply).
On top of all this, Hubzilla's filters are both vastly more powerful than Mastodon's filters and easier to use. Mastodon requires you to set up one new filter for each word that you want filtered. It's always blocklisting. And it's always account-wide.
Hubzilla covers Mastodon's entire filter functionality with one or two text fields. You have one blocklist for the whole channel. And you have an optional extra feature named "NSFW" with its own filter list that generated individual, reader-side content warnings for you. The equivalent of defining a new filter on Mastodon is to add a new line to one of these filter lists. Want to back them up? Just copy-paste them into a text file.
But wait, there's more: Hubzilla also has a channel-wide allowlist. If you only want to see certain content in your stream, you can allowlist certain keywords.
Hubzilla even optionally has one blocklist and one allowlist per connection. Imagine you could filter individual followed accounts on Mastodon.
Hubzilla's filter lists support regular expressions. There is also a "filter syntax" that lets you filter by whether a message is a top post or not, whether a message is public or private, whether it's a repeat (that's "boost" in Mastospeak or "retoot" for those of you who still have Twitter on the brain). The filter syntax even lets you use Boolean operators.
(streams) and Forte are similar. Their permissions are somewhat different (you don't need permissions for wikis and websites if you don't have wikis and websites). The permissions system is vastly easier to use because it's no longer template-based. You can simply switch permissions on and off for your channel as well as for connections. And you can choose to have even more options for reply control.
Again, all this exists in the Fediverse right now. And most of it has existed for longer than Mastodon. Some of this dates back to the earliest days of Friendica in May, 2010.
Unfortunately, next to nobody knows.
For most Mastodon features, the features that Mastodon has are the features that the Fediverse has. If Mastodon doesn't have it, the Fediverse doesn't. Not only is Mastodon the default, but there's nothing that strays from this default. That's why Mastodon users keep wishing for "the Fediverse" to introduce features which Friendica has had for almost 16 years already. Or which Hubzilla has had for over a decade.
In addition, probably not even 10% of all Mastodon users have ever heard of Hubzilla. Probably not even 1% of all Mastodon users know what Hubzilla can do. And even only the existence of (streams) and Forte is almost entirely unknown outside of (streams) and Forte themselves and Hubzilla.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hubzilla #Streams #(streams) #Forte #Permission #Permissions #ReplyControl #ReplyControls #Filter #Filters #MastodonCentricism #MastodonNormativity -
@Rob Ricci @caterpillar @Stefan Bohacek @Ericka Simone This is exactly the problem.
I'm on both Hubzilla and (streams) with multiple channels, and I've been on Hubzilla under various guises for longer than the vast majority of Mastodon users have been on Mastodon. I guess you can say that I know both very well.
I can tell you that the possibilities of Hubzilla's permissions system are staggering. It works on up to three levels: for the entire channel (that's "account" in Mastospeak), for individual connections (that's "followers and followed" in Mastospeak), for individual content (posts and and entire conversations, but also images and other uploaded files and documents).
For example, you can grant or deny permission to- see your public profile (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- see your connections (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- see your public posts in your stream (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- send you their posts (this means public posts that aren't replies because replies are not posts on Hubzilla)
- like (that's "fave" in Mastospeak; you know, the star), dislike and comment on your posts
- send you DMs
- see your uploaded files (this requires OpenWebAuth magic sign-on which Mastodon has rejected, but this also extends to images and other media embedded into posts, comments and DMs)
All in all, Hubzilla has 18 such permissions, but these are the ones that matter from a Mastodon point of view. They can be granted or denied for your entire channel at seven or eight levels, and if they're denied at channel level, they can be granted for individual connections. Imagine that, on Mastodon, you could allow only certain followers to see your profile and your toots. Or you could only allow certain followed accounts to send you their toots. All of this is reality on Hubzilla right now.
Better yet: You know that you can send toots only to mentioned accounts on Mastodon. Hubzilla exceeds and improves upon this in three ways. First of all, you can send posts to individual connections. Or to a certain privacy group (from a Mastodon POV, that's a list on steroids). Or to a custom selection of individual connections and privacy groups while even being able to exclude certain other connections or privacy groups. This goes way beyond Mastodon's "mentioned = allowed to see".
But this doesn't only define who will receive your post. It also defines who is permitted to see your post.
And: The permissions of a post are inherited by the entire conversation. Comments always have the same permissions as the top post. There's no restricting the permissions in a comment, and there's no relaxing the limitations of a comment. It's impossible to pull other Fediverse users into a private conversation by mentioning them if the top post wasn't targetted at them.
Even better yet: You can allow or disallow comments on individual posts (remember that a post on Hubzilla is only a post if it starts a conversation, not if it's a reply).
On top of all this, Hubzilla's filters are both vastly more powerful than Mastodon's filters and easier to use. Mastodon requires you to set up one new filter for each word that you want filtered. It's always blocklisting. And it's always account-wide.
Hubzilla covers Mastodon's entire filter functionality with one or two text fields. You have one blocklist for the whole channel. And you have an optional extra feature named "NSFW" with its own filter list that generated individual, reader-side content warnings for you. The equivalent of defining a new filter on Mastodon is to add a new line to one of these filter lists. Want to back them up? Just copy-paste them into a text file.
But wait, there's more: Hubzilla also has a channel-wide allowlist. If you only want to see certain content in your stream, you can allowlist certain keywords.
Hubzilla even optionally has one blocklist and one allowlist per connection. Imagine you could filter individual followed accounts on Mastodon.
Hubzilla's filter lists support regular expressions. There is also a "filter syntax" that lets you filter by whether a message is a top post or not, whether a message is public or private, whether it's a repeat (that's "boost" in Mastospeak or "retoot" for those of you who still have Twitter on the brain). The filter syntax even lets you use Boolean operators.
(streams) and Forte are similar. Their permissions are somewhat different (you don't need permissions for wikis and websites if you don't have wikis and websites). The permissions system is vastly easier to use because it's no longer template-based. You can simply switch permissions on and off for your channel as well as for connections. And you can choose to have even more options for reply control.
Again, all this exists in the Fediverse right now. And most of it has existed for longer than Mastodon. Some of this dates back to the earliest days of Friendica in May, 2010.
Unfortunately, next to nobody knows.
For most Mastodon features, the features that Mastodon has are the features that the Fediverse has. If Mastodon doesn't have it, the Fediverse doesn't. Not only is Mastodon the default, but there's nothing that strays from this default. That's why Mastodon users keep wishing for "the Fediverse" to introduce features which Friendica has had for almost 16 years already. Or which Hubzilla has had for over a decade.
In addition, probably not even 10% of all Mastodon users have ever heard of Hubzilla. Probably not even 1% of all Mastodon users know what Hubzilla can do. And even only the existence of (streams) and Forte is almost entirely unknown outside of (streams) and Forte themselves and Hubzilla.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hubzilla #Streams #(streams) #Forte #Permission #Permissions #ReplyControl #ReplyControls #Filter #Filters #MastodonCentricism #MastodonNormativity -
@Rob Ricci @caterpillar @Stefan Bohacek @Ericka Simone This is exactly the problem.
I'm on both Hubzilla and (streams) with multiple channels, and I've been on Hubzilla under various guises for longer than the vast majority of Mastodon users have been on Mastodon. I guess you can say that I know both very well.
I can tell you that the possibilities of Hubzilla's permissions system are staggering. It works on up to three levels: for the entire channel (that's "account" in Mastospeak), for individual connections (that's "followers and followed" in Mastospeak), for individual content (posts and and entire conversations, but also images and other uploaded files and documents).
For example, you can grant or deny permission to- see your public profile (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- see your connections (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- see your public posts in your stream (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- send you their posts (this means public posts that aren't replies because replies are not posts on Hubzilla)
- like (that's "fave" in Mastospeak; you know, the star), dislike and comment on your posts
- send you DMs
- see your uploaded files (this requires OpenWebAuth magic sign-on which Mastodon has rejected, but this also extends to images and other media embedded into posts, comments and DMs)
All in all, Hubzilla has 18 such permissions, but these are the ones that matter from a Mastodon point of view. They can be granted or denied for your entire channel at seven or eight levels, and if they're denied at channel level, they can be granted for individual connections. Imagine that, on Mastodon, you could allow only certain followers to see your profile and your toots. Or you could only allow certain followed accounts to send you their toots. All of this is reality on Hubzilla right now.
Better yet: You know that you can send toots only to mentioned accounts on Mastodon. Hubzilla exceeds and improves upon this in three ways. First of all, you can send posts to individual connections. Or to a certain privacy group (from a Mastodon POV, that's a list on steroids). Or to a custom selection of individual connections and privacy groups while even being able to exclude certain other connections or privacy groups. This goes way beyond Mastodon's "mentioned = allowed to see".
But this doesn't only define who will receive your post. It also defines who is permitted to see your post.
And: The permissions of a post are inherited by the entire conversation. Comments always have the same permissions as the top post. There's no restricting the permissions in a comment, and there's no relaxing the limitations of a comment. It's impossible to pull other Fediverse users into a private conversation by mentioning them if the top post wasn't targetted at them.
Even better yet: You can allow or disallow comments on individual posts (remember that a post on Hubzilla is only a post if it starts a conversation, not if it's a reply).
On top of all this, Hubzilla's filters are both vastly more powerful than Mastodon's filters and easier to use. Mastodon requires you to set up one new filter for each word that you want filtered. It's always blocklisting. And it's always account-wide.
Hubzilla covers Mastodon's entire filter functionality with one or two text fields. You have one blocklist for the whole channel. And you have an optional extra feature named "NSFW" with its own filter list that generated individual, reader-side content warnings for you. The equivalent of defining a new filter on Mastodon is to add a new line to one of these filter lists. Want to back them up? Just copy-paste them into a text file.
But wait, there's more: Hubzilla also has a channel-wide allowlist. If you only want to see certain content in your stream, you can allowlist certain keywords.
Hubzilla even optionally has one blocklist and one allowlist per connection. Imagine you could filter individual followed accounts on Mastodon.
Hubzilla's filter lists support regular expressions. There is also a "filter syntax" that lets you filter by whether a message is a top post or not, whether a message is public or private, whether it's a repeat (that's "boost" in Mastospeak or "retoot" for those of you who still have Twitter on the brain). The filter syntax even lets you use Boolean operators.
(streams) and Forte are similar. Their permissions are somewhat different (you don't need permissions for wikis and websites if you don't have wikis and websites). The permissions system is vastly easier to use because it's no longer template-based. You can simply switch permissions on and off for your channel as well as for connections. And you can choose to have even more options for reply control.
Again, all this exists in the Fediverse right now. And most of it has existed for longer than Mastodon. Some of this dates back to the earliest days of Friendica in May, 2010.
Unfortunately, next to nobody knows.
For most Mastodon features, the features that Mastodon has are the features that the Fediverse has. If Mastodon doesn't have it, the Fediverse doesn't. Not only is Mastodon the default, but there's nothing that strays from this default. That's why Mastodon users keep wishing for "the Fediverse" to introduce features which Friendica has had for almost 16 years already. Or which Hubzilla has had for over a decade.
In addition, probably not even 10% of all Mastodon users have ever heard of Hubzilla. Probably not even 1% of all Mastodon users know what Hubzilla can do. And even only the existence of (streams) and Forte is almost entirely unknown outside of (streams) and Forte themselves and Hubzilla.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hubzilla #Streams #(streams) #Forte #Permission #Permissions #ReplyControl #ReplyControls #Filter #Filters #MastodonCentricism #MastodonNormativity -
@Rob Ricci @caterpillar @Stefan Bohacek @Ericka Simone This is exactly the problem.
I'm on both Hubzilla and (streams) with multiple channels, and I've been on Hubzilla under various guises for longer than the vast majority of Mastodon users have been on Mastodon. I guess you can say that I know both very well.
I can tell you that the possibilities of Hubzilla's permissions system are staggering. It works on up to three levels: for the entire channel (that's "account" in Mastospeak), for individual connections (that's "followers and followed" in Mastospeak), for individual content (posts and and entire conversations, but also images and other uploaded files and documents).
For example, you can grant or deny permission to- see your public profile (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- see your connections (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- see your public posts in your stream (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
- send you their posts (this means public posts that aren't replies because replies are not posts on Hubzilla)
- like (that's "fave" in Mastospeak; you know, the star), dislike and comment on your posts
- send you DMs
- see your uploaded files (this requires OpenWebAuth magic sign-on which Mastodon has rejected, but this also extends to images and other media embedded into posts, comments and DMs)
All in all, Hubzilla has 18 such permissions, but these are the ones that matter from a Mastodon point of view. They can be granted or denied for your entire channel at seven or eight levels, and if they're denied at channel level, they can be granted for individual connections. Imagine that, on Mastodon, you could allow only certain followers to see your profile and your toots. Or you could only allow certain followed accounts to send you their toots. All of this is reality on Hubzilla right now.
Better yet: You know that you can send toots only to mentioned accounts on Mastodon. Hubzilla exceeds and improves upon this in three ways. First of all, you can send posts to individual connections. Or to a certain privacy group (from a Mastodon POV, that's a list on steroids). Or to a custom selection of individual connections and privacy groups while even being able to exclude certain other connections or privacy groups. This goes way beyond Mastodon's "mentioned = allowed to see".
But this doesn't only define who will receive your post. It also defines who is permitted to see your post.
And: The permissions of a post are inherited by the entire conversation. Comments always have the same permissions as the top post. There's no restricting the permissions in a comment, and there's no relaxing the limitations of a comment. It's impossible to pull other Fediverse users into a private conversation by mentioning them if the top post wasn't targetted at them.
Even better yet: You can allow or disallow comments on individual posts (remember that a post on Hubzilla is only a post if it starts a conversation, not if it's a reply).
On top of all this, Hubzilla's filters are both vastly more powerful than Mastodon's filters and easier to use. Mastodon requires you to set up one new filter for each word that you want filtered. It's always blocklisting. And it's always account-wide.
Hubzilla covers Mastodon's entire filter functionality with one or two text fields. You have one blocklist for the whole channel. And you have an optional extra feature named "NSFW" with its own filter list that generated individual, reader-side content warnings for you. The equivalent of defining a new filter on Mastodon is to add a new line to one of these filter lists. Want to back them up? Just copy-paste them into a text file.
But wait, there's more: Hubzilla also has a channel-wide allowlist. If you only want to see certain content in your stream, you can allowlist certain keywords.
Hubzilla even optionally has one blocklist and one allowlist per connection. Imagine you could filter individual followed accounts on Mastodon.
Hubzilla's filter lists support regular expressions. There is also a "filter syntax" that lets you filter by whether a message is a top post or not, whether a message is public or private, whether it's a repeat (that's "boost" in Mastospeak or "retoot" for those of you who still have Twitter on the brain). The filter syntax even lets you use Boolean operators.
(streams) and Forte are similar. Their permissions are somewhat different (you don't need permissions for wikis and websites if you don't have wikis and websites). The permissions system is vastly easier to use because it's no longer template-based. You can simply switch permissions on and off for your channel as well as for connections. And you can choose to have even more options for reply control.
Again, all this exists in the Fediverse right now. And most of it has existed for longer than Mastodon. Some of this dates back to the earliest days of Friendica in May, 2010.
Unfortunately, next to nobody knows.
For most Mastodon features, the features that Mastodon has are the features that the Fediverse has. If Mastodon doesn't have it, the Fediverse doesn't. Not only is Mastodon the default, but there's nothing that strays from this default. That's why Mastodon users keep wishing for "the Fediverse" to introduce features which Friendica has had for almost 16 years already. Or which Hubzilla has had for over a decade.
In addition, probably not even 10% of all Mastodon users have ever heard of Hubzilla. Probably not even 1% of all Mastodon users know what Hubzilla can do. And even only the existence of (streams) and Forte is almost entirely unknown outside of (streams) and Forte themselves and Hubzilla.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hubzilla #Streams #(streams) #Forte #Permission #Permissions #ReplyControl #ReplyControls #Filter #Filters #MastodonCentricism #MastodonNormativity -
@Julian FietkauExactly because racism isn't solved with the flick of a switch, we need to make improvements where we can. Block lists and reply controls in Mastodon won't eliminate racism from the fediverse, but they can make some people's time here somewhat (or a lot) better.
Only if Mastodon devs consult with the rest of the Fediverse instead of surprising everyone with a solution that's incompatible with just about everything else.
See quote-posts and the quote-post opt-in. Mastodon's solution supposes that the whole Fediverse is Mastodon or at least works like Mastodon.
Users on Mastodon 4.5 or newer can set any of their posts to un-quote-post-able. But still, anyone on Pleroma, Akkoma, Misskey, Calckey, Firefish, CherryPick, Sharkey, Iceshrimp, Catodon, Mitra, Friendica, Hubzilla, (streams), Forte etc. can quote-post these self-same un-quote-post-able posts with zero resistance.
At the same time, users on Mastodon 4.5 or newer cannot quote-post anything that doesn't come from Mastodon because Mastodon expects there to be its own proprietary, non-standard quote-post opt-in.
It's easy from a Mastodon point of view to consider Mastodon the one and only gold standard in the Fediverse and point fingers at the non-Mastodon Fediverse. But don't forget that Friendica has had quote-posts for five and a half years longer than Mastodon has even existed and for over 15 years longer than Mastodon has had them.
By the way, while I don't know about Friendica, Hubzilla has reply control. It has had it probably since 2012. It has reply control features that go way beyond what even the Mastodon devs can imagine, much less what's technologically possible on Mastodon. And (streams) and Forte manage to go even further than their ancestor Hubzilla in terms of reply control.
So Mastodon will not introduce reply control to the Fediverse. It can't expect everything else in the Fediverse to adopt its own reply control technology, much less throw out their existing reply control technology in favour of Mastodon's.
There used to be FEP-5624 that was actually proposed by a Mastodon dev. There was a lenghty discussion about this FEP draft that involved devs from all across the Fediverse, even the Hubzilla creator and (streams) and Forte maintainer. However, the FEP draft was probably abandoned in 2023 already and withdrawn two weeks ago.
The lesson learned for Mastodon may be that first introducing a FEP and discussing it in the community and with devs of stuff that's nothing like Mastodon leads nowhere, and the only way to get things done is to first build it into Mastodon, then maybe try to make it into a FEP and then demand the whole rest of the Fediverse adopt it or face being branded as broken by design.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ReplyControl #ReplyControls #FEP_5624 -
@Julian FietkauExactly because racism isn't solved with the flick of a switch, we need to make improvements where we can. Block lists and reply controls in Mastodon won't eliminate racism from the fediverse, but they can make some people's time here somewhat (or a lot) better.
Only if Mastodon devs consult with the rest of the Fediverse instead of surprising everyone with a solution that's incompatible with just about everything else.
See quote-posts and the quote-post opt-in. Mastodon's solution supposes that the whole Fediverse is Mastodon or at least works like Mastodon.
Users on Mastodon 4.5 or newer can set any of their posts to un-quote-post-able. But still, anyone on Pleroma, Akkoma, Misskey, Calckey, Firefish, CherryPick, Sharkey, Iceshrimp, Catodon, Mitra, Friendica, Hubzilla, (streams), Forte etc. can quote-post these self-same un-quote-post-able posts with zero resistance.
At the same time, users on Mastodon 4.5 or newer cannot quote-post anything that doesn't come from Mastodon because Mastodon expects there to be its own proprietary, non-standard quote-post opt-in.
It's easy from a Mastodon point of view to consider Mastodon the one and only gold standard in the Fediverse and point fingers at the non-Mastodon Fediverse. But don't forget that Friendica has had quote-posts for five and a half years longer than Mastodon has even existed and for over 15 years longer than Mastodon has had them.
By the way, while I don't know about Friendica, Hubzilla has reply control. It has had it probably since 2012. It has reply control features that go way beyond what even the Mastodon devs can imagine, much less what's technologically possible on Mastodon. And (streams) and Forte manage to go even further than their ancestor Hubzilla in terms of reply control.
So Mastodon will not introduce reply control to the Fediverse. It can't expect everything else in the Fediverse to adopt its own reply control technology, much less throw out their existing reply control technology in favour of Mastodon's.
There used to be FEP-5624 that was actually proposed by a Mastodon dev. There was a lenghty discussion about this FEP draft that involved devs from all across the Fediverse, even the Hubzilla creator and (streams) and Forte maintainer. However, the FEP draft was probably abandoned in 2023 already and withdrawn two weeks ago.
The lesson learned for Mastodon may be that first introducing a FEP and discussing it in the community and with devs of stuff that's nothing like Mastodon leads nowhere, and the only way to get things done is to first build it into Mastodon, then maybe try to make it into a FEP and then demand the whole rest of the Fediverse adopt it or face being branded as broken by design.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ReplyControl #ReplyControls #FEP_5624 -
@Julian FietkauExactly because racism isn't solved with the flick of a switch, we need to make improvements where we can. Block lists and reply controls in Mastodon won't eliminate racism from the fediverse, but they can make some people's time here somewhat (or a lot) better.
Only if Mastodon devs consult with the rest of the Fediverse instead of surprising everyone with a solution that's incompatible with just about everything else.
See quote-posts and the quote-post opt-in. Mastodon's solution supposes that the whole Fediverse is Mastodon or at least works like Mastodon.
Users on Mastodon 4.5 or newer can set any of their posts to un-quote-post-able. But still, anyone on Pleroma, Akkoma, Misskey, Calckey, Firefish, CherryPick, Sharkey, Iceshrimp, Catodon, Mitra, Friendica, Hubzilla, (streams), Forte etc. can quote-post these self-same un-quote-post-able posts with zero resistance.
At the same time, users on Mastodon 4.5 or newer cannot quote-post anything that doesn't come from Mastodon because Mastodon expects there to be its own proprietary, non-standard quote-post opt-in.
It's easy from a Mastodon point of view to consider Mastodon the one and only gold standard in the Fediverse and point fingers at the non-Mastodon Fediverse. But don't forget that Friendica has had quote-posts for five and a half years longer than Mastodon has even existed and for over 15 years longer than Mastodon has had them.
By the way, while I don't know about Friendica, Hubzilla has reply control. It has had it probably since 2012. It has reply control features that go way beyond what even the Mastodon devs can imagine, much less what's technologically possible on Mastodon. And (streams) and Forte manage to go even further than their ancestor Hubzilla in terms of reply control.
So Mastodon will not introduce reply control to the Fediverse. It can't expect everything else in the Fediverse to adopt its own reply control technology, much less throw out their existing reply control technology in favour of Mastodon's.
There used to be FEP-5624 that was actually proposed by a Mastodon dev. There was a lenghty discussion about this FEP draft that involved devs from all across the Fediverse, even the Hubzilla creator and (streams) and Forte maintainer. However, the FEP draft was probably abandoned in 2023 already and withdrawn two weeks ago.
The lesson learned for Mastodon may be that first introducing a FEP and discussing it in the community and with devs of stuff that's nothing like Mastodon leads nowhere, and the only way to get things done is to first build it into Mastodon, then maybe try to make it into a FEP and then demand the whole rest of the Fediverse adopt it or face being branded as broken by design.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ReplyControl #ReplyControls #FEP_5624 -
@Julian FietkauExactly because racism isn't solved with the flick of a switch, we need to make improvements where we can. Block lists and reply controls in Mastodon won't eliminate racism from the fediverse, but they can make some people's time here somewhat (or a lot) better.
Only if Mastodon devs consult with the rest of the Fediverse instead of surprising everyone with a solution that's incompatible with just about everything else.
See quote-posts and the quote-post opt-in. Mastodon's solution supposes that the whole Fediverse is Mastodon or at least works like Mastodon.
Users on Mastodon 4.5 or newer can set any of their posts to un-quote-post-able. But still, anyone on Pleroma, Akkoma, Misskey, Calckey, Firefish, CherryPick, Sharkey, Iceshrimp, Catodon, Mitra, Friendica, Hubzilla, (streams), Forte etc. can quote-post these self-same un-quote-post-able posts with zero resistance.
At the same time, users on Mastodon 4.5 or newer cannot quote-post anything that doesn't come from Mastodon because Mastodon expects there to be its own proprietary, non-standard quote-post opt-in.
It's easy from a Mastodon point of view to consider Mastodon the one and only gold standard in the Fediverse and point fingers at the non-Mastodon Fediverse. But don't forget that Friendica has had quote-posts for five and a half years longer than Mastodon has even existed and for over 15 years longer than Mastodon has had them.
By the way, while I don't know about Friendica, Hubzilla has reply control. It has had it probably since 2012. It has reply control features that go way beyond what even the Mastodon devs can imagine, much less what's technologically possible on Mastodon. And (streams) and Forte manage to go even further than their ancestor Hubzilla in terms of reply control.
So Mastodon will not introduce reply control to the Fediverse. It can't expect everything else in the Fediverse to adopt its own reply control technology, much less throw out their existing reply control technology in favour of Mastodon's.
There used to be FEP-5624 that was actually proposed by a Mastodon dev. There was a lenghty discussion about this FEP draft that involved devs from all across the Fediverse, even the Hubzilla creator and (streams) and Forte maintainer. However, the FEP draft was probably abandoned in 2023 already and withdrawn two weeks ago.
The lesson learned for Mastodon may be that first introducing a FEP and discussing it in the community and with devs of stuff that's nothing like Mastodon leads nowhere, and the only way to get things done is to first build it into Mastodon, then maybe try to make it into a FEP and then demand the whole rest of the Fediverse adopt it or face being branded as broken by design.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ReplyControl #ReplyControls #FEP_5624 -
@Julian FietkauExactly because racism isn't solved with the flick of a switch, we need to make improvements where we can. Block lists and reply controls in Mastodon won't eliminate racism from the fediverse, but they can make some people's time here somewhat (or a lot) better.
Only if Mastodon devs consult with the rest of the Fediverse instead of surprising everyone with a solution that's incompatible with just about everything else.
See quote-posts and the quote-post opt-in. Mastodon's solution supposes that the whole Fediverse is Mastodon or at least works like Mastodon.
Users on Mastodon 4.5 or newer can set any of their posts to un-quote-post-able. But still, anyone on Pleroma, Akkoma, Misskey, Calckey, Firefish, CherryPick, Sharkey, Iceshrimp, Catodon, Mitra, Friendica, Hubzilla, (streams), Forte etc. can quote-post these self-same un-quote-post-able posts with zero resistance.
At the same time, users on Mastodon 4.5 or newer cannot quote-post anything that doesn't come from Mastodon because Mastodon expects there to be its own proprietary, non-standard quote-post opt-in.
It's easy from a Mastodon point of view to consider Mastodon the one and only gold standard in the Fediverse and point fingers at the non-Mastodon Fediverse. But don't forget that Friendica has had quote-posts for five and a half years longer than Mastodon has even existed and for over 15 years longer than Mastodon has had them.
By the way, while I don't know about Friendica, Hubzilla has reply control. It has had it probably since 2012. It has reply control features that go way beyond what even the Mastodon devs can imagine, much less what's technologically possible on Mastodon. And (streams) and Forte manage to go even further than their ancestor Hubzilla in terms of reply control.
So Mastodon will not introduce reply control to the Fediverse. It can't expect everything else in the Fediverse to adopt its own reply control technology, much less throw out their existing reply control technology in favour of Mastodon's.
There used to be FEP-5624 that was actually proposed by a Mastodon dev. There was a lenghty discussion about this FEP draft that involved devs from all across the Fediverse, even the Hubzilla creator and (streams) and Forte maintainer. However, the FEP draft was probably abandoned in 2023 already and withdrawn two weeks ago.
The lesson learned for Mastodon may be that first introducing a FEP and discussing it in the community and with devs of stuff that's nothing like Mastodon leads nowhere, and the only way to get things done is to first build it into Mastodon, then maybe try to make it into a FEP and then demand the whole rest of the Fediverse adopt it or face being branded as broken by design.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #ReplyControl #ReplyControls #FEP_5624 -
Any #GoToSocial developers, or anyone else who might know what the hold-up with publishing the FEP for reply controls is, interested in chiming in?
-
Any #GoToSocial developers, or anyone else who might know what the hold-up with publishing the FEP for reply controls is, interested in chiming in?
-
Any #GoToSocial developers, or anyone else who might know what the hold-up with publishing the FEP for reply controls is, interested in chiming in?
-
Any #GoToSocial developers, or anyone else who might know what the hold-up with publishing the FEP for reply controls is, interested in chiming in?
-
Any #GoToSocial developers, or anyone else who might know what the hold-up with publishing the FEP for reply controls is, interested in chiming in?
-
@Stefan BohacekAnd yes, I hope better reply/interaction controls are coming soon, I know some of that is planned right after quote posts are finished. Really can't wait to see that!
And that, too, will only work within Mastodon.
Also, that, too, won't be a "Mastodon first" feature. At least Hubzilla, (streams) and Forte have reply and interaction controls included in their permissions systems which, in a way, work Fediverse-wide.
Within themselves and each other, they actually make impossible what isn't allowed. For example, if you aren't allowed to repeat (= boost) or share (= quote-post) a post or a comment, you don't even have the button. These permissions aren't understood anywhere outside these three yet, but I've got higher hopes that this permissions system will be cast into FEPs than that Mastodon's hacks will be.
In fact, Hubzilla, (streams) and Forte have reply control on three levels:- channel-wide (who is generally allowed to reply; Hubzilla has eight levels, (streams) and Forte have three)
- for individual connections
- per post (on Hubzilla, commenting on a post can be disallowed altogether; on (streams) and Forte, additionally, commenting can be limited to your full connections, and a time can be defined from which commenting will no longer be allowed)
Again, within these three, if commenting is not allowed, the UI elements for commenting will be missing. Outsiders may be able to comment, but all three block disallowed comments on a server level, i.e. they aren't deleted from the inbox, they are kept from entering the inbox in the first place. And so they don't appear in the thread for all those who support threaded conversations.
It'd really be nice if this permissions system became one or a set of FEPs for others to pick up.
CC: @PaulaToThePeople
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #ReplyControls -
@Stefan BohacekAnd yes, I hope better reply/interaction controls are coming soon, I know some of that is planned right after quote posts are finished. Really can't wait to see that!
And that, too, will only work within Mastodon.
Also, that, too, won't be a "Mastodon first" feature. At least Hubzilla, (streams) and Forte have reply and interaction controls included in their permissions systems which, in a way, work Fediverse-wide.
Within themselves and each other, they actually make impossible what isn't allowed. For example, if you aren't allowed to repeat (= boost) or share (= quote-post) a post or a comment, you don't even have the button. These permissions aren't understood anywhere outside these three yet, but I've got higher hopes that this permissions system will be cast into FEPs than that Mastodon's hacks will be.
In fact, Hubzilla, (streams) and Forte have reply control on three levels:- channel-wide (who is generally allowed to reply; Hubzilla has eight levels, (streams) and Forte have three)
- for individual connections
- per post (on Hubzilla, commenting on a post can be disallowed altogether; on (streams) and Forte, additionally, commenting can be limited to your full connections, and a time can be defined from which commenting will no longer be allowed)
Again, within these three, if commenting is not allowed, the UI elements for commenting will be missing. Outsiders may be able to comment, but all three block disallowed comments on a server level, i.e. they aren't deleted from the inbox, they are kept from entering the inbox in the first place. And so they don't appear in the thread for all those who support threaded conversations.
It'd really be nice if this permissions system became one or a set of FEPs for others to pick up.
CC: @PaulaToThePeople
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #ReplyControls -
@Stefan BohacekAnd yes, I hope better reply/interaction controls are coming soon, I know some of that is planned right after quote posts are finished. Really can't wait to see that!
And that, too, will only work within Mastodon.
Also, that, too, won't be a "Mastodon first" feature. At least Hubzilla, (streams) and Forte have reply and interaction controls included in their permissions systems which, in a way, work Fediverse-wide.
Within themselves and each other, they actually make impossible what isn't allowed. For example, if you aren't allowed to repeat (= boost) or share (= quote-post) a post or a comment, you don't even have the button. These permissions aren't understood anywhere outside these three yet, but I've got higher hopes that this permissions system will be cast into FEPs than that Mastodon's hacks will be.
In fact, Hubzilla, (streams) and Forte have reply control on three levels:- channel-wide (who is generally allowed to reply; Hubzilla has eight levels, (streams) and Forte have three)
- for individual connections
- per post (on Hubzilla, commenting on a post can be disallowed altogether; on (streams) and Forte, additionally, commenting can be limited to your full connections, and a time can be defined from which commenting will no longer be allowed)
Again, within these three, if commenting is not allowed, the UI elements for commenting will be missing. Outsiders may be able to comment, but all three block disallowed comments on a server level, i.e. they aren't deleted from the inbox, they are kept from entering the inbox in the first place. And so they don't appear in the thread for all those who support threaded conversations.
It'd really be nice if this permissions system became one or a set of FEPs for others to pick up.
CC: @PaulaToThePeople
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #ReplyControls -
@Stefan BohacekAnd yes, I hope better reply/interaction controls are coming soon, I know some of that is planned right after quote posts are finished. Really can't wait to see that!
And that, too, will only work within Mastodon.
Also, that, too, won't be a "Mastodon first" feature. At least Hubzilla, (streams) and Forte have reply and interaction controls included in their permissions systems which, in a way, work Fediverse-wide.
Within themselves and each other, they actually make impossible what isn't allowed. For example, if you aren't allowed to repeat (= boost) or share (= quote-post) a post or a comment, you don't even have the button. These permissions aren't understood anywhere outside these three yet, but I've got higher hopes that this permissions system will be cast into FEPs than that Mastodon's hacks will be.
In fact, Hubzilla, (streams) and Forte have reply control on three levels:- channel-wide (who is generally allowed to reply; Hubzilla has eight levels, (streams) and Forte have three)
- for individual connections
- per post (on Hubzilla, commenting on a post can be disallowed altogether; on (streams) and Forte, additionally, commenting can be limited to your full connections, and a time can be defined from which commenting will no longer be allowed)
Again, within these three, if commenting is not allowed, the UI elements for commenting will be missing. Outsiders may be able to comment, but all three block disallowed comments on a server level, i.e. they aren't deleted from the inbox, they are kept from entering the inbox in the first place. And so they don't appear in the thread for all those who support threaded conversations.
It'd really be nice if this permissions system became one or a set of FEPs for others to pick up.
CC: @PaulaToThePeople
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #ReplyControls -
@Stefan BohacekAnd yes, I hope better reply/interaction controls are coming soon, I know some of that is planned right after quote posts are finished. Really can't wait to see that!
And that, too, will only work within Mastodon.
Also, that, too, won't be a "Mastodon first" feature. At least Hubzilla, (streams) and Forte have reply and interaction controls included in their permissions systems which, in a way, work Fediverse-wide.
Within themselves and each other, they actually make impossible what isn't allowed. For example, if you aren't allowed to repeat (= boost) or share (= quote-post) a post or a comment, you don't even have the button. These permissions aren't understood anywhere outside these three yet, but I've got higher hopes that this permissions system will be cast into FEPs than that Mastodon's hacks will be.
In fact, Hubzilla, (streams) and Forte have reply control on three levels:- channel-wide (who is generally allowed to reply; Hubzilla has eight levels, (streams) and Forte have three)
- for individual connections
- per post (on Hubzilla, commenting on a post can be disallowed altogether; on (streams) and Forte, additionally, commenting can be limited to your full connections, and a time can be defined from which commenting will no longer be allowed)
Again, within these three, if commenting is not allowed, the UI elements for commenting will be missing. Outsiders may be able to comment, but all three block disallowed comments on a server level, i.e. they aren't deleted from the inbox, they are kept from entering the inbox in the first place. And so they don't appear in the thread for all those who support threaded conversations.
It'd really be nice if this permissions system became one or a set of FEPs for others to pick up.
CC: @PaulaToThePeople
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #ReplyControls -
I vaguely remember reading that reply controls on Mastodon are on the to-do list, after quote boosts are finished.
Does anyone recall any official statements on this?
-
I vaguely remember reading that reply controls on Mastodon are on the to-do list, after quote boosts are finished.
Does anyone recall any official statements on this?
-
I vaguely remember reading that reply controls on Mastodon are on the to-do list, after quote boosts are finished.
Does anyone recall any official statements on this?
-
I vaguely remember reading that reply controls on Mastodon are on the to-do list, after quote boosts are finished.
Does anyone recall any official statements on this?
-
I vaguely remember reading that reply controls on Mastodon are on the to-do list, after quote boosts are finished.
Does anyone recall any official statements on this?
-
It is fascinating to read the comments whenever the topic of reply controls (the ability to control who can reply to your post, or to disable replies altogether) comes up.
And the responses seem very gendered. Men demand being able to reply to everyone, all the time. Everyone else just wants to feel safe online. Hmm.
-
It is fascinating to read the comments whenever the topic of reply controls (the ability to control who can reply to your post, or to disable replies altogether) comes up.
And the responses seem very gendered. Men demand being able to reply to everyone, all the time. Everyone else just wants to feel safe online. Hmm.
-
It is fascinating to read the comments whenever the topic of reply controls (the ability to control who can reply to your post, or to disable replies altogether) comes up.
And the responses seem very gendered. Men demand being able to reply to everyone, all the time. Everyone else just wants to feel safe online. Hmm.
-
It is fascinating to read the comments whenever the topic of reply controls (the ability to control who can reply to your post, or to disable replies altogether) comes up.
And the responses seem very gendered. Men demand being able to reply to everyone, all the time. Everyone else just wants to feel safe online. Hmm.
-
It is fascinating to read the comments whenever the topic of reply controls (the ability to control who can reply to your post, or to disable replies altogether) comes up.
And the responses seem very gendered. Men demand being able to reply to everyone, all the time. Everyone else just wants to feel safe online. Hmm.
-
I love that Eugen is currently working (and commited to getting it done) on Reply Controls.
(Things like "Leave this conversation", "Mute this conversation", "Hide this thread", etc.)
Source: the Mastodon roadmap at the official Mastodon blog
https://blog.joinmastodon.org/2021/12/roadmap/ -
I love that Eugen is currently working (and commited to getting it done) on Reply Controls.
(Things like "Leave this conversation", "Mute this conversation", "Hide this thread", etc.)
Source: the Mastodon roadmap at the official Mastodon blog
https://blog.joinmastodon.org/2021/12/roadmap/ -
I love that Eugen is currently working (and commited to getting it done) on Reply Controls.
(Things like "Leave this conversation", "Mute this conversation", "Hide this thread", etc.)
Source: the Mastodon roadmap at the official Mastodon blog
https://blog.joinmastodon.org/2021/12/roadmap/