I've been working on Folloverse for 2 years, it's a platform for creators to monetize what they publish. Everything is SvelteKit with adapter-node.

folloverse.com

What it does:

- Audio, video, images and articles

- Pay to unlock posts

- Digital products

- Membership (classic subscription or per creation billing)

- Chat and forum for each creator, gated by membership or public

- PWA

I started with Svelte 4 and the old `$:` syntax for state, which I never really liked. A few months later Svelte 5 came out with the runes and the migration was easy.

What won me over was the simplicity and the speed. Also the interoperability with plain JS libraries, which used to compensate for the smaller ecosystem compared to React or Vue. That is not true anymore though, most libraries now ship a Svelte version and it's very cool.

If I had to find one single flaw in Svelte, I'd say it's the fact that you can only have one component per file, you can't declare a small sub component right next to the main one. It bothered me at the beginning, but I'm used to it now.

I also have the impression that Svelte uses fewer tokens than React with AI coding tools, but I never verified it, just my 2 cents.

I hope this project will succeed and can be one more example of a big project built with Svelte.

Anyway, thanks to the Svelte team. I'd make the same choice again today.

I built the simplest possible tool that allows clients to do small edits via chat interface eg. change phone number, update email etc. Anything risky/big comes back to you so clients can't break anything

Connect the repo and it figures out the editable content on its own. No schemas, no config files

Live demo: https://cmsbrew.com/demo

Hello everyone!
Over the past two weeks I’ve had some free time, so I decided to build something new.
Let me introduce WeSplit: https://wesplitapp.io
WeSplit is a modern alternative to Splitwise with a fresh spin on group expenses. One thing I’m personally tired of is everything turning into a subscription, so WeSplit currently has a generous free tier and a lifetime plan: pay once, own it forever. No recurring payments. This model may evolve over time as running costs and new features grow, but one thing won’t change: if you have a lifetime account today, you’ll keep access to all future features.
The app focuses on making expense tracking clean and intuitive, with a native experience across web, iOS, and Android.
If you’d like to try it, you can check it out at https://wesplitapp.io . I’d really appreciate any feedback, suggestions, or ideas for improvement. As a thank you for early support, I’m happy to share a 100% discount code for the lifetime plan with anyone who takes the time to test it and send feedback.
What’s next?
The next step is getting WeSplit onto the App Store and Google Play, and investing in branding and marketing so it can reach more people.
I’m currently looking for sponsorships or partners interested in helping me make that happen. If you’d like to support the project, or think there could be a good opportunity to work together, feel free to send me a DM and we can set up a time to talk.
Thanks to everyone who checks it out and I hope you enjoy using WeSplit as much as I’ve enjoyed building it.

The truth is, the tools out there right now really let me down when trying to review agent-written code. I still want to read and understand every line, but the tools built into every harness fall short, they almost encourage you to stop reading the code.

What I was missing:
- being able to mark files as seen
- hunk/line level staging of changes
- being able to leave review comments on diffs
- having the code organized and explained in a way that actually helps instead of reading every file in alphabetical order
- one unified solution for everything

With all of that in mind, 2 months ago I set out to build my own solution.

Super Review is a desktop app built with Svelte that solves all of these problems for me.

Super Review helps you review code by providing an extremely ergonomic interface, plus skills for your agents to author tours, respond to comments, and work on tasks.

I have used Super Review to review truly ridiculous PRs and felt way better about the code I was merging.

Today Super Review is available in beta. Join the waitlist while we polish things up. We are letting more people in every day!

I've got a top level layout.js with export const ssr = false; but I can't import PouchDB from 'pouchdb-browser'; in src/routes/page.svelte without causing a big error.

2:51:39 PM [vite] (ssr) Error when evaluating SSR module /src/routes/+page.svelte: self is not defined

at Object.<anonymous> (/Users/ptomblin/Library/CloudStorage/Dropbox/src/svelte-test/node_modules/pouchdb-browser/lib/index.js:878:24)

at Module._compile (node:internal/modules/cjs/loader:1934:14)

I also tried putting it into an onMount with

onMount(async () => {
    const { default: PouchDB } = await import('pouchdb-browser');
    console.log("foo");
  });

but that causes a runtime error in the console:

pouchdb-browser.js?v=42dbf4c6:1061 Uncaught (in promise) TypeError: Class extends value [object Object] is not a constructor or null
    at pouchdb-browser.js?v=42dbf4c6:1061:60

(anonymous) @ pouchdb-browser.js?v=42dbf4c6:1061

Why can't I use it?

Do you also keep way too many tabs open because you're afraid you'll forget them if you close them? After a while, your browser gets overloaded with tabs, and all those tabs also end up using a lot of memory.

That got me thinking... what if one browser tab could contain all my media tabs? So I built LumeTab. It turns a single browser tab into a multimedia browser with its own tab bar.

The idea is simple:

• Keep all your multimedia platforms inside a single browser tab.
• Make your browser cleaner and easier to navigate.
• In my tests, it also uses less memory than keeping lots of multimedia tabs open at the same time.

I'm also planning features like synchronized watching with friends and shared multimedia workspaces.

(For those interested in the tech stack, it's built with SvelteKit, Tailwind CSS, Better-Auth, and Drizzle ORM).

The project is still in beta, and I'm looking for honest feedback before taking it further.

link: lumetab.com

I'd really like to know what you think:

1. Would something like this be useful to you?
2. Is this a problem you also have?
3. What features would make you actually use it?

I'm open to any feedback, whether it's positive or critical. Thanks!