doodlesdev (u/doodlesdev)

doodlesdev commented on I got hacked: My Hetzner server started mining Monero blog.jakesaunders.dev/my-... · Posted by u/jakelsaunders94

exceptione · 3 days ago

The first step I would take is running podman instead of Docker to prevent container escapes. Podman can be run truly rootless and doesn't mess with your firewall. Next I would drop all caps if possible.

doodlesdev · 3 days ago

What's the difference between running Podman and running Docker in rootless mode? (Other than Docker messing with the firewall, which apparently OP doesn't know about… yet). I understand Podman doesn't require a daemon, but is that all there is to it, or is there something I'm missing?

doodlesdev commented on Scientists say X has lost its professional edge and Bluesky is taking its place psypost.org/scientists-sa... · Posted by u/CharlesW

marc_io · 3 months ago

Oh, at least here in Brazil, people still find it strange if you say you don't have an Instagram account. There's this idea of being a bit weird for not following this trend.

doodlesdev · 3 months ago

Brazil is an exception, though! Did you know we are the third country in the world with the largest number of Instagram users? [0]

Social media is very cultural here, so I'm not sure that we are representative of a larger trend in social media acceptance worldwide.

[0]: https://www.statista.com/statistics/578364/countries-with-mo...

doodlesdev commented on Less is safer: Reducing the risk of supply chain attacks obsidian.md/blog/less-is-... · Posted by u/saeedesmaili

doodlesdev · 3 months ago

   > Only a handful of packages are part of the app you run, e.g. Electron, CodeMirror, moment.js.

So they ship an extremely bloated package to ship a WebView based on one of the most complex pieces of software ever written, an entire code editor for text editing, and a deprecated time library that could be substituted by newer APIs and some glue code?

Honestly, it doesn't seem impressive at all. What Obsidian does is the bare minimum of how we should manage packages in any piece of software, not a testament to a serious security policy. They do security audits, though, which I find to be a good practice.

doodlesdev commented on Hologram v0.5.0 hologram.page/blog/hologr... · Posted by u/bartblast

bartblast · 5 months ago

That's odd - I've tested the site multiple times previously and consistently got LCP results between 0.12-0.40s on large pages, which I consider very good results. I just tested it again on a large page using the Google Chrome Performance tab and got 0.14s LCP. I'm testing on the production site, connecting from Warsaw.

The 1.5s LCP you're seeing is quite different from what I'm observing. Performance can vary significantly based on location, network conditions, and device capabilities, so perhaps that's contributing to the difference in our results?

It's also possible that different pages have different performance characteristics depending on their content complexity and the navigation structure. Could you share which specific page you tested? That would help me understand the discrepancy better.

Regarding the runtime size - it hasn't been optimized at all yet, so I expect it will be much smaller in the future. I wouldn't be surprised if we can reduce it by a few times through proper optimization.

You're absolutely right that for a pure documentation site, a no-JS approach with prefetching would be lighter. The Hologram docs site is indeed dogfooding - I wanted to showcase the framework's capabilities and stress-test it with real-world usage, even if it means some overhead for this particular use case.

The goal was to demonstrate the instant navigation experience you mentioned, plus features like client-side search and interactive examples in the future that benefit from the stateful client-side architecture.

Thanks for taking the time to test the site and provide this feedback!

doodlesdev · 5 months ago

The LCP I see is from Google PageSpeed Insights, meaning it's not benchmarked on my machine! In fact, in my setup I'll get much faster load times, but that performance level likely won't be representative of my users (I have a pretty good fiber connection till the last meter, I use Ethernet to connect, and I have a pretty beefy development workstation). The numbers you will see there aren't exactly comparable to the Lighthouse benchmarks you will perform locally: 1.5s LCP is still pretty decent, considering the average website speed nowadays, just not what I would expect from a static docs website, if that makes sense.

The page I tested is the one linked here in HN (the announcement)! I guess I should've referenced the PageSpeed Insights URL [0]. I hope you can get your bundle sizes smaller in the next versions, because honestly, from my first look (not very in-depth, of course), it's the only thing that's not very attractive about it. Likewise, I keep in mind, though, that most web frameworks nowadays ship very large bundles to achieve hydration and client-side routing.

I'm excited to see future updates to this project!

[0]: https://pagespeed.web.dev/analysis/https-hologram-page-blog-...

doodlesdev commented on Hologram v0.5.0 hologram.page/blog/hologr... · Posted by u/bartblast

doodlesdev · 5 months ago

I must say the proposal for Hologram is extremely interesting. The website is made using Hologram, and it speaks loudly to how good it is: every page navigation is (practically) instantaneous. Compared to other approaches such as LiveView, it's pretty good.

The initial page load isn't impressive, though: Google's PageSpeed Insights indicates a 100+kb runtime with lots of unused JavaScript initially, resulting in a LCP of 1.5s (results will vary, of course). I wonder how much of the JavaScript is simply code that stores the website pages, haven't had the time to look at this in detail yet.

For a docs website, that's excessive and bloated; it'd be much better to just deliver no JS and provide HTML with prefetching rules and cache headers (which would also provide instant navigation and offline support).

I'm happy they made the docs website with it, though, to dogfeed and showcase it.

doodlesdev commented on Lumo: Privacy-first AI assistant proton.me/blog/lumo-ai... · Posted by u/pentagrama

pxc · 5 months ago

Dark theme is an accessibility issue for people with eye diseases like mine. If you both need high luminance contrast and have photophobia, dark themes are the only ones that are usable.

There are workarounds, like inverting all the colors on your screen, but they suck.

doodlesdev · 5 months ago

You can also use the Dark Reader browser extension [0], an open-source extension for Chromium and Firefox that works on most websites (including Hacker News) in the dynamic mode, restyling the page to a dark theme!

[0]: https://darkreader.org/