Weball is a web-based interactive project that allows users to experience a mechanic inspired by the video game Katamari Damacy. In the game, players control a character who rolls a ball that collects objects, growing larger as it gathers more items. Weball translates this concept to the browser, enabling users to navigate websites while 'collecting' various elements like text and images into a rolling sphere.
The project's mechanics evolve as the ball grows. According to the project's description and user observations, the ball initially picks up small text elements. As the ball expands, it gains the ability to grab larger physical images from the site. Interestingly, these larger images do not just become part of the ball; they can also act as physical obstacles on the page. Users have noted that the experience remains relatively smooth on modern hardware, such as high-end mobile devices, even when processing large amounts of content like entire wiki pages.
Despite its smooth performance on some devices, the experience faces technical limitations as the ball accumulates more content. Some users reported significant framerate drops after collecting several hundred words, suggesting a performance ceiling for the current implementation. Technical analysis suggests this may occur because the ball is not a single static 3D object, but rather a collection of elements. Potential optimizations, such as periodically generating the inner layers of the ball as a single asset, could improve performance for larger collections. Additionally, the project's accessibility is currently limited by security protocols, as it primarily functions on HTTP, which may prevent the associated bookmarklet from working on many modern HTTPS-secured websites.
Evidence: - The project's core mechanic of rolling up text and images is established by the primary submission (primary) and discussed by commenters on Hacker News (hn-50140584). - Performance observations regarding framerate drops and hardware behavior are attributed to the Hacker News discussion (hn-50140584). - The technical limitation regarding HTTP-only functionality and the potential for asset optimization are identified in the Hacker News discussion (hn-50140584).