* Prezi\nPrezi pioneered the zooming canvas for presentations and remains the market leader in that space. It recently added AI-powered generation and text editing tools. It's a polished product with real traction.
But Prezi is a closed platform, not a library. You can't use its zoom engine in your own app. Pricing starts at $15/month for meaningful features, and exporting to PowerPoint flattens all zoom effects into static slides. A recurring complaint from users is that the zooming and panning transitions cause motion sickness. And fundamentally, Prezi uses zoom as a storytelling device between pre-arranged frames. It's not a navigation model. It's a presentation model.
* impress.js\nimpress.js brought Prezi-like zooming to the open web. It's a presentation framework based on CSS3 transforms and transitions, directly inspired by Prezi. It was genuinely groundbreaking when it launched.\nIts architecture is step-based: you position "steps" in 3D space and the camera moves between them. That's great for presentations, but it doesn't help you build an app where users navigate by zooming into content. impress.js has no concept of dynamically mounting views, managing zoom depth, or handling navigation state. It's a slide deck engine with a zoom trick.
* Zumly\nThis is what I built. Full disclosure: I'm the sole developer.\nThe idea is offering an alternative to traditional page navigation using zooming. You mark an element as zoomable, point it to a view, and Zumly handles the transition and inserts new views. That's basically it.
I started Zumly in 2020 after leaving behind Zircle UI (a Vue zooming library), trying to take what I learned further. Framework-agnostic, focused just on the zoom part. Since then I've rewritten the engine several times, changed the approach more than once. Only now I'm actually happy with how it feels.
Views are dynamically mounted and unmounted during zoom transitions. In impress.js, all steps exist in the DOM simultaneously. In Zumly, you zoom into a trigger element, and the target view gets injected and scaled into place. This is closer to how routing works in SPAs than to how slide decks work.
The landing page is built with Zumly itself so you can get the feel before touching any code.
Curious if anyone else has thought about this space. What makes zooming UIs work or fail?
Landing page (built with Zumly): https://zumerlab.github.io/zumly
GitHub: https://github.com/zumerlab/zumly"},"title":{"matchLevel":"none","matchedWords":[],"value":"Zooming UIs in 2026: Prezi, impress.js, and why I built something different"}},"_tags":["story","author_tinchox6","story_47665194","ask_hn"],"author":"tinchox6","children":[47665786,47665845,47665972,47666012,47666069,47666141,47666237,47666296,47666476,47666494,47666636,47666669,47667175,47667264,47667368,47667763,47667931,47668353,47668983,47669094,47669128,47669268,47670158,47672750,47693300,47727620,47766833],"created_at":"2026-04-06T18:53:15Z","created_at_i":1775501595,"num_comments":44,"objectID":"47665194","points":101,"story_id":47665194,"story_text":"There are essentially two established ways to use zooming in web interfaces today. They serve different purposes and make different tradeoffs. I built a third one, so I'll try to be fair about what each does well and where it falls short.
* Prezi\nPrezi pioneered the zooming canvas for presentations and remains the market leader in that space. It recently added AI-powered generation and text editing tools. It's a polished product with real traction.
But Prezi is a closed platform, not a library. You can't use its zoom engine in your own app. Pricing starts at $15/month for meaningful features, and exporting to PowerPoint flattens all zoom effects into static slides. A recurring complaint from users is that the zooming and panning transitions cause motion sickness. And fundamentally, Prezi uses zoom as a storytelling device between pre-arranged frames. It's not a navigation model. It's a presentation model.
* impress.js\nimpress.js brought Prezi-like zooming to the open web. It's a presentation framework based on CSS3 transforms and transitions, directly inspired by Prezi. It was genuinely groundbreaking when it launched.\nIts architecture is step-based: you position "steps" in 3D space and the camera moves between them. That's great for presentations, but it doesn't help you build an app where users navigate by zooming into content. impress.js has no concept of dynamically mounting views, managing zoom depth, or handling navigation state. It's a slide deck engine with a zoom trick.
* Zumly\nThis is what I built. Full disclosure: I'm the sole developer.\nThe idea is offering an alternative to traditional page navigation using zooming. You mark an element as zoomable, point it to a view, and Zumly handles the transition and inserts new views. That's basically it.
I started Zumly in 2020 after leaving behind Zircle UI (a Vue zooming library), trying to take what I learned further. Framework-agnostic, focused just on the zoom part. Since then I've rewritten the engine several times, changed the approach more than once. Only now I'm actually happy with how it feels.
Views are dynamically mounted and unmounted during zoom transitions. In impress.js, all steps exist in the DOM simultaneously. In Zumly, you zoom into a trigger element, and the target view gets injected and scaled into place. This is closer to how routing works in SPAs than to how slide decks work.
The landing page is built with Zumly itself so you can get the feel before touching any code.
Curious if anyone else has thought about this space. What makes zooming UIs work or fail?
Landing page (built with Zumly): https://zumerlab.github.io/zumly
GitHub: https://github.com/zumerlab/zumly","title":"Zooming UIs in 2026: Prezi, impress.js, and why I built something different","updated_at":"2026-07-22T03:26:43Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tinchox6"},"story_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"Lately, I\u2019ve been working on a small side project: a web tool for creating radial and circular layouts using CSS only. What I\u2019ve enjoyed the most is that it\u2019s completely non-AI\u2014just code, logic, and design decisions made by hand.
I have nothing against AI, but I found that building something without it has been almost therapeutic. Of course I know it is just a side project. I mean I'm not depend on its success for living.
It also made me wonder: in a world where AI is taking over so many creative and technical tasks, is there still a place for the joy of purely handcrafted software? Have others here felt something similar when working on non-AI projects?
Side project url \nhttps://github.com/zumerlab/orbit/"},"title":{"matchLevel":"none","matchedWords":[],"value":"Ask HN: Building a Non-AI tool feels surprisingly refreshing for me"}},"_tags":["story","author_tinchox6","story_43470309","ask_hn"],"author":"tinchox6","children":[43470596,43472693],"created_at":"2025-03-25T12:16:23Z","created_at_i":1742904983,"num_comments":3,"objectID":"43470309","points":7,"story_id":43470309,"story_text":"Lately, I\u2019ve been working on a small side project: a web tool for creating radial and circular layouts using CSS only. What I\u2019ve enjoyed the most is that it\u2019s completely non-AI\u2014just code, logic, and design decisions made by hand.
I have nothing against AI, but I found that building something without it has been almost therapeutic. Of course I know it is just a side project. I mean I'm not depend on its success for living.
It also made me wonder: in a world where AI is taking over so many creative and technical tasks, is there still a place for the joy of purely handcrafted software? Have others here felt something similar when working on non-AI projects?
Side project url \nhttps://github.com/zumerlab/orbit/","title":"Ask HN: Building a Non-AI tool feels surprisingly refreshing for me","updated_at":"2025-03-31T19:01:54Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tinchox6"},"story_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"Orbit CSS reached its V.1.0.0 and it is finally stable. Hope you find it useful and easy to use.
In the doc site (https://zumerlab.github.io/orbit-docs/) you can play with a multilevel piemenu, and explore potencial use cases covered in examples:
- Progress bars
- Charts (e.g., pie charts, multi-level pies, sunburst charts)
- Gauges
- Knobs
- Pie menus
- Watch faces
- Sci-fi art
- Chemical structures
- Calendars
- Dashboards
- Mandalas"},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: Orbit Composer \u2013 a CSS tool for creating any kind of circular interface"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"https://github.com/zumerlab/orbit"}},"_tags":["story","author_tinchox6","story_42573913","show_hn"],"author":"tinchox6","children":[42574694],"created_at":"2025-01-02T12:38:51Z","created_at_i":1735821531,"num_comments":2,"objectID":"42573913","points":6,"story_id":42573913,"story_text":"Orbit CSS reached its V.1.0.0 and it is finally stable. Hope you find it useful and easy to use.
In the doc site (https://zumerlab.github.io/orbit-docs/) you can play with a multilevel piemenu, and explore potencial use cases covered in examples:
- Progress bars
- Charts (e.g., pie charts, multi-level pies, sunburst charts)
- Gauges
- Knobs
- Pie menus
- Watch faces
- Sci-fi art
- Chemical structures
- Calendars
- Dashboards
- Mandalas","title":"Show HN: Orbit Composer \u2013 a CSS tool for creating any kind of circular interface","updated_at":"2025-01-02T16:02:57Z","url":"https://github.com/zumerlab/orbit"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tinchox5"},"story_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"Recently, I made public a CSS framework I developed for creating radial designs. During development, I faced several challenges, including testing different features. I noticed that CSS linters and other tools didn't allow me to see why something wasn't working, even if there were no basic errors. Another typical CSS problem was seeing how it was shared across different browsers. Fortunately, I discovered that certain new CSS features can be used to create a series of real-time tests. These features are `@support`, `@container`, and `:has()`.
By combining these features, I developed a testing system not only to check if the framework works in the browser but also, and most importantly, to see if we are applying HTML correctly according to the browser's requirements and avoiding involuntary errors when developing an application.
Since my CSS framework necessarily uses features that only the newest browsers have, such as trigonometric functions like `cos()` and `sin()`, I created a series of rules to test if they are supported by the browser. If they're not, a message appears asking to update the browser. Similarly, if the browser doesn't support `:has()`, which is used throughout the framework.
There are also typical cases of browser incompatibility, so in some non-critical cases, I use `@support` or `@container` to hide certain Orbit features that don't affect its use. For example, Safari doesn't accept SVG `context-stroke`, so I hide them.
However, beyond those critical checks and compatibility, the most common issue when using a CSS framework is not knowing how to use it properly. That's why I created other CSS rules that allow analyzing if a parent element has the required child elements and not others. Here, visual alerts also appear while developing to give a hint about where the error is in the code.
I don't want to bore you with the details specific to Orbit, but I'll leave you the link to the support source and related documentation.
Repo:\nhttps://github.com/zumerlab/orbit
Source file:\nhttps://github.com/zumerlab/orbit/blob/main/src/scss/_support.scss
Orbit related documentation: \nhttps://zumerlab.github.io/orbit-docs/tools/support/
Good to go deeper:\nhttps://heydonworks.com/article/testing-html-with-modern-css
edited: typo Suorce -> Source"},"title":{"matchLevel":"none","matchedWords":[],"value":"A practical way to test HTML and CSS in real-time using only CSS"}},"_tags":["story","author_tinchox5","story_41378981","ask_hn"],"author":"tinchox5","created_at":"2024-08-28T12:59:21Z","created_at_i":1724849961,"num_comments":0,"objectID":"41378981","points":6,"story_id":41378981,"story_text":"Recently, I made public a CSS framework I developed for creating radial designs. During development, I faced several challenges, including testing different features. I noticed that CSS linters and other tools didn't allow me to see why something wasn't working, even if there were no basic errors. Another typical CSS problem was seeing how it was shared across different browsers. Fortunately, I discovered that certain new CSS features can be used to create a series of real-time tests. These features are `@support`, `@container`, and `:has()`.
By combining these features, I developed a testing system not only to check if the framework works in the browser but also, and most importantly, to see if we are applying HTML correctly according to the browser's requirements and avoiding involuntary errors when developing an application.
Since my CSS framework necessarily uses features that only the newest browsers have, such as trigonometric functions like `cos()` and `sin()`, I created a series of rules to test if they are supported by the browser. If they're not, a message appears asking to update the browser. Similarly, if the browser doesn't support `:has()`, which is used throughout the framework.
There are also typical cases of browser incompatibility, so in some non-critical cases, I use `@support` or `@container` to hide certain Orbit features that don't affect its use. For example, Safari doesn't accept SVG `context-stroke`, so I hide them.
However, beyond those critical checks and compatibility, the most common issue when using a CSS framework is not knowing how to use it properly. That's why I created other CSS rules that allow analyzing if a parent element has the required child elements and not others. Here, visual alerts also appear while developing to give a hint about where the error is in the code.
I don't want to bore you with the details specific to Orbit, but I'll leave you the link to the support source and related documentation.
Repo:\nhttps://github.com/zumerlab/orbit
Source file:\nhttps://github.com/zumerlab/orbit/blob/main/src/scss/_support.scss
Orbit related documentation: \nhttps://zumerlab.github.io/orbit-docs/tools/support/
Good to go deeper:\nhttps://heydonworks.com/article/testing-html-with-modern-css
edited: typo Suorce -> Source","title":"A practical way to test HTML and CSS in real-time using only CSS","updated_at":"2024-09-20T17:42:46Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tinchox5"},"story_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"I started hacking on what later became SnapDOM in April this year. At first it wasn\u2019t even meant to be a standalone library \u2014 it began as an internal tool for a zoomable UI project (Zumly), I was building. To make that project work, I needed a way to capture DOM elements with high speed and fidelity. Existing DOM-to-image libraries like html2canvas often failed in subtle but important ways: missing pseudo-elements, mis-rendering fonts, ignoring Shadow DOM, or breaking on Safari. What started as a quick internal hack slowly grew into its own project.
Open sourcing SnapDOM changed everything. Suddenly the audience wasn\u2019t just me, but anyone with their own browser, CSS, and HTML quirks. That\u2019s when I realized how immense the attack surface really is. Every combination of engines, DOM structures, styles, and external resources can break in unexpected ways. At times it felt overwhelming, but I\u2019ve learned to treat each bug as a reproducible pattern: isolate it, fix it, and carry the lesson forward.
From the beginning, two principles guided the work: fidelity and speed. Capturing \u201cevery detail\u201d would not matter if the process was unbearably slow, so I spent a lot of time on caching strategies, incremental updates, and efficient DOM cloning. Benchmarking against existing libraries became part of the routine. Performance was never an afterthought \u2014 it was always as important as accuracy.
On the technical side, SnapDOM pushed me into DOM cloning strategies, caching, font embedding heuristics, browser-specific hacks, and the constant tradeoffs between fidelity and performance. On the personal side, it has been just as educational: patience, humility, and learning to really listen to users. Some of the best moments have been receiving thoughtful PRs and clear reproduction cases \u2014 collaboration that genuinely made the project better. The respect shown in these contributions has been one of the most motivating parts of the journey.
Another milestone: only a few months in, SnapDOM already has its first two GitHub Sponsors and has passed 6k stars on GitHub. Knowing that people found enough value to sponsor the project, and that thousands more cared enough to star it, has been incredibly rewarding.
I\u2019ve also been designing a plugin system, so the core stays lean while features like cropping, filters, or alternative exporters can live as extensions. It\u2019s not merged into the mainline yet, but it\u2019s a direction I\u2019m excited about \u2014 and another layer of complexity to manage as the project evolves.
It\u2019s still early days, but reflecting on the journey from April to now has been meaningful. What started as a small internal helper for a zoomable UI turned into an open source project with real users, contributions, sponsors, and community respect. Balancing the technical struggles with the human side of open source has made this one of the most rewarding experiences I\u2019ve had so far.
Thank you,\nMartin
Repo: https://github.com/zumerlab/snapdom"},"title":{"matchLevel":"none","matchedWords":[],"value":"From frustration to open source adoption: my journey building SnapDOM"}},"_tags":["story","author_tinchox5","story_45394753","ask_hn"],"author":"tinchox5","created_at":"2025-09-27T11:04:38Z","created_at_i":1758971078,"num_comments":0,"objectID":"45394753","points":3,"story_id":45394753,"story_text":"I started hacking on what later became SnapDOM in April this year. At first it wasn\u2019t even meant to be a standalone library \u2014 it began as an internal tool for a zoomable UI project (Zumly), I was building. To make that project work, I needed a way to capture DOM elements with high speed and fidelity. Existing DOM-to-image libraries like html2canvas often failed in subtle but important ways: missing pseudo-elements, mis-rendering fonts, ignoring Shadow DOM, or breaking on Safari. What started as a quick internal hack slowly grew into its own project.
Open sourcing SnapDOM changed everything. Suddenly the audience wasn\u2019t just me, but anyone with their own browser, CSS, and HTML quirks. That\u2019s when I realized how immense the attack surface really is. Every combination of engines, DOM structures, styles, and external resources can break in unexpected ways. At times it felt overwhelming, but I\u2019ve learned to treat each bug as a reproducible pattern: isolate it, fix it, and carry the lesson forward.
From the beginning, two principles guided the work: fidelity and speed. Capturing \u201cevery detail\u201d would not matter if the process was unbearably slow, so I spent a lot of time on caching strategies, incremental updates, and efficient DOM cloning. Benchmarking against existing libraries became part of the routine. Performance was never an afterthought \u2014 it was always as important as accuracy.
On the technical side, SnapDOM pushed me into DOM cloning strategies, caching, font embedding heuristics, browser-specific hacks, and the constant tradeoffs between fidelity and performance. On the personal side, it has been just as educational: patience, humility, and learning to really listen to users. Some of the best moments have been receiving thoughtful PRs and clear reproduction cases \u2014 collaboration that genuinely made the project better. The respect shown in these contributions has been one of the most motivating parts of the journey.
Another milestone: only a few months in, SnapDOM already has its first two GitHub Sponsors and has passed 6k stars on GitHub. Knowing that people found enough value to sponsor the project, and that thousands more cared enough to star it, has been incredibly rewarding.
I\u2019ve also been designing a plugin system, so the core stays lean while features like cropping, filters, or alternative exporters can live as extensions. It\u2019s not merged into the mainline yet, but it\u2019s a direction I\u2019m excited about \u2014 and another layer of complexity to manage as the project evolves.
It\u2019s still early days, but reflecting on the journey from April to now has been meaningful. What started as a small internal helper for a zoomable UI turned into an open source project with real users, contributions, sponsors, and community respect. Balancing the technical struggles with the human side of open source has made this one of the most rewarding experiences I\u2019ve had so far.
Thank you,\nMartin
Repo: https://github.com/zumerlab/snapdom","title":"From frustration to open source adoption: my journey building SnapDOM","updated_at":"2026-03-05T22:45:30Z"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tinchox5"},"story_text":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"Orbit CSS reached its V.1.0.0 and it is finally stable. Hope you find it useful and easy to use.
In the doc site (https://zumerlab.github.io/orbit-docs/) you can play with a multilevel piemenu
...and explore potencial use cases covered in examples:\n- Progress bars\n- Charts (e.g., pie charts, multi-level pies, sunburst charts)\n- Gauges\n- Knobs\n- Pie menus\n- Watch faces\n- Sci-fi art\n- Chemical structures\n- Calendars\n- Dashboards\n- Mandalas
Whatever, have a good 2025!!"},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: First Orbit stable version to build any kind of radial UI with CSS only"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"https://github.com/zumerlab/orbit"}},"_tags":["story","author_tinchox5","story_42542339","show_hn"],"author":"tinchox5","created_at":"2024-12-29T19:36:28Z","created_at_i":1735500988,"num_comments":0,"objectID":"42542339","points":3,"story_id":42542339,"story_text":"Orbit CSS reached its V.1.0.0 and it is finally stable. Hope you find it useful and easy to use.
In the doc site (https://zumerlab.github.io/orbit-docs/) you can play with a multilevel piemenu
...and explore potencial use cases covered in examples:\n- Progress bars\n- Charts (e.g., pie charts, multi-level pies, sunburst charts)\n- Gauges\n- Knobs\n- Pie menus\n- Watch faces\n- Sci-fi art\n- Chemical structures\n- Calendars\n- Dashboards\n- Mandalas
Whatever, have a good 2025!!","title":"Show HN: First Orbit stable version to build any kind of radial UI with CSS only","updated_at":"2024-12-30T06:56:27Z","url":"https://github.com/zumerlab/orbit"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"based2"},"title":{"matchLevel":"none","matchedWords":[],"value":"New critical vulnerability in multiple high-privileged Android services"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"https://blog.zimperium.com/cve-2018-9411-new-critical-vulnerability-multiple-high-privileged-android-services/"}},"_tags":["story","author_based2","story_18352769"],"author":"based2","children":[18362168,18362644,18362838,18363428],"created_at":"2018-11-01T11:11:08Z","created_at_i":1541070668,"num_comments":17,"objectID":"18352769","points":233,"story_id":18352769,"title":"New critical vulnerability in multiple high-privileged Android services","updated_at":"2024-09-20T03:18:35Z","url":"https://blog.zimperium.com/cve-2018-9411-new-critical-vulnerability-multiple-high-privileged-android-services/"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tinchox5"},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: Orbit \u2013 A CSS radial UI composer framework"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"https://zumerlab.github.io/orbit-docs/"}},"_tags":["story","author_tinchox5","story_41189637","show_hn"],"author":"tinchox5","children":[41189642,41191476,41191543,41192011,41192144,41192307,41194824,41203255,41214397],"created_at":"2024-08-08T09:35:46Z","created_at_i":1723109746,"num_comments":26,"objectID":"41189637","points":145,"story_id":41189637,"title":"Show HN: Orbit \u2013 A CSS radial UI composer framework","updated_at":"2024-09-20T17:38:14Z","url":"https://zumerlab.github.io/orbit-docs/"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tinchox6"},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: I created snapDOM to capture DOM nodes as images with exceptional speed"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"https://github.com/zumerlab/snapdom"}},"_tags":["story","author_tinchox6","story_43813330","show_hn"],"author":"tinchox6","children":[43813611,43813622,43813674,43813740,43813871,43813890,43814037,43814143,43814405,43814523,43814555,43814739,43816417,43816972,43819875,43822199,43864024,43886960],"created_at":"2025-04-27T17:00:29Z","created_at_i":1745773229,"num_comments":43,"objectID":"43813330","points":120,"story_id":43813330,"title":"Show HN: I created snapDOM to capture DOM nodes as images with exceptional speed","updated_at":"2026-01-13T13:24:05Z","url":"https://github.com/zumerlab/snapdom"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"eugenv"},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: I made an RSS News Reader that prioritizes topics you care about"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"https://www.zuperlist.com/"}},"_tags":["story","author_eugenv","story_15514805","show_hn"],"author":"eugenv","children":[15514807,15517728,15517817,15518056,15518070,15518263,15518383,15518883,15520585],"created_at":"2017-10-20T10:53:10Z","created_at_i":1508496790,"num_comments":29,"objectID":"15514805","points":61,"story_id":15514805,"title":"Show HN: I made an RSS News Reader that prioritizes topics you care about","updated_at":"2024-09-20T01:27:46Z","url":"https://www.zuperlist.com/"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"jmm77"},"title":{"matchLevel":"none","matchedWords":[],"value":"Benchmark: snapDOM vs html2canvas"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"https://zumerlab.github.io/snapdom/"}},"_tags":["story","author_jmm77","story_44307298"],"author":"jmm77","children":[44307899,44308036,44308056,44308236,44308287],"created_at":"2025-06-18T06:55:54Z","created_at_i":1750229754,"num_comments":16,"objectID":"44307298","points":47,"story_id":44307298,"title":"Benchmark: snapDOM vs html2canvas","updated_at":"2025-07-29T05:46:04Z","url":"https://zumerlab.github.io/snapdom/"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"PaulSec"},"title":{"matchLevel":"none","matchedWords":[],"value":"How I Hacked Telegram\u2019s \u201cEncryption\u201d"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"http://blog.zimperium.com/telegram-hack/"}},"_tags":["story","author_PaulSec","story_9095059"],"author":"PaulSec","children":[9095826,9095884,9095885,9095901,9095932,9095936,9096137],"created_at":"2015-02-23T16:17:14Z","created_at_i":1424708234,"num_comments":17,"objectID":"9095059","points":40,"story_id":9095059,"title":"How I Hacked Telegram\u2019s \u201cEncryption\u201d","updated_at":"2025-07-25T20:47:52Z","url":"http://blog.zimperium.com/telegram-hack/"},{"_highlightResult":{"author":{"matchLevel":"none","matchedWords":[],"value":"tinchox5"},"title":{"matchLevel":"none","matchedWords":[],"value":"Show HN: I made a set of devtools for small projects"},"url":{"fullyHighlighted":false,"matchLevel":"full","matchedWords":["zumper"],"value":"https://github.com/zumerlab/zumerbox"}},"_tags":["story","author_tinchox5","story_39843392","show_hn"],"author":"tinchox5","children":[39843394,39845537,39854429,39859485],"created_at":"2024-03-27T19:16:21Z","created_at_i":1711566981,"num_comments":7,"objectID":"39843392","points":28,"story_id":39843392,"title":"Show HN: I made a set of devtools for small projects","updated_at":"2024-09-20T16:41:20Z","url":"https://github.com/zumerlab/zumerbox"}],"hitsPerPage":50,"nbHits":488,"nbPages":10,"page":0,"params":"query=Zumper&tags=story&hitsPerPage=50&advancedSyntax=true&analyticsTags=backend","processingTimeMS":10,"processingTimingsMS":{"_request":{"roundTrip":23},"afterFetch":{"format":{"highlighting":1,"total":1},"merge":{"mergeLoop":{"prepareNextHit":7,"total":7},"total":7},"total":7},"fetch":{"query":1,"total":2},"total":10},"query":"Zumper","serverTimeMS":12}