Recent searches
Search options
Oh, ffs, Mastodon, why can’t I set these limits from the administration interface on an instance of one?
(It’s a rhetorical question. It’s because Mastodon isn’t optimised for instances of one. Then again, that’s why I’m working to try and birth the Small Web… longest pregnancy ever, mind you.)
PS. I don’t manage my own instance. If I did, I could, of course, configure it. But it shouldn’t require that.
@aral did the failure notification have a stroke?
@aral seems like there should be a single-user mastodon fork. Or a single-user mode to enable.
@travisfw There are lighter-weight ActivityPub clients. I just don’t have the time or wherewithal to migrate. The next thing I’ll be self hosting (in parallel with my Mastodon instance for the foreseeable feature, because they fulfill somewhat overlapping but separate needs and because the Small Web stuff will be rather primitive for a while yet) will be my own Small Web place :)
@aral also i wish it would just convert to lower quality instead of making me do that
@aral Silly question time, what would be the expected behavior of other instances you federate with when the post is pushed out to them? Ignore the post entirely? Strip off the media? Accept the file anyway regardless of their own limits? Don’t mean this question in a snarky way, but it seems like adjustable size restrictions would get sticky on anything that federates.
@dmnelson Not a snarky question at all. And rather cuts to the heart of the problem with ActivityPub… the way I’m thinking of handling it with the Small Web is by making the poster responsible and making notifications links. If you want to post a 1GB video, you go ahead. Everyone will load it from your instance. Seems only fair :)
@dmnelson Then again, you can do that with the Small Web because every place (domain) belongs to a single person. Not so much with a the semi-centralised (federated) model.
@aral That seems reasonable. At least one use case that would need to be accounted for is non-public posts. A long randomized address/identifier/name for the attachment maybe? But you kind of have to rely on security by obscurity since the viewer can’t authenticate to your instance to download it on-demand.
@aral same with character limits. It should be a web interface option.
@aral Quick guess: because it could trip up novice admins when they set an upload limit of 10G and have it still fail because the hosting web server supports only 1G or the temporary upload space is limited to 5G.
@aral I suspect a factor is that you also need to bump the max request body size in nginx and upstream if you're using load balancers etc