Code Monkey home page Code Monkey logo

superherotwitter's Introduction

SuperheroTwitter

We are so awesome.

Here are methods in main that still need to get written.-------------------

-respond(username)

-searchHashtag(username)

Done------------------------------

-viewTweets(username)

-viewPublicTweets(username)

-makeTweet(username)

-register()

-editBio(username)

-printPublicTweets(String)

-followUser(username)

-changePassword(username)

A requirement stuff if we have time---------------------

-searchUser(username)

AND MORE!

superherotwitter's People

Contributors

dai1313 avatar midnapeach avatar ttruslow avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar

superherotwitter's Issues

Small Bug- line printing that shouldn't?

Hey so I noticed that the line "could not find username" is printing after I quit the Lookup/Follow User menu.

Didn't want to mess up your beautiful menus so I just thought I'd post on here instead. Let me know if you'd rather I look into it.

Not sure if this is the only occurrence.

image

No file i/o

So, we haven't decided on the syntax to write the tweet file or the user file

I tentatively propose this...

author body public tags
author body public tags
author body public tags

for tweet, we may also want to include a timestamp

for users I propose

user password following1,following2,following3 bio
user password following1,following2,following3 bio
user password following1,following2,following3 bio

we have some time to figure this out though, and most of the I/O is going to be handled by the string constructor and the toString method so no worries.

If anyone has any suggestions about how to store passwords without displaying them in plaintext that would be super cool

even if we just impliment a simple Ovaltine style shift cypher that would be super cool and we could say that our code is more secure against villainous attacks.

PublicPrivate implementation of tweets is insecure

Currently the implementation that we have down for making certain tweets public or private is nonsensical.

The only thing stopping someone from seeing someone else's private tweets is clicking the follow button. In a superhero setting this is an unacceptable security flaw.

Therefore I propose that me make the requirement for someone to view someone's private tweets to be mutual followship.

That is to say, person (A needs to follow person B && person B needs to follow person A)

as opposed to (A needs to follow B)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.