rDrama/files/routes/votes.py

194 lines
6.4 KiB
Python
Raw Normal View History

2021-10-15 14:08:27 +00:00
from files.helpers.wrappers import *
from files.helpers.get import *
2022-01-19 09:07:16 +00:00
from files.helpers.const import *
2021-10-15 14:08:27 +00:00
from files.classes import *
from flask import *
2021-10-20 23:17:53 +00:00
from files.__main__ import app, limiter, cache
2021-10-15 14:08:27 +00:00
2022-07-02 06:51:19 +00:00
@app.get("/votes/<link>")
@admin_level_required(PERMS['VOTES_VISIBLE'])
def vote_info_get(v, link):
2021-10-15 14:08:27 +00:00
try:
2022-09-05 22:52:22 +00:00
if "p_" in link: thing = get_post(int(link.split("p_")[1]), v=v)
elif "c_" in link: thing = get_comment(int(link.split("c_")[1]), v=v)
2021-10-15 14:08:27 +00:00
else: abort(400)
except: abort(400)
2022-03-31 14:25:49 +00:00
if thing.ghost and v.id != AEVANN_ID: abort(403)
2021-10-15 14:08:27 +00:00
2022-01-21 20:56:56 +00:00
if isinstance(thing, Submission):
2022-01-06 16:46:09 +00:00
if thing.author.shadowbanned and not (v and v.admin_level):
2022-01-13 23:29:15 +00:00
thing_id = g.db.query(Submission.id).filter_by(upvotes=thing.upvotes, downvotes=thing.downvotes).order_by(Submission.id).first()[0]
2022-01-06 16:46:09 +00:00
else: thing_id = thing.id
2022-02-16 01:16:01 +00:00
ups = g.db.query(Vote).filter_by(submission_id=thing_id, vote_type=1).order_by(Vote.created_utc).all()
2021-10-15 14:08:27 +00:00
2022-02-16 01:16:01 +00:00
downs = g.db.query(Vote).filter_by(submission_id=thing_id, vote_type=-1).order_by(Vote.created_utc).all()
2021-10-15 14:08:27 +00:00
elif isinstance(thing, Comment):
2022-01-06 16:46:09 +00:00
if thing.author.shadowbanned and not (v and v.admin_level):
2022-01-13 23:29:15 +00:00
thing_id = g.db.query(Comment.id).filter_by(upvotes=thing.upvotes, downvotes=thing.downvotes).order_by(Comment.id).first()[0]
2022-01-06 16:46:09 +00:00
else: thing_id = thing.id
2022-02-16 01:16:01 +00:00
ups = g.db.query(CommentVote).filter_by(comment_id=thing_id, vote_type=1).order_by(CommentVote.created_utc).all()
2021-10-15 14:08:27 +00:00
2022-02-16 01:16:01 +00:00
downs = g.db.query(CommentVote).filter_by(comment_id=thing_id, vote_type=-1 ).order_by(CommentVote.created_utc).all()
2021-10-15 14:08:27 +00:00
else: abort(400)
2022-01-14 12:04:34 +00:00
return render_template("votes.html",
2022-09-04 23:15:37 +00:00
v=v,
thing=thing,
ups=ups,
downs=downs)
2021-10-15 14:08:27 +00:00
@app.post("/vote/post/<post_id>/<new>")
@limiter.limit("5/second;60/minute;1000/hour;2000/day")
2022-07-13 18:14:37 +00:00
@limiter.limit("5/second;60/minute;1000/hour;2000/day", key_func=lambda:f'{SITE}-{session.get("lo_user")}')
2022-04-20 19:25:19 +00:00
@is_not_permabanned
2022-08-11 04:05:23 +00:00
def vote_post(post_id, new, v):
2021-10-15 14:08:27 +00:00
2022-07-08 16:21:13 +00:00
if new == "-1" and DISABLE_DOWNVOTES: return {"error": "forbidden."}, 403
2021-11-16 01:49:49 +00:00
2021-10-15 14:08:27 +00:00
if new not in ["-1", "0", "1"]: abort(400)
2022-07-12 19:23:37 +00:00
if request.headers.get("Authorization") and v.id != BBBB_ID: abort(403)
2021-10-15 14:08:27 +00:00
new = int(new)
post = get_post(post_id)
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
coin_delta = 1
if v.id == post.author.id:
coin_delta = 0
coin_mult = 1
g.db.flush()
existing = g.db.query(Vote).filter_by(user_id=v.id, submission_id=post.id).one_or_none()
if DOUBLE_XP_ENABLED > 0:
if not existing and int(time.time()) > DOUBLE_XP_ENABLED:
coin_mult = 2
elif existing and existing.created_utc > DOUBLE_XP_ENABLED:
coin_mult = 2
2021-10-15 14:08:27 +00:00
if existing and existing.vote_type == new: return "", 204
if existing:
if existing.vote_type == 0 and new != 0:
post.author.coins += coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
post.author.truecoins += coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(post.author)
existing.vote_type = new
g.db.add(existing)
elif existing.vote_type != 0 and new == 0:
post.author.coins -= coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
post.author.truecoins -= coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(post.author)
g.db.delete(existing)
else:
existing.vote_type = new
g.db.add(existing)
elif new != 0:
post.author.coins += coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
post.author.truecoins += coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(post.author)
2022-03-19 12:52:36 +00:00
2022-03-21 00:40:15 +00:00
if new == 1 and (v.agendaposter or v.shadowbanned or (v.is_banned and not v.unban_utc) or (v.profile_url.startswith('/e/') and not v.customtitle and v.namecolor == DEFAULT_COLOR)): real = False
2022-03-19 12:52:36 +00:00
else: real = True
2021-10-15 14:08:27 +00:00
vote = Vote(user_id=v.id,
vote_type=new,
submission_id=post_id,
2021-11-30 14:18:16 +00:00
app_id=v.client.application.id if v.client else None,
real = real
2021-10-15 14:08:27 +00:00
)
g.db.add(vote)
2021-10-21 20:50:00 +00:00
g.db.flush()
post.upvotes = g.db.query(Vote).filter_by(submission_id=post.id, vote_type=1).count()
post.downvotes = g.db.query(Vote).filter_by(submission_id=post.id, vote_type=-1).count()
post.realupvotes = g.db.query(Vote).filter_by(submission_id=post.id, real=True).count()
if post.author.progressivestack \
2022-08-23 22:00:15 +00:00
or post.sub in ('space','istory','dinos') \
or post.domain.endswith('.win'):
post.realupvotes *= 2
2022-02-16 01:42:11 +00:00
g.db.add(post)
2021-10-15 14:08:27 +00:00
return "", 204
@app.post("/vote/comment/<comment_id>/<new>")
@limiter.limit("5/second;60/minute;1000/hour;2000/day")
2022-07-13 18:14:37 +00:00
@limiter.limit("5/second;60/minute;1000/hour;2000/day", key_func=lambda:f'{SITE}-{session.get("lo_user")}')
2022-04-20 19:25:19 +00:00
@is_not_permabanned
2022-08-11 04:05:23 +00:00
def vote_comment(comment_id, new, v):
2021-10-15 14:08:27 +00:00
2022-07-08 16:21:13 +00:00
if new == "-1" and DISABLE_DOWNVOTES: return {"error": "forbidden."}, 403
2021-11-16 01:49:49 +00:00
2021-10-15 14:08:27 +00:00
if new not in ["-1", "0", "1"]: abort(400)
2022-07-12 19:23:37 +00:00
if request.headers.get("Authorization") and v.id != BBBB_ID: abort(403)
2021-10-15 14:08:27 +00:00
new = int(new)
comment = get_comment(comment_id)
2021-12-23 15:37:12 +00:00
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
coin_delta = 1
if v.id == comment.author_id:
coin_delta = 0
coin_mult = 1
2022-09-01 19:05:37 +00:00
g.db.commit()
existing = g.db.query(CommentVote).filter_by(user_id=v.id, comment_id=comment.id).one_or_none()
if DOUBLE_XP_ENABLED > 0:
if not existing and int(time.time()) > DOUBLE_XP_ENABLED:
coin_mult = 2
elif existing and existing.created_utc > DOUBLE_XP_ENABLED:
coin_mult = 2
2021-10-15 14:08:27 +00:00
if existing and existing.vote_type == new: return "", 204
if existing:
if existing.vote_type == 0 and new != 0:
comment.author.coins += coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
comment.author.truecoins += coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(comment.author)
existing.vote_type = new
g.db.add(existing)
elif existing.vote_type != 0 and new == 0:
comment.author.coins -= coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
comment.author.truecoins -= coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(comment.author)
g.db.delete(existing)
else:
existing.vote_type = new
g.db.add(existing)
elif new != 0:
comment.author.coins += coin_delta * coin_mult
Fix comment self-upvote removal UI bug. (#236) Fixes minor UI bug when removing self-upvote on a comment. Previous behavior, starting from a new comment: - Initial state: score 1 from self-upvote, upvote button shows highlighted as `color: var(--primary)`. - Click on upvote button to remove self-upvote → button unhighlights, score displays as 0. - [reload page] - Score displays as 0, but button is highlighted. - Click on upvote button → button unhighlights, score displays as -1. [If you reload the page now, state is score 0 & highlighted; no change in serverside votes.] - Click on upvote again → button highlights, score displays as 0. - [reload page] - Score displays as 1, button is highlighted. Direct cause is `templates/comments.html @ L115-117`. I checked `api_comment`, though, and it adds a vote on new comments, and that state change propagates to the template's parameters before it renders, so I believe the only time this triggers is specifically when a user has removed their self-upvote. Bug is fixed when testing with L115-117 removed. Is there some other edge case it was meant to solve? Secondary bugfix: Removing a self-upvote _costs_ you a coin & a truescore point. I think this is one of the few ways to get negative dramacoin. I chose to fix it by having self-votes and self-unvotes not change coins/truecoins. The alternative of having new comments & posts give the user +1 coin/truecoin would modify site behavior, and you'd retroactively owe some powerusers thousands of DC & truescore.
2022-05-02 18:12:28 +00:00
comment.author.truecoins += coin_delta
2021-10-15 14:08:27 +00:00
g.db.add(comment.author)
2022-03-19 12:52:36 +00:00
2022-03-21 00:40:15 +00:00
if new == 1 and (v.agendaposter or v.shadowbanned or (v.is_banned and not v.unban_utc) or (v.profile_url.startswith('/e/') and not v.customtitle and v.namecolor == DEFAULT_COLOR)): real = False
2022-03-19 12:52:36 +00:00
else: real = True
2021-10-15 14:08:27 +00:00
vote = CommentVote(user_id=v.id,
vote_type=new,
comment_id=comment_id,
2021-11-30 14:18:16 +00:00
app_id=v.client.application.id if v.client else None,
real=real
2021-10-15 14:08:27 +00:00
)
g.db.add(vote)
2022-08-26 14:57:14 +00:00
g.db.commit()
comment.upvotes = g.db.query(CommentVote).filter_by(comment_id=comment.id, vote_type=1).count()
comment.downvotes = g.db.query(CommentVote).filter_by(comment_id=comment.id, vote_type=-1).count()
comment.realupvotes = g.db.query(CommentVote).filter_by(comment_id=comment.id, real=True).count()
2022-02-16 01:42:11 +00:00
if comment.author.progressivestack: comment.realupvotes *= 2
g.db.add(comment)
return "", 204