martinomensio / dp1_website_june2016 Goto Github PK

View Code? Open in Web Editor NEW

0.0 0.0 0.0 201 KB

Web programmin part of exam "Distributed programming I" first call of year 2016 (june)

Home Page: https://dp-web-jun16-martinomensio.azurewebsites.net/

License: MIT License

PHP 52.01% CSS 47.99%

php polito

dp1_website_june2016's Introduction

Welcome to my GitHub profile!

I am Martino, PhD Student at the Open University. I graduated in Software Engineering and I am interested in Machine Learning and Explainability. In my PhD I am exploring how different news source are using propaganda to present related events.

I like to understand how things work and I think that Artificial Intelligence should be more than algorithms that learn to perform complex tasks; we have to focus about explainable methods that enable the crowds to understand why things happen, to be able to face and remove bias, correct models and enabling the humans to improve their learning capabilities.

My main contributions here are:

models for SpaCy:
- creator of spacy-sentence-bert, a SpaCy wrapper for Sentence Transformers
- creator of spacy-universal-sentence-encoder, a SpaCy wrapper for Universal Sentence Encoder
- creator of spacy-dbpedia-spotlight, a SpaCy wrapper for DBPedia Spotlight
- mantainer of spaCy-entity-linker, a pipeline for spaCy that performs Linked Entity Extraction with Wikidata on a given Document
- Italian GloVe, an Italian version of GloVe trained on Wikipedia
MisinfoMe: an app to analyse twitter profiles. It is made of four backend services and one frontend:
- credibility: aggregating information about credibility of URLs, websites, tweets
- twitter-connector: managing interaction with Twitter API
- claimreview-collector: retrieving ClaimReview from public websites, providing the manually annotated ground truth
- backend: orchestrating the different services, providing data to the Frontend
- frontend-v2: the user interface available at https://misinfo.me/
My Master's thesis project: Joint contextual NLU and paper
Supports for Master's courses at Politecnico di Torino: see the complete list here

To get in contact in the GitHub style, you can create an issue!

https://martinomensio.github.io/

dp1_website_june2016's People

Contributors

Watchers

dp1_website_june2016's Issues

check on reservation delete

what is the meaning of "The user shall be able to remove her reservation from the site, but not before that 1 minute has elapsed since the reservation start time"?

use of quotations

if not necessary, for strings use single quotation marks instead of double

die after redirect

after each header call, die to stop php processing

email client side validation

HTML5 input type password allows emails like "a@b", while php filter_var with FILTER_VALIDATE_EMAIL does not

delete reservation only from user that created it

check in php the user id of the reservation, don't trust the client

titles too long

remove machine reservations from titles

check javascript and cookies

no javascript -> show warning
no cookies -> block user

how to block user that has no cookies and no javascript?

list reservations on every page

requirements say:
In any page of the site, even without authentication, anyone shall be able to see the current state of all reservations

if connection to db is not possible, show a better error message

probably have to do a try when creating the connection with DB

how to represent duration of reservations

Read the text again and decide if represent as (starting_time, duration) or (starting_time, ending_time).
Also decide if times are represented by (hours, minutes) or if exists a better mySql type for that

what happens on GET requests for "library" functions?

the server should not respond, instead of showing a blank page

authentication must be checked by all pages

all the pages (including the destinations of forms) must check the authentication, because user can remain some minutes completing a form, and when submits a request to one of those pages i must reject it

input validation

check input both on client side and on server side

fix scrolling: topbar must be fixed

on small screens, the topbar must not scroll

time of reservation in differents days

if yesterday I registered at 17:00, and today i try to delete this reservation at 12:00, the time of the reservation is in the future, and therefore a minute has not elapsed yet. Maybe representing the registration time by taking into account the day?

don't escape passwords

lower the "security"

authentication checking

the authentication checking by redirecting may have some problems?
please look at HTTP authentication with PHP.

convert tabs into spaces and prettify HTML

login should be forbidden for already authenticated users

if a user already logged in, on login page I should redirect him to homepage

cookie check management

from a generic source page

If the cookies are not there (cookie count), set a test cookie and go to the verification page with a POST parameter that says from which source page the user is coming
If there are cookies do nothing (terminal condition when the loop succeeds)

The test_cookie page should be reached only with cookies set. So there I can distinguish if they are enabled or not.

If they are enabled, go to the previous page, that will know that cookies are enabled because it will look at the cookies count.
If they are disabled, go to a third page (with a GET parameter propagating the source page) GET because the user can reload freely this page.

The third page works in the opposite way of the source page:

If there are some cookies, go to the page specified by the GET parameter
If there are no cookies, print a blocking error
blocking error contains a button to check again (that goes to the source page to do another loop)

From source page:
Cookies disabled: source page --> test page --> third page&src --> STOP
Cookies enabled and present: source page --> STOP
Cookies enabled but not present: source page --> test page --> source page&src --> STOP

From third page:
Cookies disabled: third page&src --> CLICK reload --> source page --> test page --> third page&src --> STOP
Cookies enabled and present: third page&src --> source page --> STOP
Cookies enabled but not present: third page&src --> CLICK reload --> source page --> test page --> source page --> STOP

Test page should not be navigated directly by user. Must check if POST argument is present. If advanced user cheats by requesting this page with POST parameter, the test will say "cookies disabled" also if the user has enabled cookies but has not the test cookie

remove prepared statements

they don't work