j-scott
j-scott on Hacker News
DJs are typically playing on promoter or venue provided equipment, which is usually industry standard of pioneer/AT.
Otherwise, they bring their own, especially if it’s anything custom or specific to their performance.
The feature definitely does what it says it does, but I think that the mount is generally accessible outside the software may be where the “surprise” lies.
I definitely would not have used this feature on a public network or exposed the mount to the open internet as well.
Rekordbox is one of the worst pieces of software I have to interact with regularly, and it reminds me of others descriptions of IoT software/firmware.
"PRO DJ LINK" enables you to access rekordbox libraries (and load music files) remotely from other devices, whether that be on a computer or dedicated Pioneer/AlphaTheta hardware.
The vulnerability in question requires the attacker to be on the same local network as the instance of rekordbox and for the remote library feature to be enabled. Interested in the full writeup once it's released
Posted by
j-scott on Friday June 19, 2026 @12:22AM
from the store.steampowered.com dept.
My bad! I was wrong; added a playground demonstration the parsing behavior above.
Not a hyperscaler, but we’re multi-cloud and probably one to two steps down.
My team’s service implements a number of performance and functionality improvements on top of your typical registry to support the company’s needs.
I can’t say much more than that sadly.
I work on the container registry team at my current company running a custom container registry service!
Music production, but I’m finally taking the leap after a decade of saying it wasn’t for me.
In my most recent cycle, I didn’t ask to use AI and I was only warned once about using AI when I had the official language plugin for an IDE annotate some struct fields with json tags. I explained the plugin functionality and we moved on.
When I was part of interviews on the other side for my former employer, I encountered multiple candidates who appeared to be using AI assistance without notifying the interviewers ahead of time or at all.
Not in the Bay Area, but I have friends at FB and I believe their RTO policy is strongly enforced unless you’re senior and have been at the company for a year at which point you can go remote.
Phone screen was 2 problems in 45 minutes, I believe the onsite portion would have been more of the same but I didn’t get that far :D
Databricks, Snowflake and Stripe required NDAs for the onsite portion of the loop.
The NDAs covered anything internal discussed during the hiring loop.
Started prepping/interviewing in Oct after reading this post:
https://news.ycombinator.com/item?id=41402581Secured interviews with Facebook, Databricks, Snowflake, and Stripe (3 referrals, 1 recruiter reach out).
Bombed the FB phone screen due to nerves/first interview of the cycle. Completed the remaining three loops by December, and got offers from Databricks and Snowflake (Stripe went on two week holiday break and hasn’t gotten back to me yet).
Accepted the Databricks offer!
Happy to talk about practice/process (within the limits of the interview NDAs)!
This is very similar to an issue I had while playing games on a wired Windows desktop. I haven’t run into it in a long time now that I think about it. I wonder what might have changed.
> People who stress over code style, linting rules, or other minutia are insane weirdos
Stressing over these things is certainly a Sisyphean task.
However, investing in automating and standardizing the application of these things every time a new repo is created eliminates an entire class of problems and saves you all sorts of trouble down the road.
I've lurked on hacker news for a number of years, and this post is what inspired me to finally make an account. Thank you for sharing; this aligns with my current situation and reinforces my recent decision that I need to make a change.