@realcaseyrollins@mstdn.social
and I checked in and added a follow to Puniko - hers seems to be a nice Pleroma instance, with SO MUCH more than the vanilla masto with 500 chars Toots allowed (and unbending admins when you request some more)
Will visit and check out Facilities -- the front page has some hints of a good place to be!
* 60, 000 (60 Thousand!!) characters limit, take that, Eugen.
* choice of the Pleroma UI/Front End -or- the more mastodon user friendly Mastodon FE (which is the Elite Glitch-Social variety -- so lots of new and improved features compared to masto.social variety)
* As in ALL Pleroma instances, rich formatted text is a Human Right -- and I absolutely love the posts I have been creatign with #MarkDown at Glitch-social instances I have recently joined.
Another pinprick to Eugen, lol... Don't gimme what I want, I am out, friend.
Kudos, thank you and appreciation to Puniko!
oh, my instance supports a bit more than pleroma itself does. like \(\LaTeX\) for example
or this! (look at this post on my instance)
reed_-_fairlight_in_action.xm
🇳🇱
Same for QOTO, we support several things that pleorma doesnt, and ultimately why for the moment I am not moving us.
Namely we too support latex. We also support pseudocode format, and remote timelines as well as subscriptions and several other features absent on pleorma.
The remote timelines is the big deal breaker for me right now.
@alex @emuz @realcaseyrollins@mstdn.social @stux @design_RG
Get the goodies from Glitch-Social and you could really offer me something I am yearning for.
Qoto remains my main account, but I so enjoy crafting a neat #MarkDown love post.
OMG. No comparison.
A real, real plus for me at Qoto -- major kudos as I use it ALL the time --Is the FULL TEXT search enabled. 2 years of posts and I CAN find things, if I use the right word.
Mastodon vanilla feature, but Disabled in most instances as it takes rAM and processing power to offer. Should be standard, but it's not, I miss it even in Elite instances like Hackers.Town which have outstanding performace.
@absturztaube @alex @emuz @realcaseyrollins@mstdn.social @stux
If you add markdown support **and** remote time lines that might be enought to see QOTO convert.
@absturztaube @emuz @realcaseyrollins@mstdn.social @stux @design_RG
I'll add Markdown support, but there will also be a lot of other things Mastodon won't have, like ChatMessages (my mockup attached), and soon Groups. Pleroma is really where the innovation is happening. Not to mention it's a more solid foundation and way more efficient.
Yes QOTO is not plain mastodon, I have customized it with several additional features. One of them is the ability to view a remote timeline.
Basically on QOTO you can setup a column that is either devoted to looking like the local timeline of a remote instance, or combines several remote timelines into one column.
In this way you dont need multiple accounts on multiple instances. My account on qoto lets me follow the timelines of any instances I would otherwise want an account on and get to see their local feed as a column in my own QOTO local client.
@absturztaube @emuz @realcaseyrollins@mstdn.social @stux @design_RG
Since you've already developed this stuff you could help add it to Pleroma. Unlike Mastodon they will actually merge your features as long as they're stable and have automated tests.
Learning Elixir is a bit of a hurdle at first, but I believe it's a better technical choice for the Fediverse. We'll be thankful for it in the long term.
Groups would be great. But I feel groups solves a very different issue in some ways. Groups are topic based, whereas the remote timeline feature is instance based and not necceseraly keyed to any specific topic.
Ideally I'd like to see both.
The other side is mastodon is for the moment the bulk of instances and they wont even support groups. So even if there is a group feature that pleorma supports it really wont help us with how 95% of the rest of the fediverse does things.
@absturztaube @emuz @realcaseyrollins@mstdn.social @stux @design_RG @fluffy
That very well could be the case. I would love to see a feature rich solution take over the scene that is less opinionated than mastodon (give the power to the admins).
But things dont always go as planned so for now I have to look at the current dynamics, at least until your able to tip the scales.
@absturztaube @emuz @realcaseyrollins@mstdn.social @stux @design_RG @fluffy
@freemo
> That very well could be the case. I would love to see a feature rich solution take over the scene that is less opinionated than mastodon
> (give the power to the admins).
The mastodon project leadership doesn't even accept or listen well to reasoned and production ready code provided -- case in point, the refusal to consider MarkDown inclusion. Code Pull request in masto Git home. Refused and closed by E.R.
As a User, that pisses me, the people in the Git discussion (long) were half pro, half against.
I think it will be Excellent for the Fediverse to see alternatives growing up - and stealing users from vanilla, rigid and unresponsive admins. [ I have campaigned for a simple increase of Max Toot Length, and was refused. Repeatedly. Annoying is to say the least ]
I have already moved some of my work to Glitch-Social instances, and am enjoying them - it seems oddly limiting now to use Plain Text here.
@alex @absturztaube @emuz @realcaseyrollins@mstdn.social @stux @fluffy
The pattern goes back a long way. I thinkwhat gave rise to glitch was the fact that someone provided a excellent PR that basically added the ability to configure toot size in the configuration file. It was rejected, and glitch was born.
@alex @absturztaube @emuz @realcaseyrollins@mstdn.social @stux @fluffy
@freemo
> the fact that someone provided a excellent PR that basically added the ability to configure toot size in the configuration file. It was rejected, and glitch was born.
Yes, that is a True Fact -- I have screenshots of the topic, even. [saved and planned to use in a critical article as you can imagine]
Only correction to add -- the PR in case (editor note : code ready for implementation, not a vague suggestion), the proposer of that was LambadaLambda.
...Who is Pleroma's Lead Developer. 😔
Eugen's style has turned many collaborators away over the years. I have notes and bookmarks of Medium posts by someone like me -- who couldnt write Code, but could fill a much needed position.
As in -- writing all kinds of user fronting documentation. She left, after repeated put downs and no acknowledgement of her contributions. Never got a mention in the Credits.
Really well written and explains a lot. It opened my mind, and I plan to refer to it as I explain my own decisions and personal campaign for Better Alternatives.
@alex @absturztaube @emuz @realcaseyrollins@mstdn.social @stux @fluffy
Yeah, I seen a similar PR with local only post, he refused to add it in the mastodon just because he thinks it's not right to have that feature.
And As about the increasing size of media as some instance want, he should have learn something from pleroma using nginx to cache external media rather than storing it with instanace media
Its really take a lot time if you don't remove external cache media on regular basis.
I'm not being mean but curious, why people don't use mute conversations option? 🤔 It's there for a reason I guess
> why people don't use mute conversations option?
it mutes the entire tree, some of which you may want to leave unmuted, and removes it from your view, which may not be desirable.
Ah, thank you -- I jsut posted the About link since I was really curious what software you had.
Here on mastodon, the Mute Conversation is worthless to me, in my experience so far. To the point of me avoiding a comment on a topic simply to avoid flooding my Notifications.
we're on soapbox dev frontend and bloat frontend with pleroma stable backend. we provide our users a free twitch-like streaming service, using various software.
I haven't filled in the about page mostly because I have many things to do. I will probably block out a few hours to fill it in once we hit one hundred users.