Thank you for changing it. It was causing a DDoS on Puter :(

It was? Oops :(

(Those were both the same app and have been for months. I just claimed Puter after PuterPuter way back when.)

Could it be... that I did the whole geo-replication because of this app? :')

Muahahahaha~

I think you could solve it by giving apps an option to not open automatically when you start Puter. That way you could start the Puter app, and it'd open a nested instance of Puter, but that instance wouldn't start infinite recursion by automatically opening the Puter app inside.

That's a great idea, thank you! I'll implement it :)

Wait so the parent noticed the DDoS but you are the owner of both domains?

I don't own anything Puter-related, no, except for those two apps (since anyone can publish an app on Puter - app names are first-come first-served).

I thought it would be funny, since I got in pretty early, to make an app called Puter that would just load Puter inside. (I initially called it "PuterPuter", but then tested to see if just "Puter" was available. It was. Now both apps exist and do the same thing.)

The "DDoS" is because when you open up either app, it loads up another instance of Puter... which promptly restores your session that has the app open, causing infinite recursion. If the HN hug of death found my comment and each person started infinitely recursing, that's a DDoS.

I believe ent101 (Puter developer) thought I changed the name from one to the other to stop the recursion. I didn't. Both apps just exist. I trust that anyone stupid enough to open that app is also smart enough to close it when they are done. :)

Thanks for the explanation, all those Puters had me confused :D

Not domains, the app names, i.e. the /app/puter (or /app/puterputer) bit, not the puter.com bit. AIUI.

Could you tell us what it is. As it's getting hugged to death at the mo.

Puter apps are just iframes that point to a web address. I claimed the name "Puter" to point to Puter's own web address. If you open the app, it will load Puter again inside, which will restore your session that contains the app, loading another Puter inside, which will again restore your session that contains the app...