@stgiga@youronlyone@youronlyone & talking about #Fedi history by the way, since the doc itself says it is a living doc, there are a few notable instances not yet mentioned there that were recently developed by high-profile (or at least notable enough for us) Fedi users & might have verifiable links or posts that can give them a place within the doc’s timeline:
• #Fedibird (#Mastodon fork) by @noellabo
• #Sharkey (a very popular #Misskey fork) by @Amelia (& others from the @Sharkey project) since 2023
• maybe #IceShrimp (#Firefish fork?), unsure if it’s notable enough for inclusion or if supported by verifiable links (even I don’t know who created it).
I leave it up to @youronlyone whether certain popular extensions (if not forks per se) like #GlitchSoc (extending Mastodon) & #Soapbox (extending or modifying #Pleroma) can be added to the timeline as well.
Also, I will definitely not suggest for inclusion (or even a footnote mention) a certain #Akkoma fork that was given an obscene name by a fringe group of people (let’s just pretend it never existed, OK?) :ablobcatknitsweats:
As a side-comment, I was also thinking of the not-Mastodon platforms which build on the same #ActivityPub network. Does #Pleroma participate in the preview cascade? Misskey and its forks? Nextcloud Social, microblog.pub, Akkoma, or Kitsune? What about the Mastodon forks Hometown and Glitch-soc?
It is getting to be more a constellation than a classification… So many new ones I have never checked out!
Tbh I'm not enthusiastic about a #Mastodon#hardfork. Not necessarily because of the #techdebt or even because it's technically inferior to other #ActivityPub implementations (which are both true), but because I cannot be sure if that new fork is going to adopt the same attitude as Mastodon in choking the rest of the #fediverse with its proprietary extensions and #EmbraceExtendExtinguish / #EEE.
I'd rather not have the uncertainty. Either start from scratch like #GoToSocial is doing or help the other two mainstream AP families which are #Misskey and #Pleroma. That's the only way we can ensure no implementation overwhelmingly dominates the fedi. :seija_coffee:
If your profile and posts are set to "public" and you can read this very post, you should have no sense of "privacy" here on Fedi. That means ANYONE can reply.
There's 20,000+ instances and new ones every day, there's NO WAY to tell who is accessing your posts or what they're doing with them.
Fediverse is not some kinda "bastion for privacy" nor is there any sort of "consent" required to see your posts if they are public.
The only way you can be 100% sure that your followers are the only ones that directly see your posts is to make your profile and posts private. Even then, screenshots exist.
Remember, you're on the internet. Once you post it, it's probably not going away. This is true everywhere.
I think the fedi needs to be more about clients/apps than it is currently.
Agreed, and I kinda touched on this earlier about how the #Threadiverse should've simply been a frontend where people just use their main fedi account instead of having to create another account for forums in a link aggregator... :sagume_think:
Tbh all the #fediverse implementations in the first place should've been backends first and foremost. Why should I not be able to have #Misskey's frontend in #Mastodon or #Pleroma? And the other way around too. This does mean that we will have to all agree on a common client API and MastoAPI will dominate, but I'd rather have Mastodon dictate client API than fediverse implementations. :seija_coffee:
I said it elsewhere, but I say it here too, I HATE how corporate social media sites have taken SOCIAL out of social media.
Thankfully the Fediverse is mostly taking that back. But if we don't expand to get those that are still on corporate social media to move here, then we'll just become the echo chambers we hate. That's why the Threads integration is a good thing. We need to expand.
A popular multiservice scrobbler for Android, “Pano Scrobbler”, added scrobble support for #Pleroma and forks.
I haven't seen how it looks, and unfortunately I can't test it myself. It's hard to find a good Pleroma instance with an open registration, and my original Pleroma instance closed and I only found out a few days ago.
(I did found a good instance, but I haven't received the verification email yet, for a few days now. Unless there's an issue, or I typed my email wrong? Hahaha.)
Anyway, anyone tried it? Not Pano directly, but scrobbling to a Pleroma instance. How does it look? Is it posting one message per scrobble? Or, it shows on your profile only? Or, does it add a scrobble footer automatically when you create a new post?
#Threads user with dotted username (an impossibility in vanilla #Mastodon) spotted in the wild federating with a #Misskey instance (namely, Voskey)! So, does this mean Misskey can handle dotted usernames & thus can further do what #Mastodont?
❓ Hier hat jemand mal den Link zu einer richtig guten Tabelle gepostet, in der Funktionen verschiedener #Fediverse Dienste wie #Mastodon, #Friendica, #Misskey, #Pleroma usw. sehr detailliert verglichen wurden. Es kann sein, dass die Tabelle sogar editierbar war. Vielleicht Cryptpad?
Leider finde ich den Link nicht mehr.
Habt ihr eine Idee, wo es sowas im Netz gibt?
Ich suche eine Alternative zu Friendica, das ich mag, bei dem die Posts aber für manche wohl zu schlecht lesbar sind. #askfedi
Actually I can't really bash #Lemmy for this (as much as I'd want to) because it seems like pretty much the rest of the #fediverse has this problem of images not getting immediately removed from the server when you delete the image or even your account. I've tested with #Mastodon, #Pleroma, and #Misskey (even Misskey somehow gets it wrong by not immediately making your image unavailable by the URL even if you've deleted it from your Drive, however this doesn't always happen, see below).
Now I'm not sure about instance admin stuff (and I haven't tested with my admin hat on in this Misskey), but I'm guessing you don't have a view of all uploaded photos by a user that an admin can delete from in Mastodon and Pleroma either (please prove me wrong though!). :sagume_think: Misskey does let you view all files uploaded by a user and delete from there, though I'm not sure if the file gets immediately removed from the server once you hit delete, but it's probably gonna be like what I'm going to write below
What I do know about Misskey is that, if you've never accessed the URL generated for the file in your Drive, and hit delete, the next time you access it, it definitely will no longer be available; a pure 404 as expected. However if you've accessed the URL at least once, then the file will get cached. I'm not sure if it's Misskey doing this or the reverse proxy (like #nginx), because clearing cache or switching to a whole 'nother browser still shows the file is available.
Oh, and have I mentioned that all three software will automatically put your image into the server the moment you hit the upload button, even if you haven't submitted the post yet? Yeah it's equally as easy as Lemmy to accidentally upload something to those three as well.
Hello again #Fediverse, I may need your #fedihelp. So, here's a list of the Fediverse software I'm about to make temporary accounts for to test all the features and differences:
So, did I miss anything noteworthy? Does anyone have any tips or recommendations before I choose a server for any one of these? I'll probably be going for the most popular server on each for improved federation and maintenance.
Note: I'm using #Sharkey right now and Misskey forks are already overrepresented, so that's why it's not included.
Google provides a tool called PageSpeed Insights which gives a website some metrics to assess how well it is put together and how fast it loads. There are a lot of technical details but in general green scores are good, orange not great and red is bad.
I tried to ensure the tests were similar for each platform by choosing a page that shows a list of posts, like https://mastodon.social/explore.
The rest don’t seem to have prioritized performance or chose a software architecture that cannot be made to perform well on these metrics. It will be very interesting to see how that affects the cost of running large instances and the longevity of the platforms. Time will tell.
It doesn't matter if you are new to the #fediverse or if you have been here forever, it's always good to keep in mind that (a) what server you pick, and (b) what software that server runs, matter.
I should admit am fairly new at this. I created my first fediverse account only a year ago. It was a #mastodon server with about 8,000 users. And while it "worked" there was something missing from the experience.
While researching the idea of hosting my own server, I discovered #FireFish which in turn led to discovering #IceShrimp. It's hard to describe how much better the experience is with IceShrimp.
The #UI is just so much better, and the feature set way more robust. The way it handles replies, the ability to quote, to use multiple emojis, etc.
If you have friends or family thinking about joining the Fediverse or are feeling unimpressed with your mastodon experience, I highly recommend getting an account running IceShrimp or other similar software.
Probably also worth mentioning that I also looked at using a #Wordpress integration and #Hubzilla#GoToSocial#Pleroma#Humhub and #Streams. I found them to be clunky; reminding me of how email was in the early 90s.
If the fediverse is going to thrive, then it needs to make a good first impression. Moving beyond mastodon is a good step in the right direction.
The #fediverse (this includes #Misskey, #Pleroma, #Peertube and yes, even #Mastodon) desperately needs a feature where either a poster can disable #comments for their post, or a feature that says you can only comment on the first post in a thread and not allow people to jump-in in the middle.
I know it's impossible to do, and that it would effectively break social networking in general but holy fucking shit!
I'm in a #thread with the amazing @lauren and the behavior of someone just chiming in and #mansplaining something they clearly don't have all the facts about is incredible.
I can only imagine the volume of this happening to every woman on the Fediverse, and dare I say I've probably been guilty of the same behavior myself.
So yeah, I think there definitely needs to be a change to the #ActivityPub specification where a poster can say, "No comments are allowed for this post".
Still doesn't stop somebody from quoting the post and adding their comments, and honestly I think that's fine.