While folks are thinking of leaving #Mastodon, just a friendly reminder that #Pleroma let a known TERF (Alex Gleason) join the project and only kicked him out because of conflict over code.
@freakazoid I have a jewish friend and an anti-semitic friend.
I have even bad them both over to my house once, they debated a bunch of neat things. I don't think they are going to go get beers together any time soon, but... I think everyone came out of the experience with a better understanding.
Anyway, you can't cancel a project just cuz one guy is a Terf. You should befriend that guy, then send him a picture of you wearing a dress, and get him to admit that u look good.
Tbh I think the #Threadiverse like #Lemmy and #kbin would make a lot more sense if they were simply frontends and perhaps a backend too but just for the forums themselves. IOW, no accounts live in Lemmy or kbin, all users post from their preferred #fediverse account instead.
Sure you can already technically do that from your #Mastodon or #Misskey or whatever fedi you're in, but that means using whatever app you're on right now, which almost certainly means it's not a #linkaggregator UI. Not ideal at all.
If I had any good programming skills I'd make it so that the link aggregator is merely a client that uses the Mastodon (with #Pleroma extensions too) and Misskey APIs, treat (almost) all #ActivityPub actors as their own forums or subs, and each post would be a boost from said actor. Users authenticate from their preferred fedi account. Voting would be tallied by few special actors, which internally receive votes via direct messages (the app will make this transparent, but this also means you can technically vote without the app if you know the exact command), which will effectively make votes secret to non-admins like in #Reddit. Users can also choose which vote counters they want to rely from.
This would make the fediverse-powered link aggregator very flexible and minimal, imo. It may look janky but that's the general idea I have. :seija_coffee:
I don't use them, but just for fun, I decided to try #tweesecake and #twblue on #pleroma. They both fail differently. First off, both require that you log out or authorization won't work. But if you log out then log in again while authorizing, they will. But at that point, #twblue will just crash. The error in the log says it's trying to do something with Pleroma that it doesn't implement. Tweesecake, on the other hand, pretends to work. It loads the messages and mentions buffers just fine. Then it adds exactly 160 items to the home buffer, all of them blank. If you leave it open, new items will stream into the home buffer. They, also, will be blank. I didn't expect either client to work; I just find the wildly differing failures amusing.
I made the way to delete some cookies from #Vivaldi#browser then cdrom.tokyo came back.
Tried to make a post with a gif image in. Suddenly cracked down and got blank. Had to delete the cookies again. Just sent some text, took some seconds to post.
Why it takes too long time for a post?
Why it fails when I upload an gif?
This is good to hear! I have been itching to move my homeserver from Linux and this current Pleroma fork and this might motivate me to do it one of these days.
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?