HN user

comfymatrix

29 karma
Posts3
Comments15
View on HN

How is it worse than having to use up all my RAM in a few browser tabs with unresponsive PWAs such as Outlook for work? I much rather have Thunderbird or Evolution silently in the background popping up notifications when I get emails - not to mention it’s much easier to compartmentalise within a DE, i.e I know my email is workspace #4 instead of having to flash scroll through all my open tabs

Apple’s Mistake 5 years ago

today the scanning is only for images uploaded to iCloud, and only for CSAM

This, to me, would be exponentially less privacy invasive as I’ve come to assume all major cloud hosting providers implement something like this (look at Google Drive), but Apple has said that the scanning is done on-device, meaning whether or not you upload your photo library to iCloud, your local photos will be scanned with an on-device database of hashes.

Essentially iOS photos now implement a direct API call to the feds with some vague “human verification” layer if you go above an unknown threshold

I feel the same, just with the times flipped around. For me the morning is great for small random/admin type tasks. Even reading a research paper or spending some time learning about something I need to do/use.

In the afternoon is when I can concentrate for 2-4 hours and do some intense work. Take a break after that, and iron out anything small before calling it a day.

I love the demoscene. I’ve been trying to get into it for some time now but it’s actually hard in terms of that are very little if any resources aimed at beginners and demo examples and tutorials.

The resources I’ve found are either incomplete or assume one is already familiar with the domain.

I understand graphics to the extent I’ve written a raytacer and a “semi-caster”, but can’t find my foot in demos, especially translating my existing graphics knowledge to ASM.

Anyone have any resources or information I may have missed?

https://bayesianneuron.com/

Hopefully I’m not late to the party!

I write about ML, optimization & CS, and... well, whatever I want or find interesting. I have a public backlog of projects and blog posts too.

I started it because I kinda like writing, but also because when I do write (technical topics) I enjoy giving very clear, fully understandable explanations.

Not a fan of the “here’s concept A, it’s very straightforward... we’re now at concept Z which as you can see makes use of A” style of writing. I understand it’s need and use, you can't always explain everything, especially if the topic is already very niche and highly complex, or maybe you don’t have the space.

I find that it lets me learn more or jogs my memory on other subjects when I have to fully explain and try to teach things.

Also blogging is fun!

I’m an ML engineer (was) and am looking for contract work during this time. In previous I also worked as a sysadmin and a python engineer. I’ve experience managing large servers and AWS. I also have experience in optimization and love hard problems. MSc in CS

Location: GMT Remote: Yes (ONLY) Willing to relocate: No. Technologies: Python, PyTorch, Sklearn, Postgress, Mongo, AWS Resumé/CV: I wish to remain anonymous on here so please use my email and I’ll get back to you. Email: kl3u4z+a3od9aa48ibiw@sharklasers.com

I don't get this? It checks against a limited list of websites if a username is taken. So what? This is hardly doxxing or "smart". Simply a faster method than the manual way, except it doesn't exhaust all avenues of search.

Out of curiosity, what stopped you from making several regexes, especially for the product numbers (ending in "-ND")? Was it mainly for edge cases or cases where it might have been slightly different?

Or, was it due data context, which I assume is more plausible. I ask because I maintain an old, slightly large, and growing project which contains about 12 different regexes and is used on messy unstructured data. I'm in the process of rewriting it into a more general framework using NER + RNNs or HMMs, but this seems like a very interesting approach.