Discussion
Loading...

Discussion

Log in
  • About
  • Code of conduct
  • Privacy
  • About Bonfire
Doug Belshaw
Doug Belshaw
@dajbelshaw  ·  activity timestamp 4 years ago

Temporary solution to some of the slowdown issues is to use uBlock Origin to block the domain 'robohash.org' (used to generate the default avatars)


You can do this by:


  1. Right-clicking on any robot avatar
  2. Choosing 'Block element'
  3. Deleting everything after 'robohash.org'
  4. Pressing the 'Create button'
  5. Refreshing the page


Hopefully @BonfireBuilders will swap out the default avatars soon!

Screenshot of blocking robohash.org
Screenshot of blocking robohash.org
Screenshot of blocking robohash.org
  • Copy link
  • Flag this post
  • Block
Mayel
Mayel
@mayel responded  ·  activity timestamp 4 years ago
@dajbelshaw @BonfireBuilders @vera anyway, one lesson here is don't rely on any external services (which we've tried to do but obviously missed some! for instance you can choose among - at the moment three - different fonts in settings, and those are loaded from the instance rather than a CDN)
  • Copy link
  • Flag this comment
  • Block
vera
vera
@vera responded  ·  activity timestamp 4 years ago
@dajbelshaw @BonfireBuilders Thanks!
  • Copy link
  • Flag this comment
  • Block
Mayel
Mayel
@mayel responded  ·  activity timestamp 4 years ago
@BonfireBuilders @vera it's a mystery as to why, but removing robohash seems to have greatly sped the loading of feeds! 🎉 🎉 great find @dajbelshaw 🙇 👏
  • Copy link
  • Flag this comment
  • Block
Doug Belshaw
Doug Belshaw
@dajbelshaw responded  ·  activity timestamp 4 years ago

It's nice to not just be for rhetorical effect for once! Thanks for the speedy fix 😀

  • Copy link
  • Flag this comment
  • Block
vera
vera
@vera responded  ·  activity timestamp 4 years ago

is it doing it on demand? it might be waiting for data before it continues processing?

  • Copy link
  • Flag this comment
  • Block
Mayel
Mayel
@mayel responded  ·  activity timestamp 4 years ago

the code generating those URIs wasn't making any requests, but it's possible that it was happening somewhere else in the backend, since we we have code that compresses images for "lazy loading", though that usually applies only for locally-uploaded ones

  • Copy link
  • Flag this comment
  • Block

Bonfire social

This is a bonfire demo instance for testing purposes

playground.bonfire.cafe: About · Code of conduct · Privacy ·
Bonfire social · 1.0.1-beta.22 no JS en
Manual federation enabled
Log in
  • Explore
  • About
  • Code of Conduct