majora2007

I actually like the idea of this, but with some restrictions (and wouldn't mind seeing it in the US). Yes, I know the costs are passed thru to consumers.

Here's my thinking:

1. Limit who is charged based on how much bandwidth they consume / month. If it's over 1TB, the tax goes into affect. This helps small businesses.

2. If (1) can't work, we can do it based on income from French users above X / month.

3. Tax income must go towards infrastructure projects: Parks & Recs, Fiber buildouts, etc.

Even before all the AI, his videos started lacking substance and were just high level showcases.

I'm in the same boat, I just switched to using it for Kavita, which only does some basic open Image -> Thumbnail to smaller size -> write to disk when importing new comics/books and on linux, memory could swell to 10GB and never get released. Switched to jemalloc and instantly memory stayed well below 1GB.

Outside of the outstanding optimizations .net has made (plus async runtime), what I really enjoyed was the reworked entry section. Stephen reiterated all the concepts from the past Performance Improvement articles to really showcase the layers of optimization techniques and how the can transform.

How is the AI controlling the video game? Is there special coding/harness that allows for this?

One thing that really interests me is declining to issue CVEs. I get a lot of AI submitted security issues and they all want CVEs. But some are simple idor to access information around an age rating on selfhosted software for friends and family.

Does anyone have any advice when to decline CVEs?

Kavita has a custom epub library that actually streams the epub pages. The reason why it's non-existent is due to epub being a zip, with a manifest of pages and images. Each page is an html document, so it may have images requested from that manifest.

Most applications just use epub.js which needs the whole book loaded at once.

Edit: Also Kavita does support some calibre tags for metadata and def is much more customizable with a powerful filtering system which you can then bind to your dashboard/side nav.

www.kavitareader.com for those that might be interested (or check the wiki to get a bit more about it).

Why not use Kavita then? It uses even less resources, it's mature (nearly 5 years old) and supports manga/comics/ebooks with a rich ecosystem of apps (esp with AI now, lots of users are creating mobile apps to connect).

I totally agree with this. I recently tried vibecoding a side project that I used to code a few days a year on and it was really fun at first.

But then I started to feel overwhelmed by the amount of code and the fact that coding manually started to come harder.

I ended up just cancelling my sub and going back to the old ways. Side projects are fine to take extra time as they are my hobby for me.

You might want to check out Kavita, the epub reader is quite good.

Surprised Kavita didn't make your list. Has KOReader/Send to Support out of the box and is extremely mature (5 years old) and feature rich.

Sad to see Kavita (or any OS self-hosted reading server) not on openaltfinder :(

I just released a pretty solid annotation system for Kavita's EPUB reader. It wasn't super challenging (although Kavita has a custom epub renderer).

Now doing that with PDF would actually make it challenging.

Annotation system (with pics): https://wiki.kavitareader.com/guides/readers/epub/#annotatio...

Because if there are valid ones, they may impact users... It's important to do due diligence (but this takes time to validate them).

Well these are well written security vulnerabilities with reproduction steps. It's hard to tell if it's an AI discovering or a user using AI to find issues. But suddenly, I'm having an influx of issues where-as for the past 5 years, I received maybe 5. Just this month, I've been hit with 5 low effort vulnerabilities (all very small, unlikely to expose anything of value).

But it's very hard to maintain these in addition to the release work.

I don't get what you're saying. You're frustrated that Open Source projects were used to build these AIs and that OS devs (or devs in general) are paying to use AI.

Then you say you had money that you used to donate(?) to OS and have cut that because of the frustration?

Open source just means sharing the source code for people to learn off or have the ability to customize on their own. I don't think there is any need to be frustrated about that (now if it was copyright/private of course).

Just an FYI, your site text is not readable. It's a white fade background with white text.

What does "fast" even mean? I always see people talk about performance and wonder, what kind of applications are they building where they are seeing a massive gap in performance between frameworks?

I'm pretty sure in this late game, all the frameworks are more-or-less the same in terms of render performance. Angular has a lot of cool tricks (with these signals) that allow for only re-rending what changes.

Signals are a privative data structure in Angular, hence core. Signal-based forms are part of the Forms module. You aren't using forms, you don't get the overhead.

Really excited for this. I've been dying to use signal-forms and resources since they were experimental. Once I got on the signal train, I could never go back and having to use RxJS for forms became a major pain point.

What is rough in the ecosystem? I haven't had any issues finding packages. Most packages have been keeping up with the signal trends as well.

Thanks for sharing, these are awesome ways to explore your data.

One thing that is so painful with Stripe is the Disputes because no matter how much evidence I show, even emails with the user claiming they did it because of X, Y, Z. ToS not upheld, etc, the customer always wins.

For me, I do a cheap subscription (4$/mon, first month 2$) and one dispute costs me like 20-30$. So that one person wipes a ton of profit from me. I always try to refund them (but you can't refund a customer with a dispute in effect).

Stripe is great to get going, but has a lot of painful points.

What's interesting to me is that it seems a lot of people got burned by AngularJs (Angular 1) and now swear off Angular as a whole.

Like many, I came from pre-SPA days -> AngularJs -> Angular 2 -> Modern Angular. I tried react a few times, plus React Native but found it hard. I wasn't good with a slightly different render-syntax (whereas Angular uses HTML) and every project I was on was wildly different from each other.

Modern Angular has been wonderful. A lot of the pain points people have are gone, some good parts of other frameworks (signals, single-components vs modules, etc) have been incorporated and embraced.

Steep price, but honestly makes a lot of sense. Lifetime licenses are never sustainable when you own a lot of infrastructure. Plex owns the auth, the reverse proxy infrastructure (to make it dead simple to setup), and a ton of development overhead and backend licensing deals.

They obviously want to shift people to a monthly plan, but still give that lifetime. If I were to buy today vs when I originally, it would still be cost effective.

There are alternatives, so users that don't want to shell up the 150$ now can jump over to. It's closed source software and the users have the opportunity to shift (or build a competing software that meets more of their core needs).

There are some really nice enhancements in here. My favorites are obv the async runtime switching from state machine and some of the JIT Optimizations. It's always impressive how much squeeze the .NET team can get out of the framework.

Kavita (note: I'm the developer), FMD2, qBittorrent, VLC, Firefox

Plex is aimed for a simple ease-of-use experience, so if you aren't technical enough to setup a reverse proxy, Plex offers all the authentication and proxying for you.

It's not a true self-hosted software. It just depends on what matters most to you.

I just want to throw out that you might like Kavita for a comic/book server. It's built to feel like Plex. https://www.kavitareader.com/

I do agree that Plex doesn't seem like a good fit for books and comics. The first major hurdle is the lack of a singular metadata source that Plex can hook into for metadata - although this year has shifted with Hardcover and MangaBaka. Plex also uses a filename parsing mechanism (like Kavita does) which has drawbacks since books and comics have an extremely wide variety of naming conventions and lack of good tooling.

idk about a house party once a week, but I do like the idea of having my friends invite their other friends. As I age, it becomes harder to find new friends just by happenstance. Friends of Friends usually end up becoming friends after meeting them.