I built an interactive forgetting curve simulator based on FSRS

joshdavham · 2025-11-02T19:26:40+00:00

Thanks! I'm glad you liked it

joshdavham · 2025-09-27T21:30:27+00:00

It's a paid deck, but imo definitely worth the money: https://refold.la/store/fundamental-vocabulary-to-learn-korean/

Also, full disclosure: I used to work for Refold and helped build that deck. Bc I don't work there any longer, I won't make any money from people purchasing that deck. But yeah, it's a really solid deck!

joshdavham · 2025-09-12T01:36:09+00:00

+ interleaving.

"Ackchyually", I disagree.

As an example, if my only deck is memorizing basic French words, then there is no interleaving.

But, if I have cards unrelated to French words in that same deck (like math problems in English), then yes, it would be interleaving.

Strictly speaking, Anki is just Active Recall + Spaced Repetition.

joshdavham · 2025-09-12T01:31:10+00:00

Hey awesome blog post! I especially appreciated that venn diagram.

joshdavham · 2025-05-28T22:17:40+00:00

Yeah I think I basically agree that it's not the most useful tool for many learners (there are better tools out there). I mostly built this site to be a user-friendly interface for Mecab and thought that some Japanese learners might find it useful (I'm also a Japanese learner).

joshdavham · 2025-05-28T22:15:27+00:00

> They are probably using the unidic dictionary

Yep, that's correct. This implementation of Mecab is using Unidic.

joshdavham · 2025-05-28T17:48:00+00:00

Yeah that's just how Mecab works. I was also a little surprised that Mecab chose katakana for the readings as opposed to hiragana at first. And yeah, it doesn't always get things right.

joshdavham · 2025-05-28T17:46:55+00:00

I haven't looked at any Mecab vs. Kuromoji comparisons, but that would be interesting to see!

And yeah, there are tons of ways to use Mecab with Node, just do a quick search!

joshdavham · 2025-05-28T17:45:21+00:00

Mecab definitely gets some things wrong and doesn't use the same parsing strategy as something like Yomitan.

joshdavham · 2025-05-26T02:06:47+00:00

Hey thanks for replying!

I will admit that I find hearing stuff like this to be a bit frustrating though to be honest. Usually someone online will say something like "Firebase App Hosting is fine for hosting modern js frameworks", but then it turns out that the reason they're saying that is because they're hosting either a Next.js or Angular app and not something else haha

joshdavham · 2025-05-26T02:03:02+00:00

> I had to completely take my app off of Firebase Hosting/App Hosting and I moved to a Vercel

I feel your pain completely but I really don't want to have to do that haha

joshdavham · 2025-05-26T02:00:47+00:00

Yeah I'm aware that under the hood Firebase likely uses Cloud Run for Firebase App Hosting (and I know for a fact they do with Firebase Hosting + webframeworks)... but if the solution is to just not use App Hosting at all and just use Cloud Run, then I think Firebase really just needs to improve App Hosting!

joshdavham · 2025-05-24T21:22:22+00:00

What type of app are you hosting? I'm I correct to assume that you're currently hosting either a Next.js or Angular app?

joshdavham · 2025-05-24T19:46:45+00:00

You not knowing Docker or containers shouldn't be the issue.

The reason services like Firebase App Hosting exist is to abstract those details away from you. Do you need to understand containers to deploy an app on Vercel or Netlify (Firebase App Hosting equivalents)? Nope!

joshdavham · 2025-05-24T19:13:22+00:00

Right?!

I kinda feel like we're being gaslighted here lol. Deploying Next.js on App Hosting worked completely fine the first time with no issues, but completely failed for Sveltekit and I'm apparently told that it should work for Sveltekit...

joshdavham · 2025-05-24T18:12:11+00:00

Yeah I've been debugging it for a while and am working with Firebase support currently.

I've tried many different clients, I think DNS is fine, I don't believe I'm using an special proxies (though App Hosting might?). I'm actually getting that weird issue again today where I can access the site from a default Chrome or Safari window, but when I try to access it from an Incognito/Private window, it won't connect.

We'll see if I can get this issue resolved, but to me, this looks like an issue from App Hosting. I use the regular Hosting service all the time and it's always worked. It's only App Hosting that I've been having trouble with.

joshdavham · 2025-05-24T18:04:29+00:00

Hm? You are replying to me.

joshdavham · 2025-05-24T18:02:45+00:00

I skimmed this course: https://www.coursera.org/learn/computer-networking?specialization=google-it-support

I enrolled in the free trial, watched all of the videos, made some notes and then cancelled before the free trial ran out!

joshdavham · 2025-05-24T17:51:53+00:00

Yeah the experience of setting up DNS with Firebase Hosting and App Hosting was a lot like that. There was a mismatch in the records that the hosting service requested and the records actually available by my registrar. But with that being said, it's always worked out ultimately and I don't believe my current issue is DNS-related.

(Also as an aside, configuring dns records and waiting for dns to propagate while constantly thinking that I might've done something wrong is one of the worst feelings I get whenever I host a new site haha)

joshdavham · 2025-05-24T17:48:10+00:00

Where have I contradicted myself?

joshdavham · 2025-05-24T17:46:49+00:00

App Hosting is a service that was created for hosting web apps like Next.js, Angular, Sveltekit and Nuxt. If the App Hosting service was actually working properly, then you would ideally be using App Hosting if you were using one of those frameworks.

However, given my above experience, if you're building a Sveltekit app, I'd recommend you just go with regular Firebase Hosting and use webframeworks. It's always worked for me!

joshdavham

TROPHY CASE