What would need to happen to make this app work on secure-scuttlebutt? We already see things as a log of meals that we derive stats from, so the jump isn't so far, and the win is we can let everyone use the app without centralising the hosting costs on us.
We've got:
Meals
{
date: isoDate,
chef: [userId],
eaters: [userId],
guests: Integer,
dish: String
}
Eaters
{
name: String,
img: url,
servings: {
given: Integer,
received: Integer
}
mealsCooked: Interger,
lastCooked: isoDate,
lastEaten: isoDate
}
And the stats on an Eater are derived using the meals they were ate or cooked. An Eater is not necesserily a user. Many people can't be bothered to log meals, and you can get a long way with just one user logging all the meals for their group. That said, every participant should be able to.
We'd like to allow mulitple groups to exist. Scores within a group won't affect other groups. This is an interesting decision point, and we can revisit it later, but that's the plan for now.
What would need to happen to make this app work on secure-scuttlebutt? We already see things as a log of meals that we derive stats from, so the jump isn't so far, and the win is we can let everyone use the app without centralising the hosting costs on us.
We've got:
Meals
Eaters
And the stats on an
Eaterare derived using the meals they were ate or cooked. An Eater is not necesserily a user. Many people can't be bothered to log meals, and you can get a long way with just one user logging all the meals for their group. That said, every participant should be able to.We'd like to allow mulitple groups to exist. Scores within a group won't affect other groups. This is an interesting decision point, and we can revisit it later, but that's the plan for now.