You are viewing a single comment's thread from:

RE: 0000000000001001 - Steemit Interface PoC - Black & White / Yin & Yang

in Steemit Dev Group3 years ago

I think the idea of a whitelist is quite excellent, though I'll throw in that it will be a lot of work to maintain.
As you say, good buddies can quickly become bad busddies and new users need to have a chance to get on the list. No code can do that, it's manual work, isn't it?
Furthermore, the criteria for being on or off the list have to be worked out as objectively as possible and made transparent. Otherwise, there will be a lot of shouting and in the end, the "decision-maker" will get everything. Haha, I guess I know that your fur is thicker than mine... ;-)

this platform needs a blacklist

Indeed!

I'm very tempted to make the financial element of Steemit less prominent

I'll give you a smooch if you manage to do that!

I am still convinced that you have to separate the pure DiFi and the pure interest in it, from the (rewarded) blogging business. Since this doesn't happen because it's not wanted or there is no idea to implement it, your frontend as a sympathetic filter bubble could be a great first step. Then it's up to the writing user to decide whether to get involved or still stare full of envy and greed at the abusers.

Thanks for all your efforts!!!

Sort:  

I think the idea of a whitelist is quite excellent, though I'll throw in that it will be a lot of work to maintain.

In time, it could become automated - similar to the anti-plagiarism game. People already whitelisted could nominate new people to join and if approved, there could be a link between the 2 users so if there's any naughtiness (via the anti-plagiarism game) in the future, the nominator is also "penalised". Lots of threads of thoughts swirling around my head at the moment of how it could work 🤔

the "decision-maker" will get everything

💪🏼

My thinking is certainly that the new front-end eventually becomes as pure as possible. If people want to abuse the system via UpVu or TipU, then they can. But they won't be doing it on my front-end. This would have the double-bonus that in time, my front-end is recognised as its own entity, built upon Steemit as a Blogging platform and crypto currency but sharing the good - getting a good reputation from search engines and ultimately, boosting the profile of Steemit. Hopefully onboarding many new users that never need to know about the shadier side of what happens here.


The progress I've made feels good. There's a long, long way to go but the direction feels positive and I'm already using my front-end to digest content and linking of to Steemit.com to reply to it 🙂

Sounds great!
I am already looking forward to beastly!

Ahso - will I be invited? ... 😂

will I be invited? ... 😂

It's hard to know... hopefully somebody will nominate you 🤣

I call in for a community-run DAO of sorts to get in I guess. We have several trusted and highly respected community members out here already. We create an on-chain voting mechanism(Or off-chain) that determines if a person gets in or not. I can get that system in place once you're closer to the launch @coding-gorilla.

👍🏼 Only for the trusted members 🙂

I wanted to ask you about your club5050 chart - how hard would it be to create a separate page which takes a username, starttimestamp and endtimestamp in a query string and returned the chart image. So I can embed it in a report.

E.g. <img src="starlordsclub5050magic.html?username=cheatingbastard&starttime=1643673601&endtime=1646092799" (imagine the close parenthesis here - I couldn't add them for obvious reasons!)

When the response is an image, the payload size increases, and the extra load is put on the server. What I would suggest instead would be to call an API(I've currently not made this open yet) that would return you the data. You could then render a chart on the client-side instead. That takes out a ton of load.