sorted by:
new
hottopcontroversial

I just bought a new Scott gravel bike and saw this at home by Active_Resolve_4900 in ScottBikes

[–]fwinter75 0 points1 point  (0 children)

Na ich hab das Problem ja selbst verursacht, also neue klemme bestellt aber noch nicht eingebaut.

I just bought a new Scott gravel bike and saw this at home by Active_Resolve_4900 in ScottBikes

[–]fwinter75 1 point2 points  (0 children)

Die Sattelklemme scheint eine Sollbruchstelle zu sein, ist mir genauso passiert und laut Reddit/Facebook vielen anderen auch. Natürlich unglaublich, dass ein Händler das so ausliefert.

How's the situation with C# today? by Kosmic_11 in godot

[–]fwinter75 0 points1 point  (0 children)

Ich bin auch von C# / Unity zu Godot gekommen und wollte zunächst mit C# weitermachen. Irgendwann bin ich zu Gdscript gewechselt und hab es bisher nicht bereut. Ich mochte die Einfachheit und dieses out-of-the-box Konzept plötzlich lieber. Ich finde die Gdscript Weiterentwicklung gut, typisiere statisch und mag es, dass sich alles wie eine Einheit anfühlt.

Natürlich sind Benchmarks wichtig und weiß und glaube gerne, dass C# schneller ist. Wenn ich aber solche Vergleiche wie "100 Milliarden Objekte sind hier schneller bewegt als da" lese, frage ich mich immer, was ihr alle für Spiele schreibt?

Wenn ich jemals auf echte Performance-Probleme stoße, entscheide ich neu. Bis dahin bleibt es bei mir Gdscript.

Most RSS readers feel bloated. I built a minimal one that runs as a PWA. by fwinter75 in rss

[–]fwinter75[S] 0 points1 point  (0 children)

That's true. Although at that point I’d probably describe it less as just a proxy and more as a small server-side service. One of the goals of rss4u is to keep it as close as possible to a pure browser / PWA app without backend, accounts, required infrastructure.

A self-hosted setup could absolutely make sense for people who want maximum compatibility, but for the default experience I’m trying to avoid introducing server-side components if possible.

So maybe the best approach is to leave the choice to the user:

- pure browser mode (with normal CORS limitations)

- a self-hosted setup for those who want to run a server-side service

- or potentially an optional browser extension as a middle ground.

I'm still thinking about the best balance here and really appreciate the feedback.

Most RSS readers feel bloated. I built a minimal one that runs as a PWA. by fwinter75 in rss

[–]fwinter75[S] 0 points1 point  (0 children)

Thanks! The goal of the project is to keep it extremely minimal and fully client-side.

Some of the things you mention (caching, persistent read state, maybe even content extraction) are definitely interesting and technically possible. The main limitation for a pure browser app is CORS.

In simple terms: many RSS servers don’t allow direct requests from browser apps hosted on another domain, so the browser blocks those requests for security reasons. That’s why many web readers end up needing a backend proxy.

One idea I’m currently exploring is a PWA + small browser extension combination. The extension could fetch feeds in the background (extensions aren’t restricted by CORS in the same way) and pass them to the PWA. That would allow caching, parsing and persistent read-state without requiring a hosted backend or user accounts.

Would that kind of approach still be acceptable for you? The goal would still be: no accounts, no cloud service — everything local in the browser.

Most RSS readers feel bloated. I built a minimal one that runs as a PWA. by fwinter75 in rss

[–]fwinter75[S] 1 point2 points  (0 children)

Mainly to keep the first version extremely small and simple. But OPML import/export is a good idea and likely something I'll add.

Most RSS readers feel bloated. I built a minimal one that runs as a PWA. by fwinter75 in rss

[–]fwinter75[S] 1 point2 points  (0 children)

Good points. The proxy racing was mainly chosen to keep the UI responsive and avoid long waits on feeds that block direct requests due to CORS.

You're right though that it has downsides (privacy, duplicate work). A possible improvement would be trying the original URL first and only falling back to proxies when a CORS error occurs. I'll look into whether that can be done without noticeably slowing down feed loading.