HN user

calmingsolitude

685 karma
Posts13
Comments38
View on HN

Basically all of Graphene's RCS issues have been fixed[0]. Additionally, your stance seems somewhat unusual - GrapheneOS isn't only meant to be used by people that have "something to hide". As for explaining it to border guard - it's just Android - if you're unlocking your phone for them anyway, they definitely shouldn't care about what flavor of Android you're running, whether it's LineageOS, ColorOS, GrapheneOS, etc.

Of course, there might be more nuance to your situation than I am privy to, but almost everyone travels, and I'd heavily hope that being stopped at the border isn't the reason keeping them away from Graphene.

[0] stickied comment on https://www.reddit.com/r/GrapheneOS/comments/1pceh1t/am_i_th...

I still use it because I like how easy it is to use extensions on iOS but definitely agree that there are a lot of UI bugs. Listing the most prominent ones just in case the dev is around:

- At times, the search bar text disappears and the "refresh page" icon is left aligned (instead of right aligned).

- When a link has an associated app that can open it, Orion opens a modal that asks whether you'd like to open it in-app or continue on the browser. However, sometimes it immediately opens the app and shows the modal once you navigate back.

- When using a custom search engine, you can no longer use the search bar to edit your query and it just shows the url.

If I were to hazard a guess, Valve was apprehensive about releasing the steam machine/frame this year because the high memory prices would mean that they'd have to price the steam machine/frame pretty high as well. However, once they saw how the steam deck was selling like hot cakes even after a $300 bump, they're deciding to go for it anyway.

You've advertised twice on this thread about your site, but I personally find the UX to be worse, not to mention the phantom scroll issues and (imo) the tasteless animations.

A few words on DS4 2 months ago

Parent is simply pointing out the incorrect usage of "empirically", which should typically only be mentioned when you've tested it yourself.

This was true a few years back, but in recent times Creality has fallen victim to quality control issues, a huge number of printer variants and generally having a not so great out of the box experience. You'll find this sentiment echoed in comments on any of the 3d printing subreddits as well.

Thanks for the update. The usage of an affiliate link feels quite dishonest here because the hyperlink says bunny.net but then opens up bunny.net/?ref=xxxx

IMO closing issues via stale bot is fine, the problem is locking issues so that no further conversation is allowed on the issue. Multiple times, I've encountered multi-year old issues (which is usually not fixed due to the fix not being simple or compatible with the current architecture). There's usually a good amount of conversation between users offering workarounds (and those workarounds updated for newer versions) - till stale bot locks the issue.

A Broken Heart 6 months ago

When I read the first sentence, I expected the author to use `git bisect`.

However, what the author seems to have done is used a prompt with claude that probably looked something like this:

"Some piece of code is causing the page to load very slowly. To debug this, I'd like to use binary search, where we keep commenting/uncommenting 50% of the remaining code, and then I manually check if the page is still very slow. Let's start now; Comment out a component (or parts of a component) that you estimate is 50% of the page, and I will tell you if the page is still slow."

This is a pretty cool project and I think the comments here are being overly negative. Sure, removing the constraints that the eBPF verifier requires might encourage more complex and less performant code - but this is just another tool in the toolbox. For truly production systems, I can see the battle-tested eBPF being the top choice over a dubious kernel extension. But for quick prototyping? Rex can probably take the cake here once the project matures a bit more.

Here's the problem: your reply is factually correct, but it doesn't address the GP's overarching complaint - the start menu is simply not performant. And since the code powering the start menu is closed source, it is not possible to perform a benchmark to see if the react native portion of the start menu is to blame or if it is something else.

Visiting this site on mobile is not great. A good portion of the screen is covered by a sticky header and there is no underline or feedback when a link is clicked. Additionally, it is missing the story position and with infinite scroll there is no way to differentiate whether you are looking at the 10th story or the one in the 100th position.

Downloaded v3 but it kept crashing for me on Windows 10. Possibly because I had designer v1 previously installed. If anyone's facing the same issue, deleting %APPDATA%\Affinity directory fixes this.

I have termux installed to quickly run `ip neigh` to find the IP addresses of devices connected to the hotspot - unfortunately my version of Android doesn't have this feature built in.

This is especially useful when you have multiple Pis connected and need to know the IP address to ssh to.

Stars are public - navigating to any GitHub profile and clicking the 'Stars' tab shows all the repositories starred by the user. Moreover, all users that have starred a repository can be viewed by appending /stargazers to the repo url or clicking the stars link in the sidebar.

I've had the experience of being on the opposite end of the spectrum when I made a joke site[0] that kept the connection open to every connected browser. Needless to say, it got hugged to death in the very first ten minutes.

What got it back up was switching from my homebrew webserver to Nginx and increasing the file descriptor limits. Switching to a battle-tested webserver made all the difference. I'm still not sure how many connections it can keep open now, but I don't have to worry about the static parts of the site going down.

[0] https://youcantdownloadthisimage.online/

Might come in useful to others on Win11:

To get the snipping tool working, close the snipping tool, manually set the date to around the start of October. Reopen the snipping tool and it should be working. The date can now be set back.