Hi everyone
As some may have noticed, the rate limiter on the CDN is in effect now, which will limit how often and quick people can download.
There are 4 stages to any imposed limits. Initially it goes by individual userIDs, but if more than 1 user is identified per IP, it takes the IP into effect rather than the user.
Stage 1: 30 minute lockout
Stage 2: 2 hour lockout
Stage 3: 24 hour lockout
Stage 4: permanent lockout.
I'm not going to say what the thresholds are as that would just invite people to create workarounds. But realistically it shouldn't be possible for any human to hit the thresholds without trying to.
I'm hoping that this is enough to dissuade any potential attackers, but failing that and they find some workaround, I'll have to start introducing some verification methods which I really want to avoid.
If anyone wants to check their standing, you can do so on Discord with the new command
Anyone who believes they have been restricted unfairly or understand the consequences of their actions can tag myself at anytime for review, or infact any member of the core team.
Anyway, let's keep looking forward to how Joey and the rest of the team cook up our A17 releases!
- Aidan
#KeepEvolving
As some may have noticed, the rate limiter on the CDN is in effect now, which will limit how often and quick people can download.
There are 4 stages to any imposed limits. Initially it goes by individual userIDs, but if more than 1 user is identified per IP, it takes the IP into effect rather than the user.
Stage 1: 30 minute lockout
Stage 2: 2 hour lockout
Stage 3: 24 hour lockout
Stage 4: permanent lockout.
I'm not going to say what the thresholds are as that would just invite people to create workarounds. But realistically it shouldn't be possible for any human to hit the thresholds without trying to.
I'm hoping that this is enough to dissuade any potential attackers, but failing that and they find some workaround, I'll have to start introducing some verification methods which I really want to avoid.
If anyone wants to check their standing, you can do so on Discord with the new command
/cdn-access and then provide your ip or userid. Both of which can now be found at https://cdn.evolution-x.org/health at the bottom.Anyone who believes they have been restricted unfairly or understand the consequences of their actions can tag myself at anytime for review, or infact any member of the core team.
Anyway, let's keep looking forward to how Joey and the rest of the team cook up our A17 releases!
- Aidan
#KeepEvolving
❤48👍5👌4❤🔥3🔥2🤯1
Forwarded from Tech Karan OFFICIAL
🚀 Finally here: Android 17 Custom ROM with Features ❤️ | ft. Evolution X v12.0 🔥
👉 Features/Customizations are back 🤯
👉 Strong Integrity fixed 😁
👉 Android 17 is Amazing 👀
More details/Download: Click here
Must watch
💫 https://youtu.be/xWXozBjNdKo
💫 https://youtu.be/xWXozBjNdKo
Also don't miss out:
⚡️ Best Tweaks/Mods for Rooted Phone ft. 2026 Edition
⚡️ Android 17 Best Features
⚡️ LineageOS Secure edition? ft. MicroG Edition
👉 Features/Customizations are back 🤯
👉 Strong Integrity fixed 😁
👉 Android 17 is Amazing 👀
More details/Download: Click here
Must watch
💫 https://youtu.be/xWXozBjNdKo
💫 https://youtu.be/xWXozBjNdKo
Also don't miss out:
⚡️ Best Tweaks/Mods for Rooted Phone ft. 2026 Edition
⚡️ Android 17 Best Features
⚡️ LineageOS Secure edition? ft. MicroG Edition
❤24🔥7👍4
Custom icons are finally working on our Android 17 build, just randomly seen today
❤89🔥23🥰13😱8🤯4👏3
Chromium-based browser freeze issue for Android 17 has been fixed.
🔥40❤14👍8👏6
Just a survey, who here has built Evo A17 for their device? Post screenshots below! 👀
🥰37🔥5❤3👍2
Download Server is back online.
Apologies for the downtime
- Aidan
Apologies for the downtime
- Aidan
❤24🥰4
For today's A17 source changes, the following have been brought back from A16:
- Custom QS tiles, 5G and Hotspot toggle in mobile data tile
- Advance restart menu
- Pocket mode
- Quick pulldown similar to separated QS Not working
- Disable QS dropdown in lockscreen toggle WIP
- Disable power menu in lockscreen toggle
- Secure QS tiles in lockscreen toggle
- Ripple effect toggle
- FP auth vibration toggles
- Revamped network traffic
- Status bar bt battery toggle
- Status bar carrier text customization
- Edge height, gesture feedback, gesture arrow toggles
These are the most useful and non-destructive changes we have seen so importing them isn't much of a problem. This way, source stays clean and stable.
- Custom QS tiles, 5G and Hotspot toggle in mobile data tile
- Advance restart menu
- Pocket mode
- Disable power menu in lockscreen toggle
- Secure QS tiles in lockscreen toggle
- Revamped network traffic
- Status bar bt battery toggle
- Status bar carrier text customization
- Edge height, gesture feedback, gesture arrow toggles
These are the most useful and non-destructive changes we have seen so importing them isn't much of a problem. This way, source stays clean and stable.
🔥57❤11🥰7🏆6
Just wanted your attention on one thing.
https://t.iss.one/EvolutionXMarble/48860
https://t.iss.one/EvolutionXMarble/48899
Context: LMO Freeform/sidebar is the custom sidebar implementation in custom ROMs and it broke after Android 17 changes. Now with that said, when looking for fixes, what do you think we should do first? Try to fix it ourselves, right? If we can't, try to find in GitHub, right? And if it's not visible/public, what now? Just give up?
It seems some developers' egos are currently too big they can't accept the fact that AI has been improved enough to the point it can help debug issues. Just because you did it first, doesn't mean you're the only one that can. Not every authorship problem is because of theft and not every fix should be attributed to you just because you were first.
If the fix was not available at the time of searching, developers will look elsewhere for solutions.
https://t.iss.one/EvolutionXMarble/48860
https://t.iss.one/EvolutionXMarble/48899
Context: LMO Freeform/sidebar is the custom sidebar implementation in custom ROMs and it broke after Android 17 changes. Now with that said, when looking for fixes, what do you think we should do first? Try to fix it ourselves, right? If we can't, try to find in GitHub, right? And if it's not visible/public, what now? Just give up?
It seems some developers' egos are currently too big they can't accept the fact that AI has been improved enough to the point it can help debug issues. Just because you did it first, doesn't mean you're the only one that can. Not every authorship problem is because of theft and not every fix should be attributed to you just because you were first.
If the fix was not available at the time of searching, developers will look elsewhere for solutions.
❤56👍15