|
|
|
|
|
by cxr
1105 days ago
|
|
One problem with Sandstorm is that it didn't have something like miniflare. (Cloudflare didn't either until recently, and that's fixed now, but the value prop was high enough otherwise that this wasn't fatal.) Another is that it lacked (and still does, from what I can see) a killer app. It had the perfect conditions last year with the Twitter acquisition, but to my knowledge didn't seize upon it. (Likewise, Cloudflare had a similar opportunity, but the Wildebeest project comes off as a celebration of Cloudflare's infrastructure for the sake of it and/or aimed at those who love devops stack complexity, generally—a fairly tonedeaf response to what would drive someone to want to run their own fediverse node that's not backed by Mastodon.) The weird URLs—or rather: the constraints that led to them, and the downstream consequences to UX—didn't help. |
|
As far as the killer app, Sandstorm has some really awesome Sandstorm-only apps, but probably not enough yet for our "exclusives" to be a draw to the platform on their own. Sandstorm currently has some limitations that make it difficult to use in federated environments, and we are working on it, but yeah, it meant we didn't have a fantastic story for social during all this Elon stuff.