Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Maintaining a web browser is an intensely cost and time prohibitive endeavor, especially nowadays. The FOSS community can maintain a lot of things but the sheer scale of Firefox, the need for expertise, the necessary labor, it just can't be done by volunteers and donations, at least not without using Chromium. They have to get a cash infusion from somewhere.
I don't like it anymore than you do but ultimately the issue isn't Mozilla, it's the state of the technology market. Silicon Valley is no place for a non-profit organization right now, no matter how much we need it.
What we need is regulations and anti-trust, but even that may not truly save us.
They need money. That's it. That's the long and short of it.
What's stopping web standards from being made simple or unchanging enough for a smaller project to maintain a functional web browser?
At this point the web is about as complex as an operating system in terms of complexity. That needs really strong specific standards in order for it to work, and in turn projects like web browsers are huge and complex.
If someone wanted to build a web browser that only followed the simpler parts of the specifications, it wouldn't work for many websites* and people would not use that browser.
*Whether or not sites need to be so complex is another question entirely, but the reality right now is that they are
Occasionally when I do web stuff I look into the big frameworks but quickly get overwhelmed and go back to simple html/css/js, so yeah I kind of just don't get what the point is or why anyone needs or wants complexity there. Large websites always do most stuff serverside anyway it seems, so where is this complexity even getting used? It is very mysterious to me. Suspect Google etc. are pushing stuff no one needs in this regard as well to move the web towards something only they can handle.
There's a very large number of DOM and browser APIs now though... Even with basic JS without libraries or frameworks, you can still build fancy 2D and 3D graphics (WebGL), interact with USB devices, allow input via game controllers, stream H264 video, implement custom caching, use push notifications, and a bunch of other things. The web browser has to implement all of that complexity. They're all useful in different scenarios.
That's a good point, I guess I haven't been too aware of all that stuff.