Submitted by dele_ted in konsent

It's been a few days since we got the Konsent beta online. It's helped to diagnose the main issues and shortcomings, which surreal and i are working on now.

A few people have asked what's going to happen next; here's my suggestion:

RIght now, we wait. It'll take some time for us to get everything working (list of stuff we need done for version 0.4b here). When that's all finished, Konsent will be ready for integration into Raddle, if the community still feels like it.

Here's how we'll go about doing that:

  • A separate subraddle will be created for Konsent issues. Every time a new issue is opened, it'll be x-posted to this subraddle (either by a bot or by the community). This is also where most discussion for the issues will happen. (suggested by T_W)

  • Solved issues will be taken into action in one of two ways:
    a) Administrators will carry out the actions that the community agrees to.
    b) A bot will become administrator (either alone or alongside current admins), and will take commands from some sort of Konsent API

  • Subraddles will decide whether they want to use Konsent or not individually. That should probably depend on their size and their nature.

This system still needs some fleshing out, but you get the fundamental idea.



You must log in or register to comment.

An_Old_Big_Tree wrote

This is looking promising. A part of me wishes there was a way to automatically be logged into Konsent when you log into Raddle and have the accounts tied together in the software, but I imagine that's not realistic any time soon.


dele_ted OP wrote

Yeah, it would be really neat if the two could blend better, but without a Raddle API and with only two devs it's not realistic. A Raddle bot controlled by community decisions taken with Konsent is very realistic, though.


An_Old_Big_Tree wrote

Was thinking about making a proposal and it seems it would be a bit complicated to do with konsent at the moment, so I'm thinking that future useful functionality would be able to deal effectively with things like:

  • grouping together decisions.
  • having mulltiple passing solutions

Say a user is offering to set up threadbots for the community. Phase 1 is the offer.

Phase 2, people suggest the sites they want to get a feed from, AND the amount of votes required for any threadbot feed to be created.

Phase 3, each of the suggested sites is voted on, and number of votes (value X) required for each site is voted on.

Phase 4, results show all options voted for above X votes.


dele_ted OP wrote

A link to all suggested solutions will be put in phase 3, and in "Completed Solutions" (or phase 4, whatever you want to call it).

I'm not sure i understand what you mean by "grouping together decisions"?