I helped with the mute function, I filed an issue on github, it now works better. It still has some bugs, by the way, occasionally I still see greyed out posts, but amusingly enough, these people are now not trolling like I saw them doing before, and I unmute them. But when I see a troll now, I can hit the mute button and poof gone.
I am willing to bet that some of these ideas you have hinted at that are on the agenda internally for implementation, are at least partly like the solutions I have proposed, the namespace sub-chain with member assignments, and a chat system that does not depend on a central server. The former could indeed be integrated into the main chain, and the latter, integrated into the witness node code, with a separate file storage that keeps unexpired posts until they are expired, then purges them.
I think that Steem is doing well and adapting solutions quite quickly, and has such a jump on the competition, that by the time these platforms come out, Steem will be very close to RC standard or even in full release.
I will continue to work on building a python/piston based gtk3 interface, because I see no reason why this would not be appreciated, and it can be ported very easily to all platforms. This would help reduce dependency on the central server, and also assist users who have computers that are not up to the performance standards the web interface demands.
Wish we can see who muted us so we can redeem our selfies. With them.
let's do a brief intro call if you're up for it
message me on rocket chat?
I am stuck on a low bandwidth, shaped 4G connection currently. I am always logged in at freenode on #steemit. I am by no means thriving at the moment but I have won enough through my own efforts that I can spend my time coding.
If you want to do an interview with IRC, just pop email me at [email protected] to schedule it (give me the timezone so I know when, I am in Eastern European Standard Time zone, in Bulgaria). I should be able to upgrade my internet connection next week but I am very reluctant to spend another 10 euros on another 10Gb for my internet connection, this is expensive compared to what I can get wired into my room here.
Otherwise, you can follow me, check my hashtags at #ascensionteam and #steemportal where I post articles related to these subjects.
Thankyou for your interest :)
edit I am terrible at names and I didn't realise. You are one of the developers?
He is one of the Steemit F O U N D E R S !!!
He is the CEO of steemit
I just looked a bit closer at my prepaid 4G service and discovered I can get a 5Gb block at the same price as the 10Gb so I am back up and running.
I am now puzzling over how to find @xeroc's piston.web code, realising that he has already built most of the glue between piston and an interface, and this would cut out a lot of work for me, letting me focus on a frontend, and @leprechaun wants to build a wxwidgets frontend as well, but now I don't know where to find piston.web. halp!
I am writing a wx widgets editor that will post to the block chain. Maybe we should join forces.
In python, right?
It would make a lot of sense - we could share code. Bundle it into the same project, and separate the parts, build a generalised interface glue (with a global variable set by each independent main script) and the common classes we can both work on. Or something like that. Where is your git repo?
I am building up the base framework for multiple frontends. I won't be building wxwidgets or qt frontends, I am just going to put stubs in there that others can add to the master branch.
The git is here:
https://github.com/l0k1-smirenski/steemportal
I should have the beginnings of the interface glue started pretty soon. Please do, if you want to, make branches, and then as they develop, they can be merged into the master branch and the app will become more frontend-agnostic, what gets implemented on the front end will be up to people coming in and building them. I realise also that a web frontend could be integrated into this structure, but since #xeroc is building piston.web (which I can't find the code for now) I will leave that alone, but you can see in the code structure how it could be linked together.
Mute button will not effectively sever the tie between a sociopath and a user. It's a good feature some instances, but doesn't solve the main design issue actually. Thanks for your work for the mute button, as that is part of the solution. I am actually bringing this up now before we have something more insidious to deal with. This is a preventative post. I think most are unaware of the potential problem that could really make headline news.
I think you are exaggerating a bit with how serious it is, since the stalkers' activity is by the nature of the platform publicly visible to anyone who hasn't muted them. Finding who they are for legal proceedings is no less difficult, depending on the user's posts, than it is for the stalker to find the victim offline.
The transparency of this platform certainly of its own, introduces privacy problems, but leaves this issue to the user to manage. The transparency also hurts the power of malicious parties too, and with a working mute button, makes these people more vulnerable to being noticed and vigilantes empowered to work on defusing the threat. This is a more cooperative model, and has many other benefits but for the issue of cyberbullying and stalking, makes such activities potentially very dangerous.
Thank you for your work. Followed & upvoted.