Conversation
Notices
-
Embed this notice
bloat maxes out at 4 images why
-
Embed this notice
@r @Suiseiseki in my experience if i upload too-large files over bloat then i'll reach a timeout somewhere because it sends all files in one http request, rather than most frontends uploading the attachments as separate requests
-
Embed this notice
@Suiseiseki Do you face any issues while using it over Tor?
-
Embed this notice
@r The only limit to bloat that I've found is whatever I can upload successfully over Tor.
-
Embed this notice
@pernia @sneeden bloat doesn't have any attachment limit and from what I know, Pleroma doesn't limit it either.
-
Embed this notice
@sneeden @r h0w do i change this
-
Embed this notice
@pernia mastodon api restriction maybe?
-
Embed this notice
@r @Suiseiseki or, well, you send all files to bloatfe in one request, i havent looked at bloat's source to figure out how long it holds open the connection to the instance
-
Embed this notice
@opal @Suiseiseki Oh yeah, that could be a reason. Although, bloat doesn't set a timeout for connections. It did use 30s timeout for bloat->upstream server connection, but I removed it after a while because it makes more sense to let the upstream server handle the timeouts.
Also, Go's HTTP and other network libraries have a concept of a "Context" which makes it very easy to pass around timeout and cancellation information to subsequent network calls. In bloat, pressing the browser stop button will also cancel the bloat->upstream server request. So it makes little sense to have timeouts in bloat.
-
Embed this notice
@r @Suiseiseki yeah i meant instance timeout could be reached, i know bloat itself doesnt impose any timeouts