@redegelde https://forum.cloudron.io/topic/8071/change-cloudron-user-management-to-mastodon-app-user-management-on-existed-app/9?_=1669227101540 it can be useful for you

@jdaviescoates https://forum.cloudron.io/topic/8071/change-cloudron-user-management-to-mastodon-app-user-management-on-existed-app/9?_=1669227101540 it can be useful for you

Yeah, at the moment it's a script that calls the mastodon api to add a git-ops derived block list. Hachyderm has one too. It's a neat idea (philosophical questions not withstanding). I think the easiest approach would be to download the code locally and have it run against your Mastodon instance and that would allow folks to choose to use it if they want or not, but not bake it into the default app. But I may have read the instructions wrong!

@nebulon Thanks! I found this too may be it’s related which states to increase the buffer I have no idea where to find this or how to do it ? “ A possible fix for this is to modify the nginx conf to increase the proxy buffer. The following worked for me: proxy_buffers 4 16k; proxy_buffer_size 16k; proxy_busy_buffers_size 32k; “

@jamescridland maybe to take a step back here, what is the reason to run such commands? The media cache is already maintained by the running app ondemand.

I will mark this as solved as many users have succeeded to use s3 for media storage already.

This applies to any open instance (matrix, rocket.chat, etc.), maybe it's best to have this thread pinned in "Discuss"?

@LoudLemur said in Can we join Cloudron.io Mastodon? What's everyone's URLs to follow?: climate change (I am sceptical about this) Sorry, sceptical about what, exactly? The very widely empirically measured over decades heating of the planet?

@shanelord01 You can ignore the recommendation. I think it's a hint for developers to optimize (and maybe sysadmins to report back to upstream project of bug/issues).

@scooke I'll report back! As long as you've copied everything over, then you can remove public/system.

@nebulon thank you

@davidneuner there is nothing "to fix". On a given instance you see the content of users on that instance and the users they are following. To see content from other instances you need to follow other users. a relay (as suggested by @doodlemania2) can help seed some content for you to follow.

Yesterday, we pushed a package which prunes the cache a bit more aggressively - https://git.cloudron.io/cloudron/mastodon-app/-/commit/87e046061335a04c96cd9a133c4bf679caeacb2a . Atleast, in our instance, that brought down the cache size from 12G to almost 2GB.

@girish im going to try it again today to see if itll work

@girish One thing I noticed actually is that theres another 2 backups I cant go back to. All same error. The only one that I can is from 2 days ago. All have the same problem. And I am 100% sure I used it AFTER those

@nichu42 Thanks, seems to have solved the problem!

@doodlemania2 thanks, wil do that.

@girish Perfect :-), Thanks a lot. I used the complete name...:-)

@ericyu00 yeah, it does username login only for LDAP and that also depends on how LDAP is setup. That is this bug report - https://github.com/mastodon/mastodon/issues/11362