Author Topic: blocklandsaves.com  (Read 24184 times)

Needs the following things:

Mandatory pictures of the build for each save

Brick count in the description

If I submit a file I'd like to know know many views it had, and of those views how many downloads it has.

A place to list color sets and bricks required to load the build correctly

Rating system that can only be used if your logged in, but you can view the ratings if your not logged in.

A way to password protect a save so you can use it as a save upload site and a way to safely transfer a private save to someone.

Did anyone see my suggestions?


I like this idea! It would be cool if it had a style similar to the forums, too.

Can we use our Zapkraft login details for this or not?


Just use the blockland auth server for logging in, you only need to enter your name then.


Can we use our Zapkraft login details for this or not?

wtf is zapkraft and why on earth would he use spome other unrelated login for this?

It's a simple algorithm I made (afaik).

P = input password

1) C = Generate some thousand characters
2) A = sha3 hash of C
3) B = C encrypted with P
4) store A/B somewhere

To login:
1) pull B out and decrypt with input password
2) hash it and compare to A
3) if equal then it is sec.

The wonderful thing about this is that you first have to crack the large hash that is the several thousand characters inorder to even begin bruteforcing the password. It's simple and effective.
i don't see what benefit this holds over doing sha3 C + P

about rating builds, I feel like If you have pictures and a description that should be all thats necessary

Suggestion for the BLID thing:

When you register, have them enter the link to their profile (ex: this), afterwards, ask them to (temporarily, of course) change their signature to contain a verification code. Scan their signature for the code; if it matches up, get their blid from their profile and then they're verified.

Suggestion for the BLID thing:

When you register, have them enter the link to their profile (ex: this), afterwards, ask them to (temporarily, of course) change their signature to contain a verification code. Scan their signature for the code; if it matches up, get their blid from their profile and then they're verified.
bullstuff. just use the master server. easier.
« Last Edit: November 27, 2013, 05:40:27 PM by Lugnut »

bullstuff. just use the master server. easier.
You can't publish saves onto the master server.

You can't publish saves onto the master server.
hng fine you noob i'll quote evar so you know what i'm talking about

see edit
Suggestion for the BLID thing:

When you register, have them enter the link to their profile (ex: this), afterwards, ask them to (temporarily, of course) change their signature to contain a verification code. Scan their signature for the code; if it matches up, get their blid from their profile and then they're verified.
bullstuff. just use the master server. easier.

bullstuff. just use the master server. easier.
I'm not saying it isn't; It's just a suggestion.