Ndymium
Joined 11 years ago
Karma
1,523
Submissions
386
Member since
Nov 19
Web developer @ Tampere, Finland
View on Hacker NewsRecent submissions
Comment · 10 days ago
This article is a bit old, LVV has already ordered Google to stop construction until the YVA processes are done. What is still unclear is if Google will face any repercussions for acting before the YVA was done, but it is looking unlikely.
Edit: One source in English but even this is a while ago: https://www.bbc.com/news/articles/cvj6jkx6g1r0o
Comment · 19 days ago
Which court stopped construction? I have not read that courts are involved at all yet, only that Finnish Supervisory Agency (Lupa- ja valvontavirasto LVV) has ordered Google to stop construction. I found a source [0] claiming that some areas that are important for biodiversity were first spared and then cut down, but this does not mean that they were old growth and the Muhos county official Mikko Kari states "[The areas] are not legally mandated to be protected."
Now, I'm not a fan of Google and I'd much prefer this whole project was scrapped, which is why I'm interested if there are sources that provide something that I've missed from the Finnish media.
[0] https://suomenluonto.fi/uutiset/luonnon-monimuotoisuudelle-t...
Comment · 20 days ago
What's the source for this? I haven't seen claims of cutting down old growth forest.
Comment · 21 days ago
From the Ministry of Agriculture and Forestry[0]:
> More than 75% of Finland’s land area is covered with forest. [...] About 3 million hectares of Finnish forests are protected or under restricted use, which represents 13% of the total surface area of forests (forest land and low-productive forests). The area of protected forests fully excluded from fellings is 2.5 million hectares, which represents 10.8% of the total surface area of forest and low-productive forest land.
Comment · 24 days ago
I still call it the Apple key ("omppu" in Finnish, colloquial form of "omena") even though the symbol hasn't matched for a long time. I use it when thinking about shortcuts as well, like a screenshot being shift-omppu-4.
Comment · 27 days ago
I just recently went through my whole library with Picard and it worked well while the UI was definitely geared for power users. Really happy with the end result.
There was one UX papercut that ended up messing some data on tracks that I had to correct later: fields with multiple values, like "Artists", show the multiple values like "Beats and Styles; Toni W.". But the field in the UI is also editable as a text field, and if you manually write that with the semicolon, it stores one artist with the semicolon included! It took me a while to realise that I can right click to open an editor where multiple values can be entered and edited separately.
Comment · 1 month ago
A classic way of getting endless money in Transport Tycoon was to build a tunnel going from one edge of the map to another. The money counter would overflow and you'd get enough money to last you a lifetime.
As kids we didn't know why this would happen, we just knew that it did and used it every game.
Comment · 3 months ago
In my case it's my Forgejo instance. My blog is static files with a limited amount of pages to crawl and indeed it's no issue at all. Forgejo is a dynamic service with an infinite amount of pages to discover and it runs git in the background to generate (some of) the pages. Tons of bots can easily overwhelm my small server. I could hide the repositories, but they're open on purpose (it's open source after all).
I have it guarded by a simple cookie check now, which seems to work well enough. Only a small subset of bots pass it. It likely kills search engine discoverability, but that's the tradeoff I have to make.
Comment · 4 months ago
If my user does jog at 2 AM, then it's better to show 2 AM than 7 PM or 10 AM even if there is a slight chance that on one singular day 2 AM might repeat itself. The user who is aware of how daylight savings works will surely be able to figure that out.
Technically you might argue that I should show 1 AM if the user did run at 2 AM in summer time, but everyone I personally know keeps their schedule over DST transitions. That is, if they did something at X o'clock before the transition, they'll keep doing it at X o'clock after it (sleep be damned). So generally showing 2 AM would be the most correct solution.
You cannot get that information from just UTC if you don't know where the user was when they made those historical events. Thus you either have to keep a history of their location (complicated) or just store the local timestamps (or at least the offsets) at the time of event. Always being able to convert from UTC with no extra data assumes that the user will never move, which might be fine if your application is limited to users in a single country.
Comment · 4 months ago
Copying what I posted under the original[0] that no one noticed because it's quite relevant to your mention of UTC for past events:
The naming of "timestamp with time zone" is one of my favorite pet peeves. It's one of those things that you can say "well technically it's true" about.
The article suggests that for past events, UTC and this timestamptz would be acceptable as a general rule, but even there it depends on what you will be doing with the data. If you intend to interpret it as a series of local occurrences and try to visualize/summarize that data later, you may be in for a surprise as your user has moved to another timezone and now all the past events are translated to the wrong local hours [1]. For example, your system might end up showing that the user's best time for jogging based on historical data is at 2 in the night.
Comment · 4 months ago
The naming of "timestamp with time zone" is one of my favorite pet peeves. It's one of those things that you can say "well technically it's true" about.
The article suggests that for past events, UTC and this timestamptz would be acceptable as a general rule, but even there it depends on what you will be doing with the data. If you intend to interpret it as a series of local occurrences and try to visualize/summarize that data later, you may be in for a surprise as your user has moved to another timezone and now all the past events are translated to the wrong local hours [0]. For example, your system might end up showing that the user's best time for jogging based on historical data is at 2 in the night.
Comment · 4 months ago
This is what it looks like right now. Unless there's some huge economic boom coming, which I doubt.
Comment · 4 months ago
As a Finnish dev with 12 years of experience, I can only aspire for such salary.
Comment · 5 months ago
It's a game. You're supposed to click on the different route options that are presented to you on the bottom of the screen. That's why it goes slower the more options there are.
But I also just followed it for the first time from beginning to end, not doing anything. Because I assumed someone had already done the math.
Comment · 8 months ago
While 7700 per hour sounds big, pretty much any dinky server can handle it. So I don't think it's a matter of DDoS. At this point it's just... odd behaviour.