New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

state of things #27

Open

1 of 8 tasks

kristopolous opened this issue Jul 16, 2020 · 1 comment

Member

kristopolous commented Jul 16, 2020 •

edited

Loading

so this is more notes for myself.

we've got the screen (supply) and advertiser (demand/payer)

the screen parts:

landing page (bit.ly like interface for screen generation #24)
email actually working
reporting system
remuneration system
some kind of login/password system

advertiser parts:

gallery of designs
ability to select a specific design
email notification of updates

Member Author

kristopolous commented Jul 16, 2020

I'll be using this, it's a model we are slightly breaking because neoclassicalism isn't actually an efficient allocation.

Anyway... here's our simplified system:

Ad side - the people paying for the ad
Screen side - the people with the screens.

looks like I'll need to decide on a url structure

Let's just go over hostnames off the olvr.io domain:

api - the shared back end ... essentially what waivescreen does
admin - the current waivescreen admin
www - the funnel into the ad/screen side
ad - the gallery, instagram creator, buyer side
ssp - the sell side (the bitly style thing)

The eps will follow the structure accordingly.

kristopolous added a commit that referenced this issue


          fowarding api to the server according to #27

88b82e5

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment