/meta/ - Meta
Screenshot_20260523_001446.png (26.9 KB 768x443)
The site will be offline for up to 2 hours, around 1PM UTC today, as Jartyflare is being rolled out.
Every unique IP address will need to complete a quick proof-of-work challenge in order to access the site. This is to prevent more DDoS attacks. The proof is valid for 7 days, so it should not be too disruptive.
Great
What is jartyflare based off of?
>>608
I rarely touch the actual code anymore. But I still have to manually design stuff, especially security critical features like jartyflare. I basically hand it a spec to implement.
Ai still sucks at designing architectural stuff, it always misses important details
bumping as reminder, site will be down in 30 mins. If everything goes smoothly it will be back up soon after.
>>610
doe will this be reliable? since ddos software exists that can bypass cloudflare and etc
>>611
Nothing can prevent DDoS attacks entirely. But it adds a lot of friction. It becomes costly to sustain an attack, as the PoW needs to be recomputed for every IP.
build.png (257.9 KB 1188x781)
Back up, seems to have gone smoothly.
Reply to this thread if experiencing any problems with Jartyflare.
>>614
It doesn't detect anything. It just requires a small amount of computational work for every new IP connecting. The browser computes a proof and submits it, which gives access to the site for 7 days for that specific IP. It makes it costly to flood the server with requests from thousands of proxies.
>>616
for every proxy the foodist would need to do x amount of computational work
So it would cost a lot of CPU time
How vvill we archive jarty.party threads now?
>>623
bump