I was idly looking over the instance of Pleroma FE that I use when a thought occurred to me. You've done a wonderful job at enabling people to customize the Pleroma environment however they wish. I feel an excellent addition to the 'lists' feature recently added would be to allow people to add custom timelines.

This would effectively allow people to add specific users in bulk to appear on their list and reduce the need to have multiple instances for different interests. Instead, you have the option to create one account and add the timelines of instances that interest you and have a greater degree over your experience.

If there are people that you find annoying, rather than mute them you can simply exclude them from your timeline. I feel this would have the potential to be huge and bring Pleroma to the forefront as a strong alternative to Mastadon. While existing tools such as mute and defederation will help prevent this feature from being used as a vector for harassment.

Should that be a concern for the implementation of this feature then you can apply similar measures as you have with following requests by allowing instances to set whether they will allow people to openly import their timeline or send out a request to the instance administrator to do so. This will significantly a bad actor's ability to abuse the feature while still allowing it to be used in the way it was intended.

Figured I would share it here to see whether anyone else may have any feedback or impute on the implementation of the suggested feature.

#pleroma #pleromadev #fediverse #meta
Stereophonic

Alright!

The good news is I got portable image descriptions working!

The bad news is... I don't like the way it's done at all :/ Basically it first uploads the image while composing the post. But on posting you first download the attachment to change the exif data and then re upload again. So that's three roundtrips!

This also means the time between pressing post and the post actually going through can take a time long enough to give the feeling of something being wrong because it's also down/uploading the image... I'm not really sure yet how to handle this better :(

If someone wants to try already, use these modules. You can place them in `instance/modules/`, restart the server, then add them via admin-fe (or via config files before restarting). Admin-fe > Settings > MRF > there you add `WriteImageDescriptionToExifData` to the policies. Then Admin-fe > Settings > Upload > add `Exiftool.ReadDescription` to Filters. Don't forget to press Submit.

#pleromadev #akkomadev
I saw that pic today of that person who blows on the top of a teapot and fills a cup that way.

Imagine someone trying that for the first time and what a mess that looks like. You now have a good picture of me hacking on admin-fe  

#PleromaDev
Btw, I'm sure people are wondering how things in Pleroma are going.

We currently have about 6 people actively trying to get Pleroma back on track and going and we're talking releases again.

One reason why a release is taking so long is because, while Newroma reverted some of the problematic code, we decided that we couldn't do that for Pleroma. Instead we decided to fix things up. Of course, this takes time, and as you have probably seen, is not always easy for non-technical reasons. But we're doing our best.

If you're interested in how the release is going, here's the milestone https://git.pleroma.social/groups/pleroma/-/milestones/18#tab-issues

The report of it's death was an exaggeration  

#PleromaDev
2.5.0 · Pleroma · GitLab

All Pleroma development

GitLab
One erratic test down
10 left to go  

#pleromaDev
I'm working on https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3652

The idea is to allow to set what mods and admins are allowed to do. E.g. Some instances may want their moderators to be able to delete users, others may not want that. This MR will provide a setting to allow/disallow this via user-tags.

I try to group things in a way that make sense, but since I run my own single user instance, I don't have much experience multiple staff and how things should or shouldn't be grouped together.

So basically I'm looking for feedback (: Pls check out the MR and see if the groupings seem to make sense to you. If you rather have me group things differently, or more fine grained, plz let me know (preferably on the issue tracker so that the discussion remains transparent for everyone). Other feedback is obviously also welcome.

#PleromaDev
Draft: More fine grained access for moderator privileges using tags (!3652) · Merge requests · Pleroma / pleroma

Fix #2852

GitLab

Huh, apparently elixir can do nested maps. I didn't know that one. Since it's immutable, you can't do something like conn.assigns.user.tags = []. But it has a put_in function, such that you can do (among other things) conn = conn.assigns.user.tags |> put_in([])

As the article where I found it says: “It may feel like magic but it's just Elixir doing what it does best: blowing your mind.”

https://dockyard.com/blog/2016/02/01/elixir-best-practices-deeply-nested-maps

#ElixirDev #PleromaDev

This is pretty cool, you can see the reports in the notifications and even resolve them from there! Code needs some touch-ups, but seems to work.

(Code is written by @shpuld btw, thx you shpuld)

#PleromaDev

It seems Pleroma is going in a good direction again, which makes me happy. I decided to take some things upon me again. For people who are interested; This is my current TODO list.

I’ll see what I do after that

#pleromadev

Merge requests · Pleroma / pleroma

Pleroma backend

GitLab