The JS Bin Robot

Still here. Was always here since 2008. I'm currently looking after 63,594,737 bins for you. Living in a mostly stable maintenance mode. You can support my continued existence too opencollective.com/jsbin/contribu… See you in the code 👋

@nullcookies @CodePen Measures deepend and live. Also, most spam lands on jsbin and not codepen and jsfiddle etc. Sad for me.

These concern me. I hope the good people at @CodePen and @js_bin implement and/or deepen countermeasures to stop en masse deployments of cryptocurrency scam sites. This is too easy. Example: hxxp://jsbin.com/xedofos

@KonajuGames @Scott_Helme Yes, *exactly* like that. Good analogy 👍

@Scott_Helme @js_bin Would it be like renting a house, but locks on the doors cost extra? Any man could walk through the middle of your house.

@js_bin is there any chance secure embeds could be available for free? Security shouldn't cost extra!

@gepeto42 @blacktip @jzsavoie @troyhunt @Scott_Helme You're all doing great on stretching the comparisons. Yes, lead toys, yes, and free rides on zeplins next…totally the same. ^rem

Interesting thread with @Scott_Helme; how do people feel about HTTPS only being available on commercial plans when using @js_bin? This is a service that allows you to embed code snippets on your site. twitter.com/scott_helme/st…

@obijan I have. In fact, I've considered _a lot_ of options. Some recent insights remysharp.com/2018/05/31/the…

@js_bin Have you considered using RDS for the database? Seems like it would get rid of various headaches.

Creating new servers from the original images didn't seem to work. At one point, I had 4 separate db AWS EC2 instances, but none working.

@Scott_Helme @rem No, security is not a paid feature. Embedding is. It just happens that I give away http embedding. (perhaps I shouldn't have in the first place, but that boat had sailed).

@js_bin @rem Sorry, maybe I missed something, but whether or not I'm an active subscriber right now doesn't change the question or answer! You may give too much away, but security is still a paid feature.

@Scott_Helme Well…are you a paying user? I find (@rem here) that I pay when I need something. Except jsbin gives way too much away.

@js_bin If you already have HTTPS support on jsbin then is the worry that people upgraded specifically for secure embeds and they would no longer pay?

@seanodotcom @vuejs No. Not doing any updates to 4 (as per readme). You're welcome to try a PR or use a <script> tag

@js_bin Could you update the @vuejs option to reflect the latest version? (currently 2.5.16) 'unpkg.com/vue' should do it. Thanks.

@emaarkhan Back, sorry.

@NOTPANICKING__ Back, sorry.

@js_bin Are you guys down right now?

@cferejohn Back, sorry.

@js_bin Not sure if anyone is checking this, but I'm unable to load any bins and I got at least one 504...

@bradshroyer Back, sorry.

@js_bin any idea what’s causing the error on sigplot.lgsinnovations.com/sigplot-2.0/tr…

@jbuzzyjr Back, sorry.

db fire update: all back. No data loss. Just time. Send @rem hugs.

@Daniel__Harvey No. The server itself was completely lost. I had to bring up a new large machine, do security updates/etc, then re-mount the db drive, fix all kinds of nonsense permissions, then reallocate IPs.

@js_bin Ah. So just a server reboot? Nothing lost?

db fire update: pretty disappointed that the AWS EC2 r4.large machine last so little time. It was originally launch on October 11, 2017 at 9:24:56. Today it was "scheduled for retirement".

@grahamlyons Sure, but I'm (@rem) is a developer, not ops. I can get so far on my knowledge.

@js_bin I feel your pain but I also see too many people using cloud providers like fixed infrastructure. You should expect the server to disappear at any time and architect with that in mind. It happens in data centres too (disk failures etc.). IaaS makes it so much easier to handle.

@Akhileshjoshi07 back.

@js_bin love the service, but you're taking too long to respond (504). I've checked status.jsbin but thought I'd give you a heads up.

@LuzhouLiquor back.

@js_bin love the service, but you're taking too long to respond (504). I've checked status.jsbin but thought I'd give you a heads up.

@BrianBest back;