Skip to main content
I'm deleting Pleroma-tan from Soapbox. Sorry. https://gitlab.com/soapbox-pub/soapbox-be/-/merge_requests/155

Delete Pleroma FE (!155) · Merge requests · Soapbox / Soapbox BE · GitLab

The main point of keeping it was to ease merge conflicts, but I don't see them actually updating this very often, and we can just throw out the...
GitLab
neko
neko  
•
kill yourself
​
​  
•
As much as I dislike gleasonware, I'd say bundling a prebuilt FE with Pleroma was a poor decision to begin with. How many instances are currently running with the revision that hangs the tab when there's more than ten mentions in post and has those godawful webfont @'s that can't be turned off?
アメリカ人チー牛
アメリカ人チー牛  
•
This rewrite the backend in something other than Elixir dear god please

Something like C, Go or Rust for extra points
pomstan
pomstan  
•
you can go play with tranny chasers at gotosocial if you want a backend in golang
neko
neko  
•
oh yeah i do 100% agree with you its a bad decision. I think the idea was to ease installation for binary users?? but either way yeah i always force overwrote the files when i modified the frontend lmao with a script

but this is bad for :dinowalk:cels
Alex Gleason
Alex Gleason  
•
Yeah, the plan was always to get rid of static files in the repo and use a postinstall mix task to fetch a frontend. All frontends matter.
neko
neko  
•
Psst…. while this is a bit more work, and I’m essentially the only Frontend dev who uses FastCGI in the year of our lord 2022, it would make my day if you could support executing a script to make a systemd-like startup script, this is the command to execute Treebird as a whole:
spawn-fcgi -a 127.0.0.1 -p 4008 -n treebird

(it’s a lot more clean if you used a socket, as according to the man page for spawn-fcgi, but ports require less permissions)

Shit like this in Soapbox would be incredible, allowing soapbox to simply watch the process and give error codes/stdout intercepting for built in logging

Process — Elixir v1.13.4

hexdocs.pm
Caek Islove 🍰 💖
Caek Islove 🍰 💖  
•
Pleroma FE is ugly. Not sad to see it go.
realcaseyrollins ✝️
realcaseyrollins ✝️  
•
why are you removing it instead of replacing it with something like #Akkoma? It's not a big deal to me but I could see some nerds preferring the #PleromaFE interface
#pleromafe #akkoma
Alex Gleason
Alex Gleason  
•
  • It comes with no frontend preinstalled, not even Soapbox. Admins can choose after installing the backend which frontend to use.
  • People have been asking me about Akkoma, so here’s my official statement on it. Akkoma sucks. It’s developed by a cringe tranny who is even MORE psychotic than Pleroma devs.
e
e  
•
>Akkoma sucks. It’s developed by a cringe tranny who is even MORE psychotic than Pleroma devs
he did something that overrode my config options in /etc/pleroma/config.exs with whatever the defaults were in the git repo config/config.exs which broke some of my shit and when I fixed it without mentioning him specifically or complaining about it he had a meltdown and blocked me. dude is unhinged. pretty sure he neurotically watches searches like pete does because he knew within minutes that I was talking about akkoma
Alex Gleason
Alex Gleason  
•
Yeah, @neko cherry-picked his commits into an upstream MR and he got upset about it: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3680#note_91647

This is open source 101.

Remote PR: Custom Emoji Reactions (!3680) · Merge requests · Pleroma / pleroma · GitLab

This is a patch from IHBAGang/akkoma which contains patches for custom emoji reactions and remote emoji reactions. These are not my...
GitLab
@neko
neko
neko  
•
I dropped this because I got bored and there were better things to be done before adding a big feature.

I wish people would merge in things like security issues / features into mainstream Pleroma, especially those who forked Pleroma, or at least get some communication about it so Pleroma devs are aware. You are indebted to what you forked and you need to remember that.
Alex Gleason
Alex Gleason  
•
I fixed some security issues, here are a few examples:Ironically lanodan accused me of introducing security vulnerabilities into Soapbox BE, but wouldn’t tell me where. So he was fine with receiving my help, but wanted to hold it over my head and blackmail me with it when it was the other way around. Of course the real reason is because no such vulnerability exists.

restricted_nicknames: Add names from MastoAPI endpoints (!2857) · Merge requests · Pleroma / pleroma · GitLab

I thought "hey, know what'd be funny? What if I made my username verify_credentials?" What I really hoped would happen is it would show me my...
GitLab
e
e  
•
>If you created an account called “verify_credentials” people who viewed your profile would see their own profile
LOL
e
e  
•
@realcaseyrollins
@realcaseyrollins ✝️
Alex Gleason
Alex Gleason  
•
You can see how they weren't taking the issue seriously and assuming I must be an idiot.
e
e  
•
I got distracted from coding again
neko
neko  
•
if it makes you feel bad, on rDrama we had a bug where you could literally edit anyone's post by just calling the API directly because the line that checked who was who was commented out. Nobody abused it cuz we get logs
Derek
Derek  
•
Years of drama, 10s of thousands of dollars, endless compromises working with enemies, funded by human traffickers, time and energy from real solutions stolen and wasted and Pleroma, soapbox, gab and mastodon still suck.

GORF Social took no money from anyone, forked no one, worked hard and quietly and built something better than all. GORF Social rocks. https://gorf.social/

GORF Social

Social network dedicated to free speech, privacy and freedom for all.
gorf.social
neko
neko  
•
Show me the source code
VIvi Nella Verita
VIvi Nella Verita  
•
wait. what if you made a retarded/derpy version of Pleroma-tan instead? that be hilarious 😂
Alex Gleason
Alex Gleason  
•
I dunno man, I feel like this already speaks for itself.
⇧