Sven Slootweg (soft-deprecated) @joepie91@pixie.town

#Abolition #BlackMastodon #BlackTwitter @blackmastodon
The question is: what is the function of the police? Can we create a system where safety functions are carried out without the police? Advocates and communities are thinking through what that would look like. In the meantime, those of you who want to spend energies on reform, pick something that will increase transparency and accountability. If you understand the down sides of some harm reduction but want to work with that do so. 11/12

Remember, friends... #furry hate is just a coverup for #lgbtqia hate. If you meet anyone who fits those statements, run the other way and do not interact. It won't help you, it will only make you a target. People like that are best ignored. Take away their audience/platform/"debates" and they're nothing.

kim here, just with an addition to help frame some of the discussion that's being had over this:

anything we make for GoToSocial whether disabled by default or not, will end up getting used by people.

and given that GoToSocial has a fairly sizeable user base at this point, decisions like these will end up swaying (even if just a little) what becomes "expected" or "new normals" among those implementing social media.

which is to say that even if it feels like a lot of privacy / safety discussion over small features, i think it's necessary given the state of everything right now (gestures at capitalism) and the unknowns it may lead to.

Hi everyone!

We're currently doing working on our hashtag implementation. We've got hashtags federating in and out nicely, and we've got hashtag timelines viewable via the API, which is cool!

However, we're now wondering about web endpoints for hashtag timelines.

Mastodon already exposes people's posts (regardless of instance of origin) on their public web endpoints, unless authorized fetch is turned on. For example: https://mastodon.social/tags/GoToSocial

However, we're doubtful about going down that same route, because it potentially exposes peoples posts more easily to scrapers and the general public, which conflicts with our goals of providing a more privacy-focused alternative.

In the developer chat, we're discussing possibly using the 'discoverable' flag on accounts to determine whether or not their public-visibility hashtagged posts are exposed via the web endpoint, so that's one option.

Another option would be to only show hashtagged posts from local accounts that have 'discoverable' set to true.

Yet another option would be to skip displaying web view of hashtag timelines altogether, and only have them visible via the API (so, for a logged-in user).

Finally, if we end up implementing any form of this web view for hashtagged posts, we will definitely allow it to be turned off by the instance admin (and 'off' will probably be the default).

What do you think? Constructive opinions please! Thank you! <3

Self care™️ is cute and all but have we considered investing in community care????

Community care asks us:

Do we earnestly check in on folks?

Do we have the language to ask for help?

Is our intuition such that we understand when someone needs care?

Do we know our capacities?

Are we building relationships founded on reciprocity?

Have we created a community wherein holding space for one another is normalized?

If we understand that individualism, as popularly understood, is a capitalist ideal, and by proxy often an ableist one: has our conception of care shifted from the personal to the communal?

- Queer X Chisme (Facebook)

#SelfCare #CommunityCare #anarchism

If anyone thinks it's impossible to pick up any traction on the Fediverse, it's worth noting that I usually get hundreds of notifications a /day/.

I'm not trying to brag, my point is that it happens because I'm not afraid to reach out and actually try interacting with people. You can't just come and expect people to come to you, you have to actually be willing to engage.

Fedi is an interactive experience and it works better when you treat it as such, instead of just a window into someone else's thoughts.

During this other backlash which also has very
serious and important implications both for the web specifically and general-purpose computing at large, don't forget that the Google employees who are spearheading this assault on our freedom have names and addresses.

@aral As predicted:
https://github.com/RupertBenWiser/Web-Environment-Integrity/issues/28

✔️ Within 3 days at most, there'll be a statement expressing their surprise how this proposal was received

✔️ They will regret that they were not able to "express" their "intentions" more "clearly", to avoid "misunderstandings"

✔️ That specific repo will be locked. Comments on that statement won't be permitted

ToDo: Within 3-6 months, this attempt will resurface, probably under a different name, and certainly on a different platform

#Google #Lies

Torment Nexus is committed to innovation and bringing new experiences.

Unlike some of the tech giants out there, we opt to omit such redundant things as soliciting public feedback or publishing standards when it comes to our innovations. They could learn from us.

I have a new hashtag proposal: #AskMeAbout

To participate in the hashtag, simply make a post listing 3-5 topics that you know a lot about and would feel comfortable discussing with other folks. Be sure to include the #AskMeAbout hashtag in your post!

Then, folks browsing the hashtag can hop on your post with their questions!

Just remembered my all-time favourite bug, where Android accidentally rendered the name of the "Grunt" tool on its webpage as "Dorkq" https://github.com/gruntjs/gruntjs.com/issues/81