Additionally, in theory your ISP could inspect your data as it passes through them on its way to you. However, sites that contain important personal data (such as your bank, email provider, online shops you buy things from, etc) should be secured via SSL. This will prevent anyone from inspecting data in transit.

Your browser will tell you if a site is secure, just look for a green padlock on the left side of the URL bar.


It's a good idea not to send anything personal or important unless you can see one of these.


TinyMCE is open source and the 'community' (read: unsupported) edition is available using NPM, and easy to use with module loaders like webpack and browserify.

I'm guessing Davy hasn't done it that way, but without him saying what he's done it's impossible to point him in the right direction. The right direction is probably RTFM, though.

Votes + Comments
Yes. "What did you do, Dave?"

Incidentally, here's the portion of my API that handles CORS. It's in Go (with vestigo), but should be easily translateable to whatever platform you're working with:

    if config.CORSEnabled {

        Warning.Println("CORS is enabled, origin:", config.CORSOrigin)

            AllowOrigin:      []string{"*", config.CORSOrigin},
            AllowHeaders:     []string{"Authorization"},
            AllowCredentials: true,
            MaxAge:           3600 * time.Second,


Unfortunately I am as much in the dark as everyone else here as to how to adapt.

Have a quick look at what's replaced forums in this area.

Take r/learnprogramming for example.

There aren't any "NEED HOTEL BOOKING APP HALP PLS" posts (they do appear but are swiftly dealt with), there's no spam, there's no drama, there are plenty of people offering advice and pointing people in the right direction.

Importantly, there is a set of rules that is rigid and anything that doesn't comply is dealt with so quick most people are unaware that it happens.

Votes + Comments
Well, here you are, weary traveler, one steaming hot cup of justice. No need to thank me, (The Tick)

This is a good question and there are thousands of potential answers, but here's what I'd suggest. Of course this depends on your interests and what you've learned so far.

Start with a problem. It doesn't have to be complicated or wide-ranging and can be as contrived as you like. Say, you have a shelf full of books (don't type them in, just use an existing list!):

  • Which has the longest title?
  • Which was published first?
  • What is the average number of pages (mean, median, mode)?
  • Which language is most popular?

These are all individual problems but you'll also need to 'share' some functionality (namely the loading/parsing of the data). All should be quite straightforward but some moreso than others.

Then add a touch of complexity:

  • Which is the longest book written before 0CE?
  • For each century, which is the most frequently-occuring author in the list?

If you get stuck on any, post back here, someone is likely to help (these are fun tasks!)


I develop on an average machine (a 2014 MBP, i5 with 8GB RAM). I don't need any more grunt because I have AWS at my fingertips. I can have a cluster of massively powered machines at a very reasonable price - you only pay for them while you use them.

If, however, I was a gamer, where latency is a key issue, I'd want that power a bit closer. But, I'd need to spend more money even if I only played three hours a week.

Pros and cons with both approaches.