13 ms·
In the spirit of transparency, I wanted to share some of the high-level decisions that went into Marqt.org. I am happy to go into further detail or discuss any
by arthurhur 3y ago
In the spirit of transparency, I wanted to share some of the high-level decisions that went into Marqt.org. I am happy to go into further detail or discuss any other aspects that I left out. Just prepare to roll your eyes at how basic I am (I know you're smarter than me, and I'm okay with that).
First, the way marqts are scored. It is an average of all the marqs (0 to 100% true) users have made, but a marqt needs to meet a minimum of twelve votes (arbitrarily chosen because there are twelve jurors in a jury) before it calculates solely off user votes. Before reaching twelve, the empty slots are set to neutral (50%), so if you make a marqt and marq it 100% true, the marqt will reflect that it is "54% true with 1 vote."
Second, the way marqts are sorted. They are sorted by most recent marqts made today (resets every day by UTC time), then by marqts with the most volume, favoring more recent marqts when the volume is the same. There is also a feedback marqt that is inserted in between today's marqts and the highest volume marqts in the sixth item, after the first marqt-maker. You are allowed to make up to ten marqts per day.
Remarqs are sorted so the most remarqable remarq is first, followed by the most remarqable opposing remarq, so that the best argument for each side floats to the top. After remarqability, it goes by things like volume, date and whether it is an opinionated or neutral remarq. The auto-generated remarqs are from Open AI's gpt-3.5-turbo model (with default settings), and the prompt is: Give me the best reason why the following statement might be {true/false} without repeating it back to me: """{statement}""".
On user privacy. The last time around, it was pointed out that I was exposing user information, which I patched immediately. I have added further protections, so that when you have an account, your marqs are not linked to your real name. But, if you add a remarq, it will display your real name (which is conversely not linked to your username). Your email address should be completely hidden and inaccessible via the API. As for anonymous accounts, I hash the public IP address through SHA-256 and bencrypt to create an anonymous user (so something like 127.0.0.1 could become @anon_YmNyeXB0X3NoYTI1NiQkMmIkMTIkSUhIVm5YRjNPeGUxQkdtd2ZIeEFyT1F3Y05DaDV4Q2hMUjI1RHBRT21LLkJOZlZPbHB6cjY=) whose first/last name is set to "Anonymous User." This is my attempt to prevent unlimited voting, although I am aware that it is not perfect (neither is email address, for that matter).
The site is still MVP-ish, but it should hopefully do everything I mentioned so far. I have an ambitious product roadmap ahead, but please let me know if you have any suggestions or criticisms. All the updates I listed above were solely derived from your feedback and not preplanned, so it's highly likely that if you have an issue that is compelling enough, I will prioritize that over other features.