mehr-licht/a3s1ltw

a3s1ltw's Issues

implement Session Regeneration < session_regenerate_id(true) >

Empty comments are allowed

At the moment we are allowing empty comments

Enhance comment submission on posts

When submit is pressed, the request to API is done and the comment is inserted on the database.
However it's still not rendered on the client side.
Instead of doing so immediately with javascript, we can improve the API call and make usage of the response.
We can have an id containing the last comment available since the page was called. The API, in addition to post id, comment can also support the last comment id. The response, if successful, returns not only the new submitted comment, but also comments added by other users in the meantime.

arrows points on postView don't work

Add a list of all stories and comments posted by the user to their profile.

exception handling for every database access

Improve header responsiveness

Something to consider is an hamburger menu for small layouts.

Add posts pages (full content + comments)

On list_stories only prints 14/15 posts. Impossible to see the olders posts.

Vertical align thumbnails in post listing

correct action_search

with Any shows Comments

and Posts

when there are none (and they are links!)

Fix flow webpage From edit profile to list_stories

If we go to edit profile there isn't a way to go back to the list_stories without changing the profile.
So my solution will be to create a invisivel button on top of the letters YetAnotherSite

Add support for voting in posts and comments

Related with #3 . Once the API interface is done, we need some JavaScript to handle user interaction (clicks) to perform HTTPRequests to our API, thus updating the database.

use http_response_code ( ### ) instead of $_SESSION(['messages']) when leaving session

...when exiting session

implement search Stories and Comments

Truncate long title and content when listing posts

At the moment, when listing all published posts, the title and content aren't truncated yet.
Probably, the easiest way to handle this is via PHP. When the query to the database is done, we can truncate the title and post content to a specific length defined by us before the function returns.

CSS also has some interesting features to limit width and height based on characters size, but the first approach is likely better.

Sort comments from newest to oldest

Image no longer are visible in list_stories after update

change saving of images to be hashable

encontrar onde temos todos os sha1 com:
grep -rn . -e 'sha1'

e substituir todos os sha1(imagem) por
hash('sha256', imagem)

add CSRF to all actions and callers to those actions

Voting on posts in ViewPost is not implemented yet

populate the database with valuable data. some birthdays, some fotos in res, etc

change how avatar names are stored. sha1($username).jpg instead of $username.jpg

Implement TLS

Create a REST API for voting

We require at least two REST API calls support:

• One to enable voting on posts (api/post_vote)
• The second one for voting on comments (api/comment_vote)

Add user profile view

Function to <Escape scripts>

...and call it for Avery input before storing the information. Information to be stored is the parsec one and not the input