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

Dynamic og:image generator could be a use case.

Think of the GitHub thumbnails where the PR number changes constantly and has to be reflected on the image preview


> Sounds like a huge liability.

This 100%.

I don't think this is being discussed enough but I frequently see a lot of landlords trying to make their contract more attractive by including an internet offer with the rent (this is especially useful for people that look for 6-months contracts when internet providers usually give you a minimum contract length of a year).

Tenants could technically do any kind of illegal activities by using that network. I've always wondered how and who would be liable in case someone uncovers something big enough to get the attention of law enforcement.

I guess this differs by country but it seems highly plausible that a legal loophole could exist, leaving the landlord unexpectedly responsible for the tenant's actions.


> I guess this differs by country but it seems highly plausible that a legal loophole could exist, leaving the landlord unexpectedly responsible for the tenant's actions.

Not in any normal country.

> who would be liable in case someone uncovers something big enough to get the attention of law enforcement

The person doing the crimes, obviously. The cops would most likely never even contact the landlord, as they’d just show up at the address where the line is connected.


WASM is not needed.

The author explicitly states that he likes to write Go and that’s why he picked it in this example, which in my opinion makes this article more interesting. The main benefit is that the 'local server' within the service worker mimics the 'real server,' which effectively means you only have to write the code once.

But I generally agree that a 10MB download on first load is not something that I’d be happy to serve to users, especially to those who are using their mobile network.


> I was seriously considering starting a compilers YouTube channel even though I’m awkward in front of the camera.

Doesn’t need to be a YT channel, a blog where you talk about this very complex and niche stuff would be awesome for many.


Starting a channel just to stand out and land a first job really puts a spotlight on the sad situation of hiring in this job market. Imagine if you needed to record videos of yourself building and driving a car to land a job as a mechanic.


I was blown away when I discovered that Rust automatically generates enum ordering. I remember I was coding an AoC solution [0] and the tests that I had set up were passing without me actually doing any work, good times! :)

[0]: https://mattrighetti.com/2023/12/07/aoc-day-7


Is the Rust advertisement in the room with us?

I've search for "rust" on the page and all I could find were 3 matches, at the bottom of the page, two of them are part of this quote:

> In Rust, the restrictions on memory use can be too restrictive. Finally, its strategy doesn’t work for all situations, and so it’s common for Rust programs to use reference counting for some of their memory.


ToC of all the 20 articles: https://lwn.net/Articles/276782/

EDIT: hug of death I suspect, in the meantime you can use [0]

[0]: https://web.archive.org/web/20250523172646/https://www.airs....


TIL! What are the advantages of hexagonal spatial indexing compared to e.g. quad trees, r-trees?


The main advantages of hexagons are that the distance to each neighbour is always the same, and the distortion across the globe is much less, because of the way H3 creates its grid (compared to the earlier Google S2 which uses squares and distorts a lot). There’s an excellent Uber blog post about this, I’ll see if I can find the link.


(here’s the blog post: https://www.uber.com/en-GB/blog/h3/ )


One of the big ones that hasn't been mentioned is all of a hexagon's neighbors are equidistant. As a result, h3 is a better fit for flow modeling - stuff like telematics. This has some nice properties for ML too.

You can see one of my jupyter notebooks that dives deep into this with h3 here: https://drive.google.com/file/d/18jIVEbE_1QbwTbHdMqj0AVqguf2...


The main advantage of hexagonal spherical tiling systems is that they are roughly equal area at a given resolution. This makes them particularly suitable for generating visualizable aggregates when you primarily care about spatial distribution rather than specific boundaries (like borders).

The main disadvantage of non-congruent tiling systems like H3 is poor scalability and performance when running analytical computations. In most cases you wouldn't want to shard your underlying data this way even if this is how you want to visualize it.

It is easy to get the best of both worlds. You can shard data models as 3-space spherical embeddings (efficient for large-scale analytic computation) and convert query results to an H3 tiling at wire speed on demand.


It is a common misconception that h3 is equal area. At any resolution level the cell size varies by a factor of 2, which is (roughly) the same as S2.

See the following visualizations for an illustration:

https://a5geo.org/examples/area

https://a5geo.org/examples/airbnb


Note that I wrote “roughly equal area”. True equal area doesn’t exist. I am on record that for analytical purposes, equal area largely doesn’t matter.


Thought it was the thunderstorm and the clouds but then I saw this :) it’s been down for more than 30m now in Italy


Lately I’ve been working on two things:

An iOS client for Cloudflare. Surprisingly, there’s none out there, maybe because nobody needs it? I do, so I’ve created one and it’s now available on TestFlight [0].

Another interesting thing I’ve recently discovered is that LLMs are pretty great at vetting tenancy agreements, so I’m working on a website that reads tenancy agreements and will return a list of unfair clauses that might be present in the contract along with a detailed explanation of how you should follow up with the landlord/agency. I still need to finish it but if you’re interested it’s here [1].

[0]: https://testflight.apple.com/join/Jj7WveWb

[1]: https://transparents.fyi


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

Search: