[Auxiliary] How revenue should be share? How to handle bus factor of single satellite-operator?

Product Discussions
,
1

Howdy everyone,

Recently, community satellite become a mildly interesting topic, reading the comments, there are several concerns about multiple aspects of it, prominently:

  1. How revenue should be split between SNO and SATO (satellite-operator, yes, it’s a new word)?
  2. How to deal with bus factor of single satellite-operator?

How revenue should be split between SNO and SATO?

First, imagine you are a SNO, how much of the revenue (in percentage) that you deserve to have?

Then, imagine you are a SATO, how much of the revenue that you deserve to have?

Go back and forth a few times and vote. Let’s be fair and honest as much as possible :).

Percentage of revenue community satellite-operator deserve to have?

  • 0
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
0 voters

And also, because at this moment, there are no SATO yet, the number here only indicate how the community feel it should be.

How to deal with bus factor of single satellite-operator?

This concern is super valid, I have a random idea, if you have one please share your below.

We could have a something like a memberlist of SATO to ping/hangout and a mechanism in case of emergency.

It could be as simple as this: click a button every month, if one cannot be contact/ping, a vault then can be open that contain secret information of their satellites. That could give customer enough time to move their data somewhere else.

Whom cake satellite-operator are eating?

Haven’t seen any comment about this, but this is one of my uncomfortable concern.

I’m no good samaritan. But, I understand the important of keeping storj source code well maintain and implementing innovative idea. Just gonna leave it at that.

Let us discuss.

2

change vote to private

3

I’d like to suggest keeping the Satellite Operator name and not inventing a new acronym. We already have a lot of confusion with the SNO acronym—many Storage Node Operators (SNO, persona) and sometimes even Storjlings incorrectly use it when referring specifically to the node (software and hardware) rather than the persona.

4

There are plenty of single-proprietor businesses. If the person gets hit by a bus… the business folds… just like with any other company run by one person. The way you deal with it is by managing customer expectations: and those expectations are managed with pricing. People, and businesses, die every day.

Before even considering overall profitability: the satellite operator needs to be keeping 50% of gross revenue: no more than half goes to SNOs. Even then… with (likely) few customers and high fixed expenses they’d be lucky to make any money.