The same thing that drove me nuts about the BridgyFed/BlueSky bridge discourse also drives me nuts with the Threads discourse. :neofox_what: Why isn't there a fediblock level that lets admins default to suspending a server, but allows users to opt back into federating with them? Is there a technical reason for it?
I really don't think it should've been on the BridgyFed developer to build an opt-in system that rightfully should've already been in Mastodon, the same way I don't think blocking Threads outright is the best solution (granted it's better than openly federating, hence why they're suspended here). Why doesn't Mastodon have a built-in system for letting users opt-in to federating with a server? :confused_dog:
Can we just have activitypub:// protocol links the same way we have mailto:// links? :neofox_what: I'm tired of posts opening on their original instance instead of just plunking into my own instance.
There’s an amazing plethora of apps that make using this platform amazing, and I am happy to have paid for quite a few.
I wonder if the next major frontier is interfacing with donations to the supporting the server and mastodons development. I have several friends who thought paying a subscription to an app meant they were also supporting their instance and masto API development… I hope app developers make that a reality someday!
On the Mastodon Public Roadmap this feature isn't even in the "Planned" section: https://joinmastodon.org/roadmap 😐 (MAS-37 Restrict who can reply to a post)
If you too think this very basic safety feature, one of the most thumbsed-up on the Mastodon issue list, should be a higher priority, go to the Github issue and add your 👍 and a comment to bump it into the devs' awareness: https://github.com/mastodon/mastodon/issues/8565
Please include your pronouns in your bio. :otter_peek: It's such a necessity when trying to figure out how to address people.
Plus, if you're using the Mastodon app or one of its forks, you can have a "Pronouns" section and it'll appear next to your username in the home feed. It's very useful. :meowuwu:
Edit: Editing the post to move the tags to a separate line did the trick for me. Let me know if the tags in this post are not displayed below the image for you.
I really, truly feel that #Mastodon needs to at least have an option for getting notifications about things happening to posts that you have boosted!
Feeling a sense of things happening, is really important for engagement – and no, engagement is not the most important thing in the world, but it is important that people want to spend time here and contribute to the community!
Seeing your boosts have ripple effects is fun! It makes you feel that the time you invest here is worth it. #MastoMeta
I think the way mastodon handles hashtags is the most puzzling of the things I find puzzling as a longtime user. I would expect if I click on a hashtag I'd see all the non-locked content visible to me with that hashtag. But it doesn't include "unlisted" posts. I assume this means the hashtag display is generated via federated timelines, so it only pulls in posts are made available for federation (i.e. listed).
can everybody please do me the hardest of solids and #boost this post so that this #firefish#instance gets #federation easier? i'm just testing stuff out on my local server uwu
I knew that #Mastodon is big in #Japan but mstdn.jp activity figures are wild.
Since November it's stable around 400k registered users, most of which go inactive for months at a time. But in the past 4 days, 200k of them returned active. That would account for half of the increase in MAU as measured by @fediverse.
Is this just the effect of word of mouth off-fediverse?
And now, to complete the set, please read my infosec blog. This one doesn't go to Never Gonna Give You Up. You may wish it did.
The fediverse is a privacy nightmare, completely independent of anything Meta might or might not do with it, and nobody seems to really want to engage with that.
Since the previous post went down so swimmingly, here's one explaining why pretty much everything everyone is saying about Meta joining the fediverse is silly and/or nonsensical.
Soon to come - why fedi is a complete privacy nightmare that you absolutely shouldn't use if you want to to retain even the slightest semblance of control over your posts.
I have closed my public instance, finecity.social, binned my account there and moved back to mastodon.social. My bots will keep running on calckey.bloonface.com but I won't use that site for anything else any more.
I have fallen out of love with #Mastodon and #fedi in a big way, I don't intend to use it much any more. The past couple of weeks has crystallised that this isn't really a platform I like much.
The reason I'm suggesting this, is because if you are a small/medium instance with open registrations, and spammers find and abuse your instance, I imagine that other instances will limit/suspend your instance without hesitation, given how willing some were to limit/suspend the much larger mastodon.social.
But do note this comment on the PR:
“To give some context to people seeing this: this is an emergency feature backport from Glitch SOC to help mitigating an ongoing spam wave, this feature may not make it in a next release, or with significative changes.”
Edited to add: multiple people have rightly commented on the accessibility concerns with hCaptcha: hCaptcha is really really really bad for blind and visually impaired people.
Please have a look at this excellent reply for more details:
I feel like it's worth mentioning, re; quote-boosts/QTs, that we can't "just add the feature to Mastodon" in a federation - it's a lot more complicated than a lot of people seem to realise?
The argument about whether or not we should add QTs is an important one, but once we get past that there's the issue of federation.
Mastodon is one software of many using the ActivityPub "skeleton" code. If ActivityPub doesn't have QTs in its code and Mastodon adds a QT feature, any non-Mastodon software (or even server) has to work out how to interpret Mastodon's QTs. If it isn't Mastodon-compatible, QTs will just break. They might even break in a way that harms the person being QTed. And what if someone on another server boosts/reblogs that broken QT?
Also, since we on Mastodon can follow people who are using federated software that isn't Mastodon (e.g. instances/softwares that look and behave like Instagram, YouTube, Facebook, etc), how does that work? Would people on Mastodon be able to QT people on not-Mastodon? How are the OPs going to feel about that? Would they even get notifications about it, since QTs aren't in the ActivityPub "skeleton" of federation?
And since we're a federation of separate servers even "within" Mastodon, there's also the question of how older/outdated Mastodon servers will handle incoming QTs. If you're on an older version of Mastodon and you follow someone on a newer instance and they QT someone, what would that look like? Maybe someone has intentionally chosen a fork of Mastodon with QTs turned off. Can people on other softwares QT them, and how would they feel about that?