Engine Owning now down 3 weeks

3 weeks since EO got detected and they are still down. With the size of EO you would think they could pay for more devs or better devs to get it done quicker. Maybe there dev is on vacation again lmao. I imagine they have already lost a good amount of users to other providers now.

Imagine using EO on 2024

just use phantom overlay.

Quote:

Originally Posted by Tflow 3 weeks since EO got detected and they are still down. With the size of EO you would think they could pay for more devs or better devs to get it done quicker. Maybe there dev is on vacation again lmao. I imagine they have already lost a good amount of users to other providers now.

These threads/posts are incredible annoying and useless, when PO or IW was offline due detection it also took 3-4 weeks, so did EO a year ago about a month. If you are thinking you could do any better or faster, why don’t you start learning for it? Shit happens, detections is a huge amount of time to invest and to work on the fix, it really also depends what kind of detection i guess and the big providers are looking for a long term solution instead of rushing their work to get detected next week again.

Btw, EO is currently in closed testing, soz SOONTM

Oh yeah about that vacation you have mentioned, this was a year ago and that man literally started working in his vacation as well (and he’s not the only coder of eo lol), imagine being so mad at a service where subs are paused and compensated after a long downtime, you can literally go to an other provider in the meantime until it’s back up instead of making useless threads, but yet that’s my opinion.

Quote:

Originally Posted by DennisMeister69 These threads/posts are incredible annoying and useless, when PO or IW was offline due detection it also took 3-4 weeks, so did EO a year ago about a month. If you are thinking you could do any better or faster, why don’t you start learning for it? Shit happens, detections is a huge amount of time to invest and to work on the fix, it really also depends what kind of detection i guess and the big providers are looking for a long term solution instead of rushing their work to get detected next week again. Btw, EO is currently in closed testing, soz SOONTM Oh yeah about that vacation you have mentioned, this was a year ago and that man literally started working in his vacation as well (and he’s not the only coder of eo lol), imagine being so mad at a service where subs are paused and compensated after a long downtime, you can literally go to an other provider in the meantime until it’s back up instead of making useless threads, but yet that’s my opinion.

valid asf, well put. people think solving a detection is a switch you just flip, lol. not to mention internals are much harder imo to avoid detections.

Quote:

Originally Posted by DennisMeister69 These threads/posts are incredible annoying and useless, when PO or IW was offline due detection it also took 3-4 weeks, so did EO a year ago about a month. If you are thinking you could do any better or faster, why don’t you start learning for it? Shit happens, detections is a huge amount of time to invest and to work on the fix, it really also depends what kind of detection i guess and the big providers are looking for a long term solution instead of rushing their work to get detected next week again. Btw, EO is currently in closed testing, soz SOONTM Oh yeah about that vacation you have mentioned, this was a year ago and that man literally started working in his vacation as well (and he’s not the only coder of eo lol), imagine being so mad at a service where subs are paused and compensated after a long downtime, you can literally go to an other provider in the meantime until it’s back up instead of making useless threads, but yet that’s my opinion.

not that it matters much but just setting facts straight, iw was down 11 days

Quote:

Originally Posted by privacyendorser not that it matters much but just setting facts straight, iw was down 11 days

I'd like info on that one since i'm sure it was at least 3 weeks, but yeah it does not matter at all, it really also depends on what kind of detection i guess, not gonna fight over it, IW was a solid provider.

X22 was down only about 1 week after it was detected

Quote:

Originally Posted by DennisMeister69 These threads/posts are incredible annoying and useless, when PO or IW was offline due detection it also took 3-4 weeks, so did EO a year ago about a month. If you are thinking you could do any better or faster, why don’t you start learning for it? Shit happens, detections is a huge amount of time to invest and to work on the fix, it really also depends what kind of detection i guess and the big providers are looking for a long term solution instead of rushing their work to get detected next week again. Btw, EO is currently in closed testing, soz SOONTM Oh yeah about that vacation you have mentioned, this was a year ago and that man literally started working in his vacation as well (and he’s not the only coder of eo lol), imagine being so mad at a service where subs are paused and compensated after a long downtime, you can literally go to an other provider in the meantime until it’s back up instead of making useless threads, but yet that’s my opinion.

I find these posts/threads informative as it should be, far from annoying

you are comparing a period without kernel drivers and a period of kernel drivers. Stupidity. 3/4 weeks is the period that everyone "uses". Detection is bypassed pretty quickly, but there's more to it...not just what you see

Quote:

Originally Posted by privacyendorser not that it matters much but just setting facts straight, iw was down 11 days

He is a purveyor of misinformation; don't take anything he says seriously.

Engineowing is ur way for an easy ban I lost three accounts because of them

Quote:

Originally Posted by DennisMeister69 when PO or IW was offline due detection it also took 3-4 weeks

It wasn't "3-4 weeks" FYI. Dates are still in my announcement channel. I closed injections and announced detection October 16 2023 -> had the detection fixed, hardened against similar detections, and announced updated/safe October 26 2023

Corresponding announcements and dates are still available in the channel history

That's 10 days

Not a huge deal but just wanted to correct the timeline

Quote:

Originally Posted by zebleer It wasn't "3-4 weeks" FYI. Dates are still in my announcement channel. I closed injections and announced detection October 16 2023 -> had the detection fixed, hardened against similar detections, and announced updated/safe October 26 2023 Corresponding announcements and dates are still available in the channel history That's 10 days Not a huge deal but just wanted to correct the timeline

My bad, probably have checked wrongly. will check soon how i missed that xD, i really did not intend to spread misinformation, i guess i was a little stoned when checking haha