Original Post - 05/29/2025 03:29 PM *(edited)

Kxzir1

Posts: 68

just an question

2
2
0
Reply - 05/29/2025 04:12 PM

Powdered2

Posts: 13

I think finobe.net will implode tommorow.

0
0
0
Reply - 05/29/2025 04:39 PM

moot

Posts: 17

yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah yeah

0
0
0
Reply - 05/29/2025 08:45 PM

xs08c

Posts: 28

I think finobe.net will implode tommorow.

yes

0
0
0
Reply - 05/30/2025 01:31 AM *(edited)

Sea

Posts: 46

I was actually thinking to make a post about this a few days prior, but either I could not been asked or felt delusioned enough to expect only disagreement about this.

I was strongly confident about it bringing back ORC to a good condition. Aesthetiful has great knowledge when it comes to web security, and that was the major reasoning behind it all. But that was before the incident which has happened a few days ago. Now then, as well as with Todd stating in the "Critical problem" forum post that anything can go wrong when the clients will be ready, all I can say is: I do not know.

If we really want finobe.net to resurrect the ORC, everything MUST be polished for it to happen. I do mean that it MUST be, otherwise this revival and the trust which we gave to Aesthetiful would be on the line, and I am pretty sure he does not want that to happen. Importances like security and vulnerability patching MUST be the prime focus of it, if we all hope for it to happen. Every flaw, and literally every must be eliminated.

Now, I do know I sound like a perfectionist here, but in the reality of revivals, this is a valid point with how many low-effort revivals have fallen apart because of them not focusing of the main principle of web development and the important mindset of revivals that "You cannot trust the client". We do not want that to happen to finobe.net, right?

In short: finobe.net must give it all, in order to do it flawlessly.

2
2
0
Reply - 05/30/2025 02:29 AM *(edited)

Kxzir1

Posts: 68

I was actually thinking to make a post about this a few days prior, but either I could not been asked or felt delusioned enough to expect only disagreement about this. I was strongly confident about it bringing back ORC to a good condition. Aesthetiful has great knowledge when it comes to web security, and that was the major reasoning behind it all. But that was before the incident which has happened a few days ago. Now then, as well as with Todd stating in the "Critical problem" forum post that anything can go wrong when the clients will be ready, all I can say is: **I do not know.** If we really want finobe.net to resurrect the ORC, everything **MUST** be polished for it to happen. I do mean that it **MUST** be, otherwise this revival and the trust which we gave to Aesthetiful would be on the line, and I am pretty sure he does not want that to happen. Importances like security and vulnerability patching **MUST** be the prime focus of it, if we all hope for it to happen. Every flaw, and literally **every** must be eliminated. Now, I do know I sound like a perfectionist here, but in the reality of revivals, this is a valid point with how many low-effort revivals have fallen apart because of them not focusing of the main principle of web development and the important mindset of revivals that "You cannot trust the client". *We do not want that to happen to finobe.net, right?* In short: *finobe.net must give it all, in order to do it flawlessly.*

2016 is easy to patch since the client source code was leaked

0
0
0
Reply - 05/30/2025 04:07 AM *(edited)

Sea

Posts: 46

2016 is easy to patch since the client source code was leaked

That is indeed true and something that I am aware of myself, but:

  1. The 2012 client is still a hellscape of Assembly code that I do not bother to understand (I plausibly could, but I have better and more important things to do than involving in grey area)
  2. Again, with the concerns that I have after the said incident, I really do want to be sure that not just the backend, but everything in this revival has at the very least little to no flaws at all, else the potential would be lost to the brim.

It already feels like that I am starting to get paranoid, but I just value this revival with the way how it acts 10x more adequate than any other and I do not really want someone oppositional of that (like what could have happened) to kill it just like that.

1
1
0
Reply - 05/30/2025 05:52 AM

Todd

Posts: 56

will it survive

0
0
0
Reply - 05/30/2025 05:54 AM *(edited)

Kxzir1

Posts: 68

will it survive

it survived 2 years without client it could survive much longer

0
0
0
Reply - 05/30/2025 06:48 AM *(edited)

Part

Posts: 3

>But that was before the incident which has happened a few days ago.

Can somebody explain to me what exactly happened, what incident exactly? Is this related to dive spamming the forums or?

0
0
0
Reply - 05/30/2025 06:51 AM

Kxzir1

Posts: 68

>But that was before the incident which has happened a few days ago. Can somebody explain to me what exactly happened, what incident exactly? Is this related to dive spamming the forums or?

related to dive friending everyone without friend request and also spamming the forums

0
0
0