3 ms·
Yes, people stuck using a corporate browser might have trouble accessing non-corporate websites because of those browser's loses of capability. It sucks. HTTP w
by superkuh 2y ago
Yes, people stuck using a corporate browser might have trouble accessing non-corporate websites because of those browser's loses of capability. It sucks. HTTP webservers are fully capable but realistically every human person should do HTTP+HTTPS for the best of both worlds.
Regardless, for HTTP there's an entire 'year 2000's web' worth of people out there using browsers that can access the non-corporate web. As the corporate web diverges with things like stateful HTTP extensions, UDP HTTP, and CA TLS only implementations (if not spec) there's no need to switch to a niche protocol like Gemini. Just making a normal website on the web is enough to bring back the old small web environment. As a human person not operating under a profit motive and just doing things for kicks this is just fine. A silver lining like how usenet is actually good again now that most people don't get it from their ISP.
- immibis 2y agoCorporate browsers such as (checks notes) Firefox and all of its forks.
- superkuh 2y agoYes, Mozilla is very corporate. These days it's primary design considerations are about executing javascript to buy things or watch DRM media. It's use cases cannot allow for it being a web browser for human persons. It uses cases are all about commerce now. But there are fine Firefox forks that split off before it just became a chrome copy.