Axtell

« first day (253 days earlier) ← previous day next day → last day (381 days later) »

1:00 AM

@Mego I dunno what's happening so far with avatars but I think we should probably validate that they are valid Imgur image. On the frontend I can modify the upload code so the URL/uploaded image is put on imgur

Anonymous

@Downgoat /preferences/avatar takes an image URL, uploads it to imgur, and sets the imgur URL as the user's avatar. The only thing we need is a raw image upload route

Downgoat

how about I just give the server an imgur image ID and it validates that, and raw image upload can be done on frontend

Anonymous

Because that would expose the imgur API key

Downgoat

how? we can anonymously upload on the frontend so the API key isn't revealed

we're already doing that for image uploads for posts

Anonymous

I guess? I just don't see a compelling reason to change the current setup

Downgoat

3:50 AM

ok I think I got CSRF working

Feeds

4:02 AM

Axtell/Axtell: Add CSRF protection

posted on July 16, 2018 by vihanb

I hope this doesn't wreck the tests Signed-off-by: Vihan contact@vihan.org

Anonymous

Tests wrecked, gg

Downgoat

Q_Q

Anonymous

It will be super easy to fix though

Downgoat

also apparently we weren't using any cryptographically secure random entropy source so I've added M2Crypto

Anonymous

Ok so I thought it would be easy to fix the tests but I forgot about contexts

Anonymous

4:50 AM

CSRF is live

Poke

1:38 PM

@Mego Why is it dumb

5 hours later…

Anonymous

6:33 PM

@Poke Obscuring vote counts will just delay the inevitable, and it takes information away from users

Poke

6:58 PM

@Mego It gives people more time to answer the challenge without having voters swayed by current vote counts

so John Doe may answer 1 minute after the challenge is posted

But Josh Doe can also answer 5 minutes later

and Sarah Doe who goes to vote will not have a biased vote if those answers' vote counts are hidden

I'm not trying to say you're wrong; just trying to get you to explain your rationale more

quartata

I think it could work but they'd have to be hidden for longer than Reddit does it

Of course, that's if you have voting at all...

Poke

So that's a concern. How long do you hide them? We're not going to see as much traffic as Reddit. Is 10 minutes enough? 30? It does start to get a little excessive, perhaps

Oliver

Anyone else getting an Internal Server Error?

Poke

yes

Oliver

Poke

7:04 PM

I think voting is being kept in this project. Internet points hold communities together after all

2 hours later…

Downgoat

8:55 PM

@Oliver aw.. h*ck

oh looks like missing depndency

I guess I should add pip install to deploy

should be back up

Oliver

back up, thanks!

This challenge has a MATL answer in the leaderboard, but I'm not seeing it

Downgoat

oh, it was deleted, I still need to fix it

1 hour later…

Downgoat

10:03 PM

So the site that we use for the changelog it costs like $15 for some 'Pro' features but those are only blocked by a <div> that prevents you from clicking on the 'Pro' features >_<

*$50/mo

1 hour later…

Anonymous

11:24 PM

@Downgoat You know what to do :P

Anonymous

11:36 PM

@Poke FGITW is caused partially by the fact that, at any given time, the oldest answer has had a larger window in which it can receive votes than other answers. The only way to attempt to solve that is to restrict the voting window by waiting some predetermined period of time after the challenge is posted to open voting, which would still leave answers posted after that window at a disadvantage.

Anonymous

The other issue is that views on a challenge drop off significantly with time, so newer answers get less eyes, and therefore less votes. There is no simple way to solve that problem.

Anonymous

yesterday, by Mego

FGITW is a difficult problem that will not be solved by simple solutions

quartata

@Downgoat I refuse to believe people are this bad

Anonymous

@quartata Until recently, my company's software had a nag screen for expired subscriptions that worked exactly like that.

Downgoat

11:52 PM

I suppose we could curb the points awarded in some way to avoid FGITW

« first day (253 days earlier) ← previous day next day → last day (381 days later) »

all rooms