Aussie living in the San Francisco Bay Area.
Coding since 1998.
.NET Foundation member. C# fan
https://d.sb/
Mastodon: @[email protected]

  • 4 Posts
  • 1.46K Comments
Joined 2 years ago
cake
Cake day: June 14th, 2023

help-circle

  • It was a feature built in to the web browser, providing a website, file sharing, a music player, a photo sharing tool, chat, a whiteboard, a guestbook, and some other features.

    All you needed to do was open the browser and forward a port, or let UPnP do it (since everyone still had UPnP enabled back then), and you’d get a .operaunite.com subdomain that anyone could access, which would hit the web server built into the browser.

    This was back in 2008ish, when Opera was still good (before it was converted to be Chromium-powered). A lot of people still used independent blogs back then, rather than everything being on social media, so maybe it was ahead of its time a bit.







  • I don’t have any knowledge about this in particular, but as someone with experience working at big tech companies, you’re missing the most likely reason:

    1. Everyone who worked on it was reorged to higher priority teams, and nobody is left to maintain the apps

    A lot of teams are only 3-6 developers, an engineering manager, a project manager, and a designer. Other roles like content design and QA are often shared across lots of teams. Developers with experience building native apps might be needed on other projects.