I'm a Byteball dev and a service provider for the byteball platform and I'm still going to call it byteball because I never agreed with Obyte as it's an inconvenient name to pronounce and it looks weird. If you were going to change the name then at least do it right, or are you planning on doing this every year now so you don't need to put much effort into it? Makes me wonder. Anyway, the management has taken a step to the worse in multiple fronts so I'm not even mad. Dropping slack for an inferior service, changing the name into a worse one, having all these moon lambo bois like tarmo888 making dumb comments like "scaling can only come AFTER adoption". I'm glad the price is pumping with those pump and dump news though, because I am increasingly seeking for an exit from this project. It had all the potential in the world but is now screwed due to the uneducated but vocal moon lambo bois who joined the project with the last rally (2017/2018).
One of us)
My opinion is that the project was initially overvalued, including by me. But as time moved, the flaws began to show up as acne on the skin of a teen. After all it doesn't scale because tonych do not know how to scale it
Lol @ "Byteball dev". Couple of PRs and commits on Github doesn't make you a Obyte developer. You have just made some chatbots that hardly use any Obyte core functionality. You could easily port them to FB Messenger, are you going to call yourself FB Messenger developer then?
Slack was inferior service for Obyte because you don't understand the problems that the team had with Slack. Your solution to turn Obyte Slack into payed community is not a solution for a platform, which wants to be open for everybody, so Discord is better for that. Also, Slack was hell to moderate, Discord has better options for that because it is aimed to communities like that. Only things Discord is inferior to Slack: threaded comments and quoting.
I never said "scaling can only come AFTER adoption", what I said was that there is no point to focus on scaling when there is no need for scaling yet. Year ago Obyte could do 15TPS, now it can do already 30TPS on average (peaks can go even into hundreds or thousands), but the need for TPS is still below 1TPS. It is not only my opinion, it's opinion of others too, that's why it's not a main focus. I am just focal about it. Obyte already scales better than Bitcoin and Ethereum on base layer.
Tony knows how to scale it, it just not the main focus. Some steps for scaling has already been done with improving the SQL queries. Obyte core is not memory heavy or CPU heavy, it's heavy on the disk, so there are plenty of opportunities to scale from there (different databases have been tested). Eventually the whole ocore could be rewritten with C++ or some other low-level language (Node.js was chosen only to iterate faster in the beginning). And then there is layer-2, which Obyte haven't even touched yet.
I consider Hyena a lambo boi, you are the one who is looking at the exit sign, I don't plan to exit nor buy any lambos. I just don't like people shit-talking without actually helping the project any way.