Actually, i can't decide between option 1 and 2.
There's something i don't uderstand about option 2: we can have an external service running to keep sharing, but has the user any power about "when" it's active?
I mean, i'm fine with both an internal (that would be opt 1, closing when osu is closed) or an external (opt 2, active even if osu is not running) solution, but i really think we should also get some way to monitor and turn this off sometimes.
As many people already stated, lots of users also run osu from places like university (i do that too, sometimes) and in those places any kind of P2P software is not allowed.
The main problem about this argument is that if too many people turn sharing off, we get lots of leechers/peers but no seeds.
So, i'd like to hear some more details before giving an answer >.<
There's something i don't uderstand about option 2: we can have an external service running to keep sharing, but has the user any power about "when" it's active?
I mean, i'm fine with both an internal (that would be opt 1, closing when osu is closed) or an external (opt 2, active even if osu is not running) solution, but i really think we should also get some way to monitor and turn this off sometimes.
As many people already stated, lots of users also run osu from places like university (i do that too, sometimes) and in those places any kind of P2P software is not allowed.
The main problem about this argument is that if too many people turn sharing off, we get lots of leechers/peers but no seeds.
So, i'd like to hear some more details before giving an answer >.<