Conversation

Notices

1. Embed this notice
   þernia (pernia@cum.salon)'s status on Saturday, 15-Oct-2022 14:57:40 JST þernia
   bloat maxes out at 4 images why
   • Embed this notice
     opal hart (opal@ap.maladaptive.art)'s status on Saturday, 15-Oct-2022 14:57:33 JST opal hart

     in reply to

     • 翠星石
     • r
     @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
     r (r@freesoftwareextremist.com)'s status on Saturday, 15-Oct-2022 14:57:35 JST r

     in reply to

     • 翠星石
     @Suiseiseki Do you face any issues while using it over Tor?
   • Embed this notice
     翠星石 (suiseiseki@freesoftwareextremist.com)'s status on Saturday, 15-Oct-2022 14:57:36 JST 翠星石

     in reply to

     • r
     @r The only limit to bloat that I've found is whatever I can upload successfully over Tor.
   • Embed this notice
     r (r@freesoftwareextremist.com)'s status on Saturday, 15-Oct-2022 14:57:37 JST r

     in reply to

     • Edward Sneeden
     @pernia @sneeden bloat doesn't have any attachment limit and from what I know, Pleroma doesn't limit it either.
   • Embed this notice
     þernia (pernia@cum.salon)'s status on Saturday, 15-Oct-2022 14:57:38 JST þernia

     in reply to

     • Edward Sneeden
     • r
     @sneeden @r h0w do i change this
   • Embed this notice
     Edward Sneeden (sneeden@freecumextremist.com)'s status on Saturday, 15-Oct-2022 14:57:39 JST Edward Sneeden

     in reply to
     @pernia mastodon api restriction maybe?
   • Embed this notice
     opal hart (opal@ap.maladaptive.art)'s status on Saturday, 15-Oct-2022 14:58:18 JST opal hart

     in reply to

     • 翠星石
     • r
     • opal hart
     @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
     r (r@freesoftwareextremist.com)'s status on Saturday, 15-Oct-2022 16:04:02 JST r

     in reply to

     • 翠星石
     • opal hart
     @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.
     opal hart likes this.
   • Embed this notice
     opal hart (opal@ap.maladaptive.art)'s status on Saturday, 15-Oct-2022 16:27:35 JST opal hart

     in reply to

     • 翠星石
     • r
     @r @Suiseiseki yeah i meant instance timeout could be reached, i know bloat itself doesnt impose any timeouts