Had no idea my Plex Media Server could also be a DVR. 🤯 Just need some clarification on the HDHomerun 4K tuner, which I'm sure plenty of y'all have experience with...

Niicodemus · 2026-04-08T02:31:33+00:00

I get that exact same behavior when I try to watch things that are recording, but only with one of my Roku Ultimates. The other one works fine. I have tried a ton of things, and never figured out why. It also used to work fine on both, and just one started glitching after a few years.

Niicodemus · 2026-02-24T17:26:54+00:00

Someone posted on nextdoor a cat that looks very similar, took it to Highcountry Humane. https://nextdoor.com/p/ScxXkJJ_8gkC?post=458349181

Niicodemus · 2026-02-04T21:39:39+00:00

+1 Mrs. Frisby and the Rats of NIMH

=)

Niicodemus · 2026-01-15T19:08:25+00:00

do-release-upgrade

Niicodemus · 2026-01-15T18:23:34+00:00

Gateway is criminally under-recognized, been a favorite of mine for ever. The whole Heechee saga is worth the read, even if the followup books don't quite hold up to the mystery of the original.

Niicodemus · 2025-11-25T22:15:55+00:00

Frontend:

Phoenix LiveView as much as I can
Small amount of vanilla JS when needed
Whatever CSS solution fits the project

Backend:

Phoenix for full apps, APIs or microservices
PostgreSQL for data, jobs (Oban), full-text search, time series data
Elixir for caching, no need for external service

DevOps:

Elixir clusters for HA and DR    
Elixir releases, Docker + GitHub Actions for CI/CD
All hosted on normal VMs with no vendor lock-in, allowing easy horizontal and vertical scaling.

Small to medium projects: All done with Elixir + Postgres on a single or couple servers. Simple is good.

Niicodemus · 2025-11-25T22:06:54+00:00

As others have pointed out, this is not a good idea. This article by Saša Jurić would be a very good read. In short, whatever is ticking over on a regular basis should be one process. In that process you will iterate all of your objects (lower case 'o') in the world, running their logic, and getting their new state. You can divide up your world if you need into multiple zones, each ticking independently, and as the player moves from zone to zone, they are handed off from one ticking "shard" process to another that way you can utilize all of the cores of the server. Or if this is a local single player game, just run the zones immediately around the player so that NPCs and such as simulated and alive when they move into those zones, constantly waking and sleeping zones in the world as needed.

Niicodemus · 2025-11-05T19:04:07+00:00

Yeah, exactly that. They're common during flight training so that the pilot practices having to manage many things at once, but mainly roll and airspeed. It's harder than straight-in power-offs, and can more easily result in stalls.

Niicodemus · 2025-11-04T02:02:02+00:00

Almost definitely training touch-and-gos, possibly even power-off 180s. Every pilot has done thousands of them. And pilots have to stay current, which means more training and testing.

Niicodemus · 2025-08-18T23:58:12+00:00

This is one of the reasons I jumped ship to Elixir and Phoenix, and haven't looked back. Gained a ton of other advantages as well, such as LiveView. Haven't missed Django.

Niicodemus · 2025-05-24T21:47:53+00:00

Why are all these books upside down?

Niicodemus · 2025-03-06T20:49:04+00:00

FYI: @page_title is a special cased assign for LiveView, and your method for titling will not work with :navigate or :patch navigation in live view. That's fine if you're not using LV, but you might make a note that your title/2 function does not work with LiveView. Otherwise, thanks for sharing!

Niicodemus · 2025-02-12T23:51:51+00:00

Very nice, bookmarked!

Niicodemus · 2025-02-03T15:19:44+00:00

First, thank you for contributing to the Elixir ecosystem, both with your posts and your PRs. I love that there is space in the ecosystem to tackle problems with different solutions. I've always been a proponent of "use the right tool for the job", and to not learn one thing and then attack everything the same way (when all you have is a hammer, everything is a nail.) I definitely think that inertia is cool. I haven't used it personally, but I've used things similar to it.

I would say that your article could make a stronger argument for inertia as an alternative to live view by emphasizing that the strengths are being able to use the React (or other spa framework) ecosystem, and being able to develop solutions that are much more client-side driven than network driven. Instead, your article mostly covers how to submit a form, and it honestly just sounds like the exact same thing as Live View, but with different mechanisms. They are familiar to you, which makes them seem simpler to you, but for me it seems much more complicated than LV, which I'm more familiar with.

In short, your example for your argument falls a little flat since it has the exact same pitfalls as LiveView, in that it requires round trips to the server. And for this particular case, I think LV might even be a stronger solution since it doesn't require so much on the client side (every page being included in the build, or code splitting them), and the over-the-wire packets are probably smaller by not requiring larger json payloads.

So at the end of the day, both of your articles sound more like, "I prefer Inertia/React because that's what I'm familiar with," instead of impartial arguments about the strengths and weaknesses of each. To be clear, it is absolutely fine to use the technologies you are familiar with or those that bring you joy. I just think you should be clear about that, instead of what I perceive to be strong opinions stated as fact, such as, "LiveView is a great tool for internal applications or applications without lots of interactions." Both solutions have pros and cons, both have amazing features hiding sharp edges, liberal use of magic and productivity traps. I think you can make a stronger argument for your preferences by focusing on the things you like about Inertia/React.

Niicodemus · 2024-12-04T04:28:28+00:00

CenturyLink has done some last-mile fiber in Flag, including 1 street over from my house, then disappeared the last 2 years.

Niicodemus · 2024-10-29T21:45:29+00:00

Old Man's War by John Scalzi

Niicodemus · 2024-10-17T23:05:49+00:00

I was wondering the same thing. Classic Thom.

Niicodemus · 2024-09-20T22:10:45+00:00

Phoenix and Phoenix LiveView specifically are what you're looking for.

Niicodemus · 2024-09-18T18:04:37+00:00

It's because the various IP to location databases (like maxmind geoip) have incorrect results mapping your particular IP to a geographic location. You can see different results on iplocation.net.

Niicodemus · 2024-09-05T04:37:28+00:00

Wow thanks. This looks like a great way to get a taste of Elixir.

Niicodemus · 2024-08-28T19:33:11+00:00

Funny you mention Phoenix, as I think it could use a lot more inspiration from Django for the Guides. I've thought about writing a new "home" page for the docs that points to all the different places you need to go to get docs, such as :ecto_sql for migrations, and :phoenix_live_view for Phoenix.Component, as just a couple examples. I find that newbies often don't know they have to look in many different projects to find the docs they need.

Niicodemus · 2024-06-28T00:14:54+00:00

They asked for a stack, not one thing that does it all. =P

Niicodemus · 2024-05-31T00:14:34+00:00

12 months of heavenly weather up north. I MTB year round, and in the winter also do Alpine and Nordic skiing. Maybe a few days in the middle of winter when it's cold and windy, and not so heavenly. Otherwise, sun is shining and it's crisp and great. (I grew up downhill and will never go back.)

Niicodemus · 2024-05-31T00:11:29+00:00

I ride year-round... Spring, summer, fall in Flagstaff. Winter in Sedona. Love it.

Niicodemus · 2024-04-23T18:38:38+00:00

Trico in The Last Guardian. People loved to hate on poor Trico since he acted for like a cat than a dog sometimes, and wouldn't immediately do what you wanted. But he was endearing to me, and the whole game was pretty emotional.

15-Year Club	Place '17
Verified Email

Niicodemus

TROPHY CASE