Hacker Newsnew | past | comments | ask | show | jobs | submit | franky47's commentslogin

This is hilarious, thank you!

How did it match my facial hair in the XKCD, since HN is text-only? :mind-blown:

https://hn-wrapped.kadoa.com/franky47


That’s what CI is for.

Refined GitHub [1] still does (for things like PR approvals & automations), and it feels odd indeed. Still worth adding on top of the stock UI.

[1] https://github.com/refined-github/refined-github


Sad, I wrote my first ever programs on Arduino, learned C++ through it, and did my first OSS contribution by creating the Arduino MIDI Library, ~16 years ago.

I wouldn't be where I am if it wasn't for Arduino. Thank you to the OSH community for making these boards open to all back then.


I gave my kids (5 and 2) two Volcas (Beats & Keys) to play with. The Keys is a bit too advanced (too easy to get no sound at all, or something that sounds horrible), but the Beats is a wonderful machine for kids, as it's virtually impossible to make it sound bad. Also great to teach them rhythm.


Except you hit limits when trying to share that URL. Eg: try pasting a URL longer than 4096 bytes in Signal or WhatsApp, and they don't render it as clickable.


Thanks for mentioning it! (I'm the author)


Thanks for the feedback, Vercel domain uses nuqs [1] (I'm the author) for URL state, and I agree flooding the browser history is a bad experience.

Is there a way to update the URL (ie: keeping it reactive in the address bar) without creating those history entries, or to ask the browser to squash the last entry it created into the previous one?

[1] https://nuqs.dev


I am not aware of any approaches that work consistently across all major browsers. This matter is nothing new -- there's a Bugzilla report[0] from 13 years ago about this behavior that remains open.

Since there's no spec for global history and it's unlikely one will be introduced, the most practical solution to avoid flooding the browser history would be to debounce the changes.

This is the approach taken by Google Maps -- with maps being a well-known case where URL updates would clutter the history, as noted in the Bugzilla report.

[0] https://bugzilla.mozilla.org/show_bug.cgi?id=753264


Cursed alphabetical sorting of numbers:

8 5 4 9 1 7 6 3 2 0

Can you guess what it is?


They are sorted by their Unicode character names obviously

U+0038 DIGIT EIGHT

...

U+0030 DIGIT ZERO


The reaction (removing the package) is also similar to an inexperienced developer when confronted to their first vulnerability report.

Assuming good intentions (debugging) rather than malice was at play, communication is key: drop the malicious version of the package, publish a fix, and communicate on public channels (blog post, here on HN, social media) about the incident.

A proper timeline (not that AI slop in the OP article) also helps bring back trust.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: