Fighting for the open web.
#krita #MastoArt #ArtWithOpensource
#Firefox #Privacy #Chrome #WebEnvironmentIntegrity
Well. I've just learned a couple of things about the #Matrix spec and its process that are giving me serious concerns about the long term.
I'm refraining from sharing details here right now, because they would be extremely easy to misinterpret, and it's not an immediate problem to worry about.
However, I do think that it's time to start seriously thinking about forking the protocol, and I've created a room for talking about this: #fork:pixie.town
If you're interested in working on this (as a developer, as a technical writer, as a spec designer, or something else), then please join the room!
However, it's important to recognize that such a spec fork will impact many existing communities and developers, and so breaking compatibility is not to be taken lightly. If possible, it should be avoided.
So if you feel like burning everything down and starting over, this is probably not the project for you. Also, I do expect everybody *not* to harass Matrix core folks over this.
If those things are not an issue for you, then please join!
no one is saying to ignore things that are happening and not talk about it
what Is being said is that people should be able to consent to reading about horrible things instead of being bombarded 24/7
yall need to get back into the habit of using cw and start operating under a culture of consent
deaths should have a cw
opression at the hands of the state should have a cw
covid and climate change should have a cw
triggering people into hypervigilance is not consent culture, nor is it effective or helpful
Think about the vanishingly small number of powerful people who actually can make meaningful change and are positioned to do so
They exist
Now imagine if they had the same level of concern
As all the people who will die screaming in their cars on the highway trying to escape the next small Canadian city that just bursts into flames due to an oil industry externality
Instance admins are often targeted by the instances they block, with the admins of the toxic instances emailing them straw man arguments and sealioning questions meant to have them question their decisions and trick them into thinking they're being unfair.
As I'm often asked for advice with how .art deals with these shitheels, in the next toot I'm going to provide a simple guide that anyone can use the next time the disingenuous admin of Another Toxic Instance emails them.
social media thoughts
i've been thinking about how academics (and academic institutions) have been trained over the course of the past 15 years or so to think about social media uncritically as a means of professional development, to the extent that universities themselves offer "how to advance your career with social media" workshops etc. and how that makes certain habits hard to break for academics, because their careers and networks (and self worth?) have become so enmeshed with (e.g.) twitter
I'm genuinely stuck. The Matrix S2S spec seems effectively unimplementable in its current state, with core functionality being undefined, which leaves me with only a few options:
1. Try to implement it anyway, and be chasing undefined behaviour and broken rooms for the next 5 years
2. Try to get all the holes in the spec resolved, which will probably take a decade at this pace, if it ever succeeds at all (and will burn me out, guaranteed)
3. Fork the protocol into something that's actually strictly specified, but this will fragment the ecosystem because of missing compatibility
4. Just give up on implementing a Matrix server. Take the (extremely rare for me) decision to just abandon this project entirely.
All of these options suck. I see no remaining solutions until the Matrix core/spec developers actually start prioritizing fixing the spec over other things.
Now what the hell do I do?
#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
Less happy post but important, about those who hate furries.
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.
If your plan includes the words "but if everyone would just—"
You don't have a plan
Everyone has never "just—" in the history of time
They won't "just—" this time either
We can't "individual responsibility" our way out of a systemic problem
Plastic recycling* doesn't exist**
Your personal carbon footprint* doesn't exist**
Carbon offsets* don't exist**
Carbon capture* doesn't exist**
Green growth* doesn't exist**
__________
* At the scale necessary to matter in the slightest
** Is and always was an intentional deception perpetrated by industry and those complicit with them to avoid any meaningful change or regulation
Kinda related to my previous post about Matrix but it's unfortunately a much more widespread problem:
When people complain about the documentation quality, don't respond by telling them to fix it! This is a useless response.
Complaining about the docs means they probably don't understand them, and so they also cannot document it.
If you want a serious and successful documentation overhaul, you *as a developer* need to be involved in the process.
At the very least, you need to make yourself consistently available with quick response times to whoever is doing the documentation work.
You are likely the only one(s) who actually understand the undocumented details, and so it needs to be possible for people doing documentation work to retrieve that information from you as-needed.
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)
In the process of moving to @joepie91. This account will stay active for the foreseeable future! But please also follow the other one.
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
- No alt text (request) = no boost.
- Boosts OK for all boostable posts.
- DMs are open.
- Flirting welcome, but be explicit if you want something out of it!
- The devil doesn't need an advocate; no combative arguing in my mentions.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.