34 + 35's Posts

34 + 35 📌 1 month ago • 7 views
thinking is har :(
34 + 35 1 month ago • 8 views
Lots of new changes have occurred since the last update so totaally check it out!
34 + 35 2 months ago (edited) • 10 views

Introducing w i k i v e r s e.......
You can create and edit articles but you can't delete and also there's no login because I'm too lazy and inexperienced anyways enjoy! I wanna see people create some articles! Anyways, please comment below some bugs I'll never fix and suggest any ideas you want into WIKIVERSE!

Anyways here's the link...

4
34 + 35 1 month ago • 5 views
i almost got a 100% on my math assignment (i got a 99%) AND ITS ALL BECAUSE IN ONE QUESTION I USED THE WRONG FRICKING LETTER
34 + 35 📌 1 month ago • 7 views
thinking is har :(
34 + 35 1 month ago • 12 views
Eating my favorite candy in the world.... Can y'all guess what it is? :-)

Mints 11%

Twizzlers 11%

Twix bars 11%

Chocolate bars 11%

Skittles 22%

Chewing gum 33%
Ended • 9 votes
34 + 35 1 month ago • 13 views
Darflen achievements are broken lol
34 + 35 1 month ago • 9 views
WHO LIVES IN A PINEAPPLE UNDER THE SEA
(continue in comments)
34 + 35 1 month ago • 8 views •
water melon car
34 + 35 1 month ago • 6 views
SHUSH. YOURE GIVING THEM IDEAS
pi 1 month ago • 13 views

tf is this troom troom type shit

‮895 1 month ago • 22 views

today a girl stole my kitkat and hid it in her bra
what the fuck does that one mean

5

2
34 + 35 1 month ago (edited) • 3 views •
heres three ways on how i might implement articles having views on wikiverse:

1. i iterate through every article and check which articles has the most views

- advantage: you can see top 10 most viewed

- disadvantage: will defintitely not scale up for large data

2. therell be a popular articles field in the root endpoint the field will contain information about the popular article. whenever someone incremenets a view to an article, itll compare the article someone just viewed to the popular article in the root endpoint if it has more views itll replace the article in the popular article field in the root endpoint

- advantage: im sure this'll scale well, right?

- disadvantage: I CANT DO TOP 10 WATCHMOJO THING BOOOOOOOOO

3. urmmm i actually forgor the third

- advantage: less thinking

- disadvantage: theres literally nothing

4. therell be an additional row called viewers. whenever someone views an article itll do a check server-side to see if someones already viewed it already, then will do the same steps from method 2

- advantage: wohooo! no botting!

- disadvantage: viewing only applies to logged in users

so urmmm please do suggest some other techniques or point out some obvious flaws please thank you :)
34 + 35 1 month ago • 10 views
I was just watching "corn 2" when I saw this: