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

https://vladde.net/

my personal page :)


from the email sent to me:

> Although our investigation is still ongoing, our early review indicates that your personal data has been accessed, which may include: Identity information: > - first name, last name, date of birth, gender; > - Contact information: email address, home address, telephone number, if provided; > - Passport information: passport number, country of issue and expiration date (not including copies of the documents).


> There are 169 guests currently online and -1 members (168 users in total).

haha this made me chuckle


Old joke:

A pair of mathematicians are sitting in a park chatting. There’s a snack shack near by, and while they’re talking, three people walk into the building. Some time later, four people walk out, and another couple walks in. A bit after that, two more people walk out. One of the mathematicians notices this and comments to the other, “you know, if one more person walks into that building, it’ll be empty.”


at least they are not renaming retroactively.

looking at you USB 3.0 (or USB 3.1 Gen 1 (or USB 3.2 Gen 1))


AWS just renamed their Security Hub service to Security Hub CSPM and then created a new service named Security Hub that is related but completely different than the original service.


And there's AWS S3, and there's AWS Glacier. And there's AWS S3, Glacier storage tier, which isn't Glacier. Which is OK, because Glacier is going away, and you should use S3, Glacier tier. Unless you're already using it, in which case you can still use it. So you still have to know Glacier and Glacier, while both storing your data, aren't technically the same thing.

But if you think that's bad, you haven't seen the name change shenanigans Microsoft pulls in Azure.


looks sick. website says it's open for pre-orders, but it's not?


> The algorithm provides accurate results over a period of ±1.89 Trillion years

i'm placing my bets that in a few thousand years we'll have changed calendar system entirely haha

but, really interesting to see the insane methods used to achieve this


Maybe not in a few thousand years, but given the deceleration of the Earth’s rotation around its axis, mostly due to tidal friction with the moon, in a couple hundred thousand years our leap-day count will stop making sense. In roughly a million years, day length will have increased such that the year length will be close to 365.0 days.

I therefore agree that a trillion years of accuracy for broken-down date calculation has little practical relevance. The question is if the calculation could be made even more efficient by reducing to 32 bits, or maybe even just 16 bits.


> The question is if the calculation could be made even more efficient by reducing to 32 bits, or maybe even just 16 bits.

This is somewhat moot considering that 64-bits is the native width of most modern computers and Unix time will exceed 32-bits in just 12 years.


I meant reducing the representable year numbers, not the whole timestamp.


Shorter term the Gregorian calendar has the ratio for leap years just a tiny bit wrong which will be a day off by 3000 years or so.


> i'm placing my bets that in a few thousand years we'll have changed calendar system entirely haha

Given the chronostrife will occur in around 40_000 years (give or take 2_000) I somewhat doubt that </humor>


The calendar system already changed. So this won't get correct dates, meaning the dates actually used, past that date. Well, those dates, as different countries changed at different times.


Wouldn’t it be accurate for that as well? Unless we change to base 10 time units or something. Then we all have a lot of work to do.

But if it’s just about starting over from 0 being the AI apocalypse or something, I’m sure it’ll be more manageable, and the fix could hopefully be done on a cave wall using a flint spear tip.


Or set 0 to be the Big Bang and make the type unsigned. Do it the same time we convert all temperature readings to Kelvin.


And count Planck time instead of seconds.. it's not as impossible as it may sound. You'll need more than 128 bits but less than 256 bits even if the epoch is the Big Bang (I can't recall exactly how many bits are needed, but I did the math once, some years ago). And it'll be compatible with alien or future time systems too, in case what we call a second (currently defined by caesium-133 periods) changes.


is there any way to remove entries with the CSV import function?

my bank includes transactions that are yet not final (preliminary transaction where currency conversion still isn't final). these rows change both in both the title and the amount, but i can do some guessing on how a row updates.

however: when i import my transaction a couple days later again, i need to manually keep track and remove preliminary transactions (now removed from my bank's export).

related: when i imported a CSV into YNAB, i would have to manually keep track of updated entries and remove those. with some code and state handling, i could figure out which rows no longer existed – but i couldn't remove them with the import function.

i ended up abandoning YNAB's CSV import and use their API to remove transactions... but it would have been much simpler if the CSV import could just have removed certain rows from the get-go.

(while i don't think this acts as a budget, it think others will run into similar issues as i have when it comes to importing CSV files)


could someone please explain what this means?

> cluster the inconsistent labels by embedding them in a vector space


For any label it generates, he uses an embedding model to generate the embedding vector for it. (You could say that "embeds the label in a vector space") Then, he looks at that generated embedding for that label and asks if there is another previously-generated embedding that had a _very_ similar embedding generated for it. If you set some sort of "how close is close enough" threshold for that, you are "clustering" all generated labels, by saying "These 10 labels have slightly different words, but essentially mean the same thing.


> It's still the wrong answer, because the question should have been, "How can I make this code thread-safe?" and whose answer is "Use System.Collections.Concurrent" and 1 line of code.

I often found myself adding "use built-in features if they exists", just because because of this type of scenario.

It unsettles me that some people feel okay always accepting AI code, even when it "works".


One of the easiest ways (for me) to spot AI code on a homework assignment has been to ask myself a simple question. Is this code something that would make sense for a human to write. It doesn't catch all cases - it doesn't catch even the majority of cases - but it does filter out people who just took the assignment and pasted it in to a prompt.

Mirroring the example provided in the article I once saw a 200 line class implementation for tridiagonal matrices in python - where a simple numpy command would suffice and perform an order of magnitude better.


In Sweden, we can write dates as 28/5-25


As another swede, I dare you!

We swedes use standardized ISO 8601 dates such as YYYY-MM-DD as dictated by our excellent government and you find it in use in our social security number, government correspondence and mostly everywhere.


> YYYY-MM-DD as dictated by our excellent government

Same here in germany! ...Which is the reason why everyone ignores it in favour of the traditional format.

I love democracy, and also mountain-shaped temporal unit ordering ^ It's 28.05.2025 13:15.

Text-ordering by date is a nightmare because everything is first grouped by day-of-month, then month, then year! :)


So dates have endianness?


And Americans use Middlianness. Middle-endianness?


great, now i've just wandered off wondering if there's psychology studies on the affect of one's endianness on their mental health. like, does one's parent object not show enough affection towards the middle-endian child objects vs their big-endian child objects, or will the little-endian child objects always win affection?


I guess some people just want to see the world burn.


Even more fun when that includes date or time ranges; I've literally had to paste Swedish-style dates into Claude to help me parse what the intended reading is.


Being able to does not mean that you should


-20.6


Not 28/5 '25?


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

Search: