Everyone here has been overreacting about the Mozilla layoffs, but they only laid off poeple working on the metaverse, ai, and their VPN and stuff. They're actually refocusing on Firefox.
People have been freaking out about them working on ai now, too, but theyve been doing ai for a while (Mozilla common voice anybody?)(Firefox's translation feature?) And it's always open source, and runs offline, they're not gonna add a shitty internet-connected ai sidebar.
Here is the entire internal memo fore the interested:
--
Scaling back investment mozilla.social: With mozilla.social, we made a big bet in 2023 to build a safer, better social media experience, based on Mastodon and the Fediverse. Our initial approach was based on a belief that Mozilla needed to quickly reach large scale in order to effectively shape the future of social media. It was a noble idea but one we struggled to execute. While we resourced mozilla.social heavily to pursue this ambitious idea, in retrospect a more modest approach would have enabled us to participate in the space with considerably greater agility. The actions we’re taking today will make this strategic correction, working through a much smaller team to participate in the Mastodon ecosystem and more rapidly bring smaller experiments to people that choose to live on the mozilla.social instance.
Protection Experimentation & Identity (PXI): We’re scaling back investment in some of our standalone consumer products in the Security and Privacy space. We are reducing investment in market segments that competitors crowd and where it is challenging to deliver a differentiated offering. Specifically, we plan to reduce our investments in VPN, Relay, and Online Footprint Scrubber. We will maintain investment in products addressing customer needs in growing market segments.
Hubs: Since early 2023, we have experienced a shift in the market for 3D virtual worlds. With the exception of gaming, education, and a handful of niche use cases, demand has moved away from 3D virtual worlds. This is impacting all industry players. Hubs’ user and customer bases are not robust enough to justify continuing to dedicate resources against the headwinds of the unfavorable shift in demand. We will wind down the service and communicate a graceful exit plan to customers.
Right-sizing the People Team
Given the reduction in staffing and lower headcount budget moving forward in MozProd, some roles have been consolidated in the People and other support services orgs so that we are offering the right level of support to our product portfolio. Optimizing our org to sharpen focus.
In 2023, generative AI began rapidly shifting the industry landscape. Mozilla seized an opportunity to bring trustworthy AI into Firefox, largely driven by the Fakespot acquisition and the product integration work that followed. Additionally, finding great content is still a critical use case for the internet. Therefore, as part of the changes today, we will be bringing together Pocket, Content, and the AI/ML teams supporting content with the Firefox Organization. More details on the specific organizational changes will follow shortly. Within MozProd, there are no changes within MDN, Ads, or Fakespot. There are also no changes to Legal/Policy, Finance & Business Operations, Marketing, or Strategy & Operations.
--
all you have to do is
host your own PDS, where your account lives, this is easy, I do it myself already.
host you own appview: the only actually good appview is bsky's, luckily it's open source, unfortunately I do not believe they made it easy to self-host.
Host a relay, this isn't all that hard, it just needs a real big server (AFAIK it needs a shitton of io throughput), so unless you're very rich it's not too realistic to host this.
So yeah, a PDS is easy to host but the other two parts are a pain, and since the protocol has only been open for a few months, people haven't really done too much.
Frontpage exists, but they haven't made it be able to interact with bsky.Social, although the accounts are shared. I have been told by people involved with that that that's an issue with frontpage's implementation, and not the AT protocol