Author Topic: AfterBlock - Blockland Desktop Program [UPDATE 1.2 RELEASED]  (Read 38102 times)

It seems like that it isn't any security you want to preserve, rather your control of the application.

As I said, version 2.0 uses an encrypter which protects the code of people who build custom apps for AfterBlock. If you decompile the program, you can expose the encryption system and keys and blow open peoples apps. If you also decompile, you can learn more about the AfterBlock system and core resources which you could potentially abuse. For example, someone might program a snipplet that clears or damages core variables, breaking functionality. Its a security risk for my programming, a security risk for 3rd party programmers, and a general risk to the welfare of the AfterBlock project. If this doesn't make sense to you, then thats too bad.

As I said, version 2.0 uses an encrypter which protects the code of people who build custom apps for AfterBlock. If you decompile the program, you can expose the encryption system and keys and blow open peoples apps. If you also decompile, you can learn more about the AfterBlock system and core resources which you could potentially abuse. For example, someone might program a snipplet that clears or damages core variables, breaking functionality. Its a security risk for my programming, a security risk for 3rd party programmers, and a general risk to the welfare of the AfterBlock project. If this doesn't make sense to you, then thats too bad.
Just approve apps before they're made public via your site.

Just approve apps before they're made public via your site.

A system like that is unlikely. My approval doesn't stop people using apps-- I'm not turning into a national socialist service like RTB either.

I hope AfterBlock gets a lot more apps. I would totally make something for it if I knew how...

It would be nice if it were possible for Brick Factory to make irregular bricks as well... such as ramps, corner bricks, etc. I don't know how easy that'd be though...

As I said, version 2.0 uses an encrypter which protects the code of people who build custom apps for AfterBlock. If you decompile the program, you can expose the encryption system and keys and blow open peoples apps. If you also decompile, you can learn more about the AfterBlock system and core resources which you could potentially abuse. For example, someone might program a snipplet that clears or damages core variables, breaking functionality. Its a security risk for my programming, a security risk for 3rd party programmers, and a general risk to the welfare of the AfterBlock project. If this doesn't make sense to you, then thats too bad.
Actually, that would be bad. If you didn't do that, people would have to make secure apps because of that everybody could review their code while they would have access to APIs that you didn't approve which might make the apps better.
For example, if you want it to be secure then you might block socket/networking. But what if someone wanted to make an rss client?

Anyway, why would this be useful at all? Everything in this could be made as stand-alone applications just as easy (at least) without this bloated "framework" made with a game engine.

A system like that is unlikely. My approval doesn't stop people using apps-- I'm not turning into a national socialist service like RTB either.
Didn't realize the national socialist's invented quality control.

Didn't realize the national socialist's invented quality control.
Does he realize how stupid he sounds when he tags think as being national socialist?
Sounds like Glenn Beck.

Does he realize how stupid he sounds when he tags think as being national socialist?
Sounds like Glenn Beck.

Think is a national socialist? What?

Tom

Sounds like Glenn Beck.
lolyeah
IcyGamma, the new Glenn Beck!

Does he realize how stupid he sounds when he tags think as being national socialist?
Sounds like Glenn Beck.

He means he won't have a site up for distributing user created add-ons. I don't blame him either.

Actually, that would be bad. If you didn't do that, people would have to make secure apps because of that everybody could review their code while they would have access to APIs that you didn't approve which might make the apps better.
For example, if you want it to be secure then you might block socket/networking. But what if someone wanted to make an rss client?

You obviously don't understand what I wrote.

Anyway, why would this be useful at all? Everything in this could be made as stand-alone applications just as easy (at least) without this bloated "framework" made with a game engine.

There is no bloated framework. This is a single application containing multiple functions rather than requiring separate programs. Its an all-in-one. Whats so hard to understand?

You obviously don't understand what I wrote.
I do understand what you wrote, but I fear that you didn't understand what I wrote.
There is no bloated framework. This is a single application containing multiple functions rather than requiring separate programs. Its an all-in-one. Whats so hard to understand?
The thing is that GM in itself is bloated when it comes to creating "applications". While it might be acceptable for a game to have to load for several seconds, for a small-to-medium-sized application it is not.

While it might be acceptable for a game to have to load for several seconds, for a small-to-medium-sized application it is not.

Then wait for AfterBlock 2.0.

And no, you don't understand what I wrote because you wrote "people would have to make secure apps because of that everybody could review their code " when apps are encrypted by the runner in AfterBlock, a point I was making over and over.


And no, you don't understand what I wrote because you wrote "people would have to make secure apps because of that everybody could review their code " when apps are encrypted by the runner in AfterBlock, a point I was making over and over.
You don't understand what I wrote.
I wrote that as a pro for removing the "encryption" and the restrictions.

Or how about this?
Applications can be in two forms:
  • "Encrypted"
    • Runs in a restricted environment
    • Source is protected
  • Raw GML source
    • Can do just as much as the built-in apps
    • Everybody can read source