HN user

kataklasm

378 karma
Posts6
Comments180
View on HN

The practical implementation of IP? Sure, that's debatable. But the concept of IP is rooted in favoring progress. The thought process being, that if one's intellectual work can be copied and reused and modified and what not without issues, why should anyone invent things anymore? Just wait for the next person to do it and then copy their work, that's way less effort than inventing things yourself. IP aims to protect progress by making sure inventors have actual incentive to invent stuff. They way it's implemented is fundamentalst flawed, I agree, but the concept itself? I'm not so clear on that

One major issue with transportation in the Martian environment is the extremely abrasive dust and the sharp rocks. Pretty much every rover has had the issue that the wheels deteriorate very quickly and dust gets into every nook and cranny, eventuelly destroying important movement-related mechanisms. As to their movement speed, that's mostly down to the movement being manually commanded and with the light delay of about 20 mins (one-way), you can only command the rover to go so far before involuntarily hitting an object.

Can't say that's entirely true for me ('02). If my [ employer, supervisor, ... ] provides me with logical, traceable tasks with their context properly laid out, I can totally put a ton of effort into providing meticulous, well thought out solutions, that are as good as it gets under the provided constraints. It's the non-sensical (be it actually non-sensical or just not understood enough because of unprovided context) tasks that make me not care.

The German metro area "Rheinland" has a population of 8.7 million people across 12 thousand square kilometers. ~700/sqkm vs the 240/sqkm population density of Atlanta metro. Train and metro travel in this metrk area is extremely convenient and fast. It's not that Atlanta (or anywhere else in the United States for that matter) couldn't do it because of vastness, there's just no political and societal will behind this idea. In a society that glamorizes everyone driving the biggest trucks and carrying the largest rifles, of course convenient train systems are "not feasible".

When have we given up on expecting journalists to do their jobs and write articles worthy of being read and containing actual information? If I wanted to read blubberish I'd go read some AI slop but if an article is written by a human I have some base expectation of it providing a modicum of value to me. Even more so if it reaches the HN frontpage.

edit: removed my own snark. sorry for that.

That's the kind if short-sighted view that's the root issue in a ton of enshittification happening around: the belief that short-term gains or benefits are all it's about. It's not sustainable to leech off of wikipedia content to fuel your own (ad in Google's) knowledge pop-ups, even if it benefits the user in that they save a single click, because that means long-term wikipedia will die out because users no longer associate the knowledge gained with wikipedia but with Google even though they had nothing to do with it apart from "stealing it".

To expand on this, as stated in your source:

[270B solar masses] is the maximum mass of a black hole that models predict, at least for luminous accreting SMBHs.

as well as:

The limit is only 5×10^10 M [50B solar masses] for black holes with typical properties, but can reach 2.7×10^11 M [270B solar masses] at maximal prograde spin (a = 1).

However in the chapter before, it's stated:

New discoveries suggest that many black holes, dubbed 'stupendously large', may exceed 100 billion or even 1 trillion M.

In a similar vein, I really liked "Robot" by Adam Wiśniewski-Snerg, first published in 1973. It doesn't really mention AI itself, but it is about the relationship between humans and artificial life/intelligence. The central theme is the question of knowing if you're "real" in an artificial world. Not the easiest read and can be quite dark at times, but one of my favorite works of classical science fiction. Very underrated!

Yes, they are. Starship has proven multiple novel engineering approaches and technologies. Examples: 1. catching the booster in the air to save on landing gear weight and complexity 2. firing 33 engines simultaneously in a tight cluster 3. the only large scale production and use of CH4-fuelled engines (all other CH4 engines have only been fired a handful of times at most)

Darktable 5.0.0 2 years ago

I'm using Collections in darktable to achieve this. Have you tried it? Although I don't distinguish on an event basis I sort everything into folders by month.

  -2024
   --jan
   --feb
   ...
   --nov
   --dec
  -2025
   --jan

albeit files are slightly overly compressed I agree, pretty sure the host upload is at fault here.

What light source did you use A simple LED strip light, you know those flexible ones. They were glued on the inside (just the bottom panel) of an aluminium box 30x40x8cm and then a frosted acrylic panel was placed on top. While the light color is not that important I chose a neutral white. But I reference each scan images white balance from a reference image of the light table so it gets compensated anyway. Worked like a charm when I still shot analog. Gone digital now unfortunately as the costs just rose too quickly as a college student. Still miss my Fuji GX680 sometimes, but I'm also really happy with my Fuji X-Pro 2.

Yea this is definitely a setup issue. Everything looks soft in his DSLR scans, probably an issue with the depth of field. I used to DSLR-scan 6x8 medium format and while it was a major PITA the results were phenomenal [1,2]. With stitching and a high enough magnification you can easily pull up to 800 Megapixels or more out of medium format frames. Without a 1:1 magnification (while the lens was able to magnify 1:1, my setup wasn't able to accomodate the focus distance adequately so I was more in the ballpark of 1:1.8 or 1:2) I was able to stitch frames into 300+ Megapixel images with about 16 or 20 individual images making up the mosaic.

The key to great DSLR scanning is a proper, high-quality light table (I built my own) and a high quality macro lens (high quality != expensive). Adobe Lightroom always worked best for stitching, Adobe Photoshop and others had some issues for some reason. Cleaning dust off as much as possible before taking the mosaic images is vital to reduce post-processing time.

If you've got a good workflow and don't have to scan hundreds of frames a week it's a great process that's a great deal cheaper, gives better results than even drumscanning if done properly and can be faster than having a lab scan it for you.

Here's an example of a 6x8 DSLR scan. Taken with a 20MP Sony DSLR with 60mm (90mm FF equiv) macro lens by Tamron. Downsampled to 13MP image resolution from the 300+MP scan mosaic because that original mosaic file was about half a gigabyte in size. 1: https://bear-images.sfo2.cdn.digitaloceanspaces.com/marius-1...

Here's one taken as a single frame with the Sony DSLR without any stitching. 2: https://bear-images.sfo2.cdn.digitaloceanspaces.com/marius-1...

Have you seen the domains Microsoft uses? Half the time I am not sure if they are genuine or not, it's actually crazy. Sometimes they use .com, other times .ms. Sometimes Microsoft is in the top-level other times it's in the second-level. Sometimes they have no subdomain, sometimes they have two. It's utterly inconsistent and it's insane to me how close some of them look to actual phishing domains...