pleroma-support activityhttps://git.pleroma.social/pleroma/pleroma-support2020-06-01T20:48:12Ztag:git.pleroma.social,2020-06-01:72379rinpatch closed issue #33: How do I know if the icon change was successfully ...2020-06-01T20:48:12Zrinpatchrinpatchrinpatch@sdf.org

I change the icons about once every two weeks or so. However, many Mastodon server administrators have told me that the icons have not been changed on their servers. Apparently my server doesn't seem to be able to propagate the icons well. Currently, the account is being refreshed on a remote server.

How do I know if the icon change was successfully propagated? I'm completely unfamiliar with Elixir products and have no knowledge of debugging, can you tell me if I'm propagating the icons correctly while running the production environment?

I think there are some Pleroma servers that do a good job of propagating their icons. I'm reluctant to declare it a bug, so I've declared it in this repository.

tag:git.pleroma.social,2020-06-01:72280kunimi komichi opened issue #33: How do I know if the icon change was success...2020-06-01T03:55:48Zkunimi53chikunimi komichi

I change the icons about once every two weeks or so. However, many Mastodon server administrators have told me that the icons have not been changed on their servers. Apparently my server doesn't seem to be able to propagate the icons well. Currently, the account is being refreshed on a remote server.

How do I know if the icon change was successfully propagated? I'm completely unfamiliar with Elixir products and have no knowledge of debugging, can you tell me if I'm propagating the icons correctly while running the production environment?

I think there are some Pleroma servers that do a good job of propagating their icons. I'm reluctant to declare it a bug, so I've declared it in this repository.

Anything related to IPv6 being broken with mix deps.get in Elixir should be directed upstream. It's a bug in Elixir then.

tag:git.pleroma.social,2020-04-14:65828Haelwenn closed issue #32: How to serve local emojis through a CDN? at Plerom...2020-04-14T07:48:47ZlanodanHaelwenn

I serve my local media through a CDN by storing it on s3 (Minio, then proxy it via a caching CDN). However, it seems like there is no way to do this with custom emojis. This would be very useful as tools that download thousands of custom emojis can produce a significant load on the server, and delegating it to a CDN would be much more efficient.

I don't think there is any way right now to do it, probably because historically emoji used to be basically fine as static assets rather than something which should be more close to uploads now.

tag:git.pleroma.social,2020-04-13:65814Mew Mew opened issue #32: How to serve local emojis through a CDN? at Pleroma...2020-04-13T22:52:55ZmewmewMew Mew

I serve my local media through a CDN by storing it on s3 (Minio, then proxy it via a caching CDN). However, it seems like there is no way to do this with custom emojis. This would be very useful as tools that download thousands of custom emojis can produce a significant load on the server, and delegating it to a CDN would be much more efficient.

I'm a fairly new instance admin(Came from mastodon imported followings) and i have some questions i've been unable to find answers to. Mostly around moderation. I am using Pleroma.Web.ActivityPub.MRF.SimplePolicy

If i add an instance to reject or federated_timeline_removal how do i deal with things that are already received.

How do i block a single user instance wide

Next when i first started up the instance i had this set

config :pleroma, :fetch_initial_posts, enabled: true, pages: 1

because i wanted some content right away and figured this was needed to do so. I quickly watched the DB grow to over 200mb. Not knowing how much more it would pull in i turned off this setting. How would i prune/purge what it pulled in? Or should i even worry?

Next would be around relays to get greater federation going. I have tried adding a relay using

Hi. Apologies if this was already addressed and I failed to find the proper answer while looking through past issues.

I've noticed that when I create a new user, no email is forthcoming.
I am also aware of the bug where creating a new user while logged in causes the operation to fail, found in a different ticket, and I make sure to work around this one: the accounts do get created.

I also noticed that if I try to recover my password, I will not receive any email either.

I tried replacing Swoosh.Adapters.SMTP with Swossh.Adapters.Logger, :debug level but did not see anything in the log output.

This looks like a plugin set into nginx for managing the certificates, the documentation is using the standalone mode with a cron entry.

Sort of, its a certbot plugin created by the LetsEncrypt team to have a standard for creation of SSL certificates. The current revidion of the letsencrypt ACMEv2 tool has fixed the issues that the earlier versions had where it would fail to auto-renew, and the nginx plugin is "smart enough" now to correct/add what needs correction in the nginx config files.

Regardless the certbot command would still need to be modified to prompt the end user to accept ToS, so best practice would be to let the official letsencrypt acme client handle the update request, rather than a local crontab entry IMHO.