You are viewing a single comment's thread from:

RE: Bandwidth Limit Exceeded? How Witnesses Help You.

in #witness-category7 years ago

yep. but you have to agree, the control of dev in steem is too tight, and it shuts out potential free labor, and there is no rep or rewards to incentivise.

there is big issues baked into the architecture. some were for sure intentional, but most were just fad following like lemmings.

i am just doing a reboot. I was trying to show people how the errors have benefited the worst kind of people, and they are defending the indefensible. time to move on.

Sort:  

Steem is open source. No one stops you from developing for it and fixing bugs. You could probably earn quite a bit from the community too.

There are issues in every architecture, that is how it works, nothing is perfect there are tradeoffs everywhere.

Your critique sounds like you have no idea how Software development looks like. I'm happy to be proven wrong but your arguments are not really convincing.

It really sounds like 'all are evil and plotting xy or following the masters' and that is a heavy claim without any backup facts.

Naivete seems pretty foolish in this part of the software development space.

Anyway, as I develop my thesis I am realising that the main mistake, one made by almost every crypto project except, afaik, dash, is no direct mechanism to fund development. This mistake explains almost all the underhanded and indirect ways seeking to fund.

Would you support a hard fork for steemit to get a fixed percentage of new tokens to fund operations? It would solve a lot of problems...

sometimes you start with the wrong answers to the right questions. It in no way invalidates the query.

Yes, there is a block against me submitting bug reports. I posted it here. It was valid and my fix would work. I am banned, because I am making them look bad. Such simple bugs that cause me so much work in workarounds and I am not the only one.

also, just to explain their justification, it was because no ability to reduce vote weight is very prejudicial against newbies. Plus, they accepted to conserve the self vote on posts with a changed default. But my request to allow a reasonable minimum of say 25% min instead of 100% was a "feature request" when it is in scope as ux and onboarding problem. a proper issue.

I forgot to just point out, that a simple fork, like golos is to steem, does enable the elimination of issues like voting prisoner's dilemmas, but I am more concerned about the mingling of the data types within the same graph database, there is a big problem:

https://neo4j.com/blog/dark-side-neo4j-worst-practices/

Another common mistake I see is using Neo4j as a Binary Large Object (BLOB) store. You might have heard that we do support byte type properties, and we do support arrays of primitives so byte arrays are possible. This, of course, opens up the possibility of storing gigabytes of data in a property value

Binary or not, large blobs of UTF-8 still has this same problem. Steem, keeping the forum data with the rest, in a graph database, leads eventually to an unsustainable load on the indexes and IMHO is already happening.

Never mind the fact that it is

  • written in c++
  • uses boost, which seems to change api more often than babies need nappies
  • uses a graph structured database on simple linear tables that rarely use more than two tables, or would be, were they stored as tables.

The designers of blockchains are pretty much ignorant to database theory, and graph databases are for complex data with many lateral relationships.

This is about as far away as you can get from a double entry ledger. There is no sane reason to use graphs. It would be pretty neat for generating searches for full text of posts. But that isn't. Google is steem's outsourced full ext search. and it is useless...

Coin Marketplace

STEEM 0.26
TRX 0.20
JST 0.038
BTC 96560.41
ETH 3644.15
USDT 1.00
SBD 3.81