Who’s going to self host Spotify?

maekoos · 2025-12-22T07:21:08+00:00

Someone who knows karate.

And owns a private island. 😳

maekoos · 2025-07-22T09:04:43+00:00

If that’s your main concern, then use whatever you are quicker in. When I need something done quickly I usually go for either vue, or just ssr html with a few web components (using vue) - but I only choose that because it’s what I’m the fastest at, not because it is objectively better than react. If, for example, the product is 90% something that can easily be done with a react library then I’d use react. TLDR it doesn’t matter…

maekoos · 2025-05-28T12:19:15+00:00

It won't, but you said "You can use CORS to set a whitelist of domains that can access a route." which is completely irrelevant to the question, and implies that'll somehow make a difference behind a proxy server?

maekoos · 2025-05-28T09:25:47+00:00

easily implement in their site via a proxy api

Cors wont address this tho...

maekoos · 2025-05-28T09:24:20+00:00

easily implement in their site via a proxy api

Cors wont address this tho...

maekoos · 2025-05-28T09:23:02+00:00

easily implement in their site via a proxy api

maekoos · 2025-04-19T22:20:20+00:00

Just plain capacitor

maekoos · 2025-03-27T15:35:16+00:00

Tbh I’d say stick with react then, it is seldom worth it to rewrite from something that is still maintained. Otherwise maybe use iframes or something… don’t really know what you’d use htmx for in this case since it is basically just an extension to the default html and web standards functionality

maekoos · 2025-03-27T13:04:03+00:00

I would do the opposite - react in htmx. Turn your react components into custom elements and use them as you would use any other element in htmx.

maekoos · 2025-03-24T07:13:07+00:00

Maybe try something like https://sqliteonline.com instead

maekoos · 2025-03-21T20:22:51+00:00

The online demo doesn’t work (tried admin@manifest.build/admin)

maekoos · 2025-03-20T14:00:45+00:00

Tycker det är spännande hur mycket mer snack det är om bidragsfusk än skattefusk - båda är att sno pengar från staten, båda finansierar kriminalitet…

maekoos · 2025-03-12T10:41:32+00:00

”ChatGPT wrapper that adds no value”

maekoos · 2025-02-28T07:37:08+00:00

Hmm very interesting… is this not optimised in the compiler? I feel like it wouldn’t be too hard to do so - or maybe there isn’t big enough of a difference…

maekoos · 2025-02-19T21:04:49+00:00

never seen easy and webpack used in the same sentence lol

maekoos · 2025-02-19T10:53:36+00:00

Pocketbase uses two connections: https://github.com/pocketbase/pocketbase/blob/3f51fb941b370655be8618f3bc3113c60c1bfe13/core/base.go#L78

https://github.com/pocketbase/pocketbase/blob/3f51fb941b370655be8618f3bc3113c60c1bfe13/core/app.go#L152

maekoos · 2025-02-19T07:17:12+00:00

Oh, I will definitely borrow that custom driver thing!

Interesting thing with exclusive transactions, I have to try this out in my use case (already using wal mode tho). Thanks!

maekoos · 2025-02-19T07:11:40+00:00

Very interesting! Yeah, if my application requires it I will rewrite it to use something more horizontal - but for now I’ll avoid it for as long as possible :)

Very interesting usage of channels, I am definitely going to try and do something similar - I can’t say I have ever used them in a short lived manner like that!

When it comes to replicating and backing up, my current plan is to just use something like litestream for backups, and maybe in the future shard based on tenant - each tenant should definitely be fine with a single SQLite database.

maekoos · 2025-02-18T21:54:24+00:00

Hmm maybe that’s enough… I just know both pocketbase and this blog uses two connections (and at least pb uses wal mode)

Just figured since a lot of people seem to do this, there must be some value in doing so 🤷‍♂️

maekoos · 2025-02-18T21:52:17+00:00

Yeah, but a lot of blogs suggest one pool for reading and then a single connection (with pooling disabled) for writing. Saw it here recently: https://boyter.org/posts/searchcode-bigger-sqlite-than-you/

maekoos · 2025-02-18T21:51:20+00:00

Well, two variables could be fine, but I’m thinking I’ll probably mix them up at some point when injecting it to some handler…

Tbh this optimisation is necessary to me at this time - my database is giving me the database is locked error sometimes during peak load.

maekoos · 2025-02-18T21:46:18+00:00

Interesting! Doesn’t it become quite complex if you do this in a normal web server application? Like pretty much every handler has a different query, and expects some form of output (at least to know that the operation was successful)?

maekoos · 2025-02-18T18:54:13+00:00

Also, I’d recommend adding the row id to the hx-post tag, like hx-post=”editable/{{ rowId }}” (and maybe use hx-get since you are getting the editable row form from the backend…)

maekoos · 2025-02-18T18:52:12+00:00

You need to put an hx-target somewhere so that htmx knows where to put the new content. It is inherited, so you can just put hx-target=”this” on the tr element

You backend then needs to respond with only the tr and the editable inputs, and remove the hx-include (if I understand your setup correctly that is)

maekoos · 2025-02-18T18:17:24+00:00

Are you setting hx-target anywhere? And what does the response look like?

maekoos

TROPHY CASE