3 ms·
> run a forked codebase on isolated servers[...] It's not forked at all, when you use the business version of Facebook you can even URL hack public Facebook UR
by avar 9y ago
> run a forked codebase on isolated servers[...]
It's not forked at all, when you use the business version of Facebook you can even URL hack public Facebook URLs to share the same global IDs to your "private" instance, and you might even see public comments from public Facebook users.
It's also possible to invite public Facebook accounts to your groups in your business instance, to them they're just browsing another group on Facebook.com.
So the Facebook Business instances really aren't separated out at all more than just being the equivalent of an aggregation on private groups on facebook.com + custom domain etc.
Edit: I just tested this by taking a random post of Zuckerberg's and replacing www. in the URL with <mycompany>. and sure enough, Zuck then shows up on our "internal" Facebook, albeit with a notice saying it's a public post. You can then "share" the post and get the same behavior as on public Facebook when you share an existing group post to another group or message.
- pbalau 9y agoSo, you are saying one can share links on Workplace? I can see some uses for this feature...
- avar 9y agoYes it's useful. Not saying it's bad if they've got their ACLs right. It's just an interesting leaky abstraction showing that it's little more than a whitelabel for Facebook.com.
- afro88 9y agoIt can still be a forked codebase and do all of what you say. What you’re outlining is that it’s not isolated from public Facebook infrastructure.
- avar 9y agoIndeed. My comment only shows that, but as a follow-up it's also clearly not a forked codebase. Facebook UI changes show up at the exact same time, and as a practical matter they must be syncing regularly if both access the same underlying storage.