@bobjonkman @bobjonkman One positive is that some #Twitter clients are now advertising #Mastodon clients. I wish they'd also look at making clients for #GNUsocial, #Misskey, #PixelFed and so on, as not everyone supports the Mastodon API.
@evan@prodromou.pub @evan@identi.ca ( and formerly @evan@e14n.com ) has said this a few times, but here it is again.
"Every time you post on Twitter, you produce value for the advertisers.
You tell everyone in your network there that it's OK to stay. That you're all helpless to leave.
You tell the people who've lost their jobs, the people who are being hounded and harassed, that they are not important to you.
You know you're going to be ashamed of it later.
Just stop posting.
Do it here, not there. Connect here, not there.
Don't reply, don't like, don't retweet.
Stop feeding your life into the machine."
This was true before Elon #Musk bought #Twitter, but I guess it wasn't as important before.
I don't fully agree, simply because there may be some advantages to many people who continue to use Twitter instead of moving to the #Fediverse (e.g., #GNU_Social, #Mastodon, #Pleroma, #Misskey, #PixelFed, #Lenny / #Lemmy, etc) or they would have moved over already.
Also, because unless one self-hosts one's own presence, an angry instance admin is all it takes to lose all posts and connections and have to start over. Or, if one has contacts on a different instance, then irate instance admins participating in #blockwars (including #fediblock) can separate the person from some portion of their contacts.
So remember, everything that Twitter is or can do to you, your Fediverse instance can also do. Most instances will never do most of those things, but pretending that one is safe here could result in disappointment in the future.
@administrator @aab I'm just guessing, but it could be related to an exploit someone launched against #Mastodon and #Misskey yesterday. From what I read, it brought several instances to their knees. Misskey released a #security patch yesterday.
Tagging this thread with #Fediverse #Security ... whomever made the script obviously read some protocol docs and some source code. With just a little #JavaScript, they were able to knock some #Misskey and #Mastodon instances to their knees.
This isn't the first, and it won't be the last. Remember when someone posted a humongous image and locked up any #GNUSocial instance that tried to download the image? Remember when someone's instance was replaced by some sort of cryptocurrency site and PuSH es from your site to theirs would crash your site because of their site's response? (I'll bet I still have that domain blocked at the firewall.)
We have to stop being naive about the intentions of those in the current migration. The overwhelming majority will have benign, if not good, intentions. But a select few will have bad intentions. Among those intentions is to colonize the Fediverse with #Twitter's culture, to come here and impose that culture of anger and disrespect upon the inhabitants here ... which already happened once with the first wave of people joining #Mastodon instance, except it was Twitter and #Tumblr at that time.
#Misskey security update. Someone created "instances" which trigger a denial of service in Misskey and possibly #Mastodon. From what I hear, #Pleroma is not vulnerable. #GNUsocial is likely also vulnerable.
We can expect a lot more of these kind of things now that the #Fediverse is getting attention.
Caution: this episode is over three hours long, so I have not listened (and will likely only listen to a fraction of it).
I wish @tio had also brought someone from #GNU_Social and someone from #Pleroma (and maybe @mike@loadaverage.org @mike@z.macgirvin.com to represent #Hubzilla and #Zap (and #Mistpark, #Redmatrix), and @dansup developer and project founder / leader of #PixelFed, and perhaps someone from #PeerTube, #Misskey, and so on). The other thing I wish had been done is to slice this far-too-long episode into four pieces, each an hour or less in length.
Sorry, Michael, I don't know whether you're officially the project leader, so I left that unsaid.
@gdroid@paulfree14 there are instances with 10000 character limits and there are probably ones that have 256 character limits. Are you only supporting commenting with mastodon or is it implemented in a way that #pleroma and #misskey (or other #activitypub implementers) could use too?
If you're on #Pleroma, #Friendica, or #MissKey you may (unsurprisingly) have issues with trying to subscribe to #WeDistribute. This is because the plugin that I rely on, #Pterotype, is currently tested against Mastodon.
I'm trying to suss out the problems by filing bug reports and providing logs, but it could take a while to get things exactly right. That said, future versions of the plugin will rely on a new-and-improved backend that separates the federation logic out into a library. Sorting out federation bugs with Pleroma is a high priority for @jdormit
If you're on #Pleroma, #Friendica, or #MissKey you may (unsurprisingly) have issues with trying to subscribe to #WeDistribute. This is because the plugin that I rely on, #Ptyerotype, is currently tested against Mastodon.
I'm trying to suss out the problems by filing bug reports and providing logs, but it could take a while to get things exactly right. That said, future versions of the plugin will rely on a new-and-improved backend that separates the federation logic out into a library. Sorting out federation bugs with Pleroma is a high priority for @jdormit
just signed up for a #misskey fedi account at @x@💛.tk but mastodon doesn't respect punycode so it doesn't really work too well for its intended purposes. I guess I should see how it works with #pleroma. @x