We need to be able to export the ed25519 private key from local storage. Let's debate options and add some sort of mechanism to allow the user to export end import said key.

A user reported in Slack that the markdown editor doubles certain words while typing.

Device: Galaxy Note 8
Browser: Chrome, Firefox

Using Chrome:

If I type "decred.o" and then "r", I get "decred.odecred.or"

"google.c" &"o" gives me google.cgoogle.co

Firefox seems to be worse:

Any time I hit space, comma, or period, the entire word just disappears!

The issue is reproducible using the base headzoo/react-markmirror component, but it's not as bad with the JedWatson/react-md-editor component. For JedWatson/react-md-editor:

it seems to delete periods the first time i type them. So "decred." becomes just "decred", but if I type the "." again it stays.

It's redirecting to users/login again after going to the right route creating a "flicker effect". It also happens when a page is refreshed.

Need to port the bootstrap+jquery widget from dcrpayments.

We need better error/success messages. Just from light testing I noticed we need better messages for:

• /user/verify/success
• /user/verify/failure
• /login

There are probably others as well.

Admins can't comment on unvetted proposals anyway, the API is returning a "proposal not found" error.

We need access to the policy object fetched from /api/v1/policy within getHumanReadableError() inside src/helpers.js.

react-markmirror is a very nice Markdown editor, but it's 500kb built.

Ideally we should only load it once the user visits the submission creation page

Here is a proposal creation:

We need key introspection in order to debug this.

Currently there is no indication to the user what is actually wrong with the password.

backend validation: ^[[:alnum:]\.\:\;\,\- \@\+\#]{8,}$

All set errors should be wiped on page transitions; currently if there's an error when submitting a proposal and I navigate to another page and then navigate back, I can see the error from before.

when i attempted to submit a new proposal, i received the near-useless error message "Error creating proposal, Bad response from server". errors should be less vague and include details that allow users to make a meaningful bug report.

by requiring that a sysadmin check the logs or dig further for an error, it decreases the likelihood of the error condition being properly handled.

The admin publish/censor actions are currently only seen when visiting the admin proposal status page. They should be available within the unvetted list too, and still protecting with a JS confirm dialog.

To support censoring a proposal based on its title, the title must be part of the content that is signed by Politeia. The title should be sent in the proposal description (index.md) in the following format:

<title>\n
<description>

The server has to support this first, so this should only be implemented after decred/politeia#115 has been closed.

/proposals/{token}/setstatus to /proposals/{token}/status

Annotate the config file and make sure we mention --proxy on politeiawww.

After logging in, if you refresh the page, it appears logged out. This doesn't appear to be a problem caused by Politeia because the session has a timeout set: https://github.com/decred/politeia/blob/master/politeiawww/www.go#L575

Here's an example of an error message when 500 is returned from the server:

The error message should be displaying the internal error code along with instructions to contact Politeia administrators.

The warning should be some kind of JS confirm dialog.

• When logged in, menu still displays Login instead of Logout
• After first logging in, it should redirect to either the Submit or Home page

After submitting a proposal and navigating to another page, the Submit page should reset and allow the user to submit another.

Clicking the file input to attach files wipes any existing file attachments on the new proposal page. I can only select multiple files if I select them all within the file selector dialog, but I should be able to attach multiple files, one at a time, from multiple accesses of the file selector dialog.

the submit tab is shown when the user is not logged in. this gives the impression that one can submit a proposal without registering with the site, which mismanages user expectations. the submit tab should only appear when users are logged in.

When logged in as an admin, I'm seeing only an Admin menu item. I should instead see Unreviewed and Censored menu items, each of which displays those proposals.

i added a larger image (~628 KB) to a proposal and it printed an error about how the image was too large. this should be prevented up-front if possible, so the user cannot upload an image with size greater than the max size.

For /user/new, /user/password/change and /user/password/reset routes, if the user supply a malformed password (under 8 chars) it doesn't notify them what's wrong. The server is returning: { "errorcode": 13 }

Requires: decred/politeia#146

when proposals are first submitted, they are considered in the 'unvetted' state and must be manually reviewed by someone who checks that a number of basic requirements are satisfied. since proposals that are unvetted or currently in the process of being vetted could contain inflammatory content, we must deprive users of the ability to externally access this data while a proposal is unvetted. this avoids the scenario of pi being used to effectively serve inflammatory content, albeit via an indirect channel.

as part of fixing this, the censorship token lookup widget in the ui would be removed. users who submit proposals that are ultimately censored should be able to independently verify that their proposal was indeed received and not made public with its censorship token alone. by allowing lookups against a censorship token, whoever is hosting the pi instance may end up inadvertently hosting inflammatory content.

Currently we're using <LoadingIcon> for page-to-page transitions, but that's not working well on the proposal detail page. We should create a <PageLoadingIcon> component which is used for page-to-page transitions, and is consistently displayed maybe 200 - 300px from the top of the page. This should be separate from <LoadingIcon> which should be easily embeddable into other components. Similarly, <ButtonWithLoadingIcon> should be refactored to use <LoadingIcon>.

#81

Currently pgui redirects user to their proposal’s permalink after successful submission.

API no longer returns a users unvetted proposals so we will need to add a page that replicates proposal detail with the data from the successfully submitted proposal (should be in the proposal request’s payload and response in state)

the censorship token amounts to a signature from a particular pi instance confirming that a proposal submission has been received. instead of having users lookup their proposal by id or censorship token to check its status, the user should be prompted to download a "proposal bundle", which would contain all the censorship data, along with the file(s) that make up the proposal.

beyond prompting the user to download a proposal bundle, there needs to be a simple tool that users can run to verify a censorship token is valid. this is important not only for the user being censored, but also other users who wish to verify the proposal in question was indeed censored.

There's no error displayed in the UI when the server returns 500 for /vetted and /unvetted routes. The UI is also lacking a "There are no proposals" message when /vetted and /unvetted return no data.

The admin proposal page currently only displays the proposal title and the actions. Actually, this page could be removed and the actions could just be added to the proposal details page if the current user is an admin.

Also - actions should not appear if status == Censored.

The markdown preview area doesn't seem to be working.

Steps to reproduce:

1. Navigate to the new proposal page in Chrome.
2. Type # Test in the markdown editor.

Expected to see a header "Test" in the markdown preview area, but nothing is shown and there are no JS errors in the console.

The Change Password page has several visual issues that need addressing:

• The error display overlaps with the sidebar on the right side of page
• The inputs and button should look and be organized like the inputs on the signup/login page

Trying to censor a proposal didn't work. It errored out with the following message:

Error setting proposal status
The provided signature was invalid.

Then when I went to the admin panel this was the result:

decred/politeia#160

Loading indicators should be displayed for the proposal submit page and when executing the censor/approve admin actions.

After logging in to Politeia, it should take you /proposals/new. If you refresh while on the page, it will navigate to the /user/login page. It should stay on the /proposals/new page.

Similarly, refreshing on /admin/censored and /admin/unreviewed takes you to the home page.

Runs static website.

nodejs/docker-node#243

I think overall this editor is better suited for our purposes, it's lighter and doesn't have weird text duplication bugs on mobile browsers.

It doesn't do fancy syntax highlighting though,

Need this to happen before the previews will be accurate though:

andrerpena/react-mde#56

since a user may add then wish to remove an image for a proposal, they need a corresponding button/link to do this. currently, you can only add images.

When clicking the verification link in the email, it redirects to /user/verify/success, but there is no UI displayed for that route.

users will need to be able to do stuff like reset their password, set their username, add an avatar, etc.

having a simple page for performing these actions is a start and can be expanded later.