@souple

If anyone had any trouble registering on wikiverse, its because of this line of code. Sorry :P

```

if (!(/^[a-zA-Z0-9.\-_$@*!]{3,30}$/).test(password)) {

return c.json({ message: 'Password cannot contain spaces or newlines and must be at most 30 characters' }, 400)

}

```

what regex should i use for validifying passwords?

Uh need to remind yall that yall accounts from the prev version arent in the new database but you can create a account with the same username to carry the old data

After 3 months, Wikiverse is finally back with a new look, a full on html, js, and css customization for themes, polls, blogs, and so much more!

Will make themes from the designs soon!

https://wikiverse.pages.dev/

#wikiverse #souple #dev

how is burrito not banned on wasteof :P

I actually played a whole song on the piano :O

(if you're wondering its Wrecking Ball by Miley Cyrus!)

wikiverse might release in like late september or somethin so stay tuned :>

I kinda played Thick of It on the piano!

Which homepage design do you like best for wikiverse? (3rd design is incomplete)

#1: https://files.catbox.moe/mez8iv.png

#2: https://files.catbox.moe/goxwo8.png

#3: https://files.catbox.moe/34oosc.png

what if i made a wasteof client

vote!

—-

https://darflen.com/posts/49eabaf101058de324c93f69

todays my bday!!

Lots of new changes have occurred since the last update so totaally check it out!

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 :)

imma stay neutral on this..