You can do a lot of cool stuff on Glitch, but what first drew me to the platform as a user was the ability to easily build and host APIs. I still can’t quite believe you can hit a button and immediately have a hosted API available for making client requests, backed by persistent data storage. If that isn’t enough, you can jump in and start editing in the browser, seeing the results straight away, with no deployment process whatsoever. 🤯

So needless to say, I’ve been having fun working on the new set of data apps I’ll talk a little about in this post. We’ll run through the available options, whether you’re hosting your data on Glitch or connecting to an external service. We’ll also take a look at our minimal no-frills version, and find out how you can switch to your own data provider, use your project as an API, or just tear it apart and turn it into whatever you like.

The app concept we’ve used in all of the Hello data projects is a user poll on favorite coding languages. The homepage lists the poll and presents results in a chart when the user casts a vote. An Admin page shows a log of votes, and allows deletion when you set up an admin key by following the steps in the README.

These projects are intended to follow on from Hello Node, using a similar pattern–a server script returning data to a user interface with Handlebars templating.

When you remix the Hello SQLite project, Glitch will build you a copy of the underlying database, making your app work out of the box with no setup steps. 

The database files are placed in the .data folder, which you should use to securely store any data you add to your apps, as the folder is not copied when a project is remixed. The data starter projects also use the .env for secure storage of access keys: How do I store secrets, credentials, or private data?

What we’re going for here is coverage of the primary operations you’d need in a database backed app–queries, inserts, updates, and deletes. Authentication / authorization is a huge barrier when learning about anything data-related, so we wanted to introduce the idea of auth without wading knee-deep into a full auth flow, which is not only a pain, but frankly not the most fun part of working data when you’re just getting started.

A common pitfall in building demos for data is allowing the user to post without requiring auth. You can of course do whatever you like in your own remixes, but for the official Glitch apps we need to be mindful of the risks in allowing anonymous users to post data that other people in our lovely community will see. This is why we went for a poll, since you can only submit a vote for existing options. 😅

As with our recent series of core Hello apps, the data apps include next steps you can try out in TODO.md, so that you can get stuck into an edit straight away, and take it from there. 🚀

Third-party data integration with Airtable and DataStax

Hosted SQLite is handy for ease of setup, and lets us minimize learning barriers by keeping people within the Glitch environment, but as you work on real world projects, you’re likely to integrate data from a third-party service. This is where our Airtable and DataStax projects come into play.

Hello Airtable provides a low-friction data storage option with setup steps outlined in the README. We’ve included a link to a base you can copy so that the app will work as soon as you’re set up. 

Copy the base, grab your ID and API key, pop them into your Glitch project, and off you go.

We’ve been loving collaborating with the DataStax team on the Hello Astra project, which uses Astra DB, a persistent cloud database that gives you all the power of Cassandra but without the complexity of setting it up. For a distributed, highly scalable data service, there are remarkably few steps required to get started–each outlined in the README. 

Expect to get your own database ready and connected to Glitch in the space of a few minutes.

Our Hello apps are primarily optimized for learning, with lots of bells and whistles demonstrating a variety of functionalities, plus a nice front-end so that you see something when you visit a project’s page. This is good for beginners, but for those who just want to get a project up and running with as little hassle as possible–we have blank versions of the starters.

The blank SQLite project gives you a minimal outline of CRUD operations, with a sample data model representing a list of chat messages. This app has no front-end, so the home route just returns a list of the available endpoints (courtesy of Fastify hooks). The sqlite.js module handles managing the database, with server.js calling the methods available to retrieve, add, update, and delete (with endpoints returning JSON). To change the data model, alter the setup code in the SQLite script.

We’ve tried to build these projects in a modular fashion so that you can pull out whatever bits you want and bin or ignore the rest.

Our Hello data apps support sending and receiving raw JSON if you want to use them without the front-end. You can make requests to the endpoints from any client of your choice, supplying a query parameter: ?raw=json (try glitch-hello-sqlite.glitch.me/?raw=json in your browser or client to see it in action). 

We structured these apps to handle the database operations in a dedicated module for the relevant provider. In the src folder you’ll see sqlite.js, airtable.js, or astra.js, with methods called by the server script whenever an endpoint receives a request.

This means that you can swap out an existing database for another one, just by replacing the data handler script. The server will continue to work as long as you provide the same methods in your data module, and include the script name in data.json, for the database property.

If you remix with a different database, let us know how you get on!

You can do a lot of cool stuff on Glitch, but what first drew me to the platform as a user was the ability to easily build and host APIs. I still can’t quite believe you can hit a button and immediately have a hosted API available for making client requests, backed by persistent data storage. If that isn’t enough, you can jump in and start editing in the browser, seeing the results straight away, with no deployment process whatsoever. 🤯

So needless to say, I’ve been having fun working on the new set of data apps I’ll talk a little about in this post. We’ll run through the available options, whether you’re hosting your data on Glitch or connecting to an external service. We’ll also take a look at our minimal no-frills version, and find out how you can switch to your own data provider, use your project as an API, or just tear it apart and turn it into whatever you like.

Dive into the new Glitch data starter apps

Good news — after the wonderful response to our recent huge updates to Glitch, we’re back with even more of what you — the Glitch community — asked for.

Now running a real database behind your app is as easy as remixing

We’ve launched four brand-new starters that instantly set up some of the most popular database options for your app automatically. 

~glitch-hello-sqlite: A simple, powerful full-stack app backed by a SQLite database

~glitch-blank-sqlite: That same SQLite app, but with just the basics to get started

~glitch-hello-airtable: Use your data in Airtable to power your Glitch app!

~glitch-hello-datastax: It’s a Cassandra database app, powered by our friends at Datastax

Now, you can experiment with creating archives, backups, collaborative apps, and more with the power of persistent data storage. 

Imagine having a full-stack node app running a Cassandra database, in under a minute. Thanks to our amazing Glitch community, that's now possible, along with lots of other improvements to building full-stack (and even database-powered!) apps.

Try out Blank starter apps and improved next steps

We loved this idea from the community, so now Blank starter apps are available for most of the Glitch starter apps. Blank is truly the best way to describe these minimal starter versions of the apps, and we’re very excited to see how you use them! We’ll create Blank options for all of our Hello starter apps going forward. (No more having to delete parts you’re not using!)

Another update to the current roster of Hello starter apps is the new “Try this next” in TODO.md, which gives you a simple list of tips on what to try next once you’ve created a new app.

Look for the TODO.md file in our Hello apps. It’s got a few suggestions for things you might want to try next with your new app. Let us know if you try any of them out!


Check out curated collections and start gathering your own

Search no more, curated collections are back! Now, you can find the new (and classic!) starters on /create-project along with a showcase of apps made by the community. 

We’re always on the lookout for apps and collections to share with the community, so let us know if you’ve curated any that we should share by posting them to the Support Forum gallery. 

Just when you thought things couldn’t get any fresher

Finally, because you know we like to keep things fresh, we’ve made some performance updates resulting in a significantly faster load of Glitch.com (up to 3 times faster!). This is just the first step toward even bigger new community features to come. 

We can’t think of anything fresher than showing appreciation back to the community so now you can thank users just by hovering. This makes it easier than ever to thank fellow members of the community for their awesome contributions. Don’t be shy about thanking your fellow community members, it’ll make their day.

As you try out these new starters, features, and updates, be sure to tag us on Twitter or email community@glitch.com so we can share your handy work with the Glitch community. We want to tell the world about what you make, so don’t be shy. Your work helps inspire everyone else in the community!

Good news — after the wonderful response to our recent huge updates to Glitch, we’re back with even more of what you — the Glitch community — asked for.

Data-driven full stack apps — running instantly!

Recently, we launched a whole new set of starter apps on Glitch, with the goal of making it nearly instant to build apps using the latest and greatest frameworks. Naturally, while creating these new experiences, we wanted things to be simple. But that raised an important question:

Going back a few years, we built Glitch around the idea that anyone should be able to create a real website or app using standard code, right from their browser, and have it up and running instantly. Today, that’s more or less the case, and the evidence is that clever folks (like you!) have used Glitch to build over ten million apps.

For some users, like students learning to code for the first time, “simple” may best mean “has the fewest distractions”. And in that context, distractions can be things like metadata or configuration options that, while useful for a production website, might require a lot of confusing explanation at a point when a learner is first trying to understand the major concepts they’re wrangling with.

By contrast, for coders who may be familiar with web development in general, but might not know the specifics of a new framework that they’re trying out for the first time (or for the first time in a long time), the typical boilerplate that one might see in an app are familiar and reassuring parts of a web page that they expect to see. And so, “simple” means “it handles all those little default chores for you, so you don’t have to”.

These are both valid expressions of “simple”, and both vitally important to audiences we care deeply about. Having simple experiences that anybody can use to start coding productively is a key part of tackling the stress we call "stack anxiety".  But these two versions of simplicity are also mutually exclusive — we can’t make an app that’s “simple” by having fewer lines of distracting metadata while simultaneously making one that’s “simple” by giving you all the default metadata out of the box. We can’t be simple by automatically handling configuration while also being simple by making it easy to customize configuration.

So we took an uncharacteristic path for Glitch: We chose both.

Typically, we’ve had a strong bias toward being opinionated, while offering customization under that hood. That way, we can have a predictable experience that users on the platform can share, and also we can smooth the rough edges of one particular designed experience. But we’re at a stage of maturity and familiarity with the ways that people want to build on Glitch which lets us offer a little more flexibility without losing that ease of use.

We took an uncharacteristic path for Glitch: We chose both.

Thus: “Hello” and “mvp”. (Here, we're using "mvp" to mean "minimum viable product", a common industry term for the simplest version of a project that could possibly do the job.) For each of our common frameworks, we offer each of these two options:

Hello: a starter app that’s set up with all the most popular default configuration settings and boilerplate provided for you out of the box

MVP: a starter app that’s the absolute minimum to get you running, with nothing that you might want to delete and no distractions of anything unfamiliar

These two approaches encompass two different but valuable views of simplicity:

“Do it for me, but let me change it later if I need to”

“Don’t do anything for me except the essentials, so I don’t have any distractions”

We’d love to hear how those choices work for you, and also how you think about what “simple” is for creating. The early response to these choices has been phenomenal. One way we could tell that this approach is working is by looking at examples like these Preact starters, created by a community member, which already follow the implicit convention we’ve been creating. The fact that people in the community can intuit how these kinds of examples should work means that it’s comprehensible enough for people to understand the whole system, not just one individual implementation. And it’s creators in the community who see the benefit.

We’ll be accelerating our creation of opinionated new starter apps in both flavors of “simple”, using the toolkits, frameworks and libraries you’ve asked for most. If you want to be part of creating one, or to see your favorite technology featured, reach out and share your ideas (or example apps!) with us. And if you’ve tried out the new, simpler starter apps, let us know what would make them even more useful for your workflow. We want things to be as simple as possible.

Recently, we launched a whole new set of starter apps on Glitch, with the goal of making it nearly instant to build apps using the latest and greatest frameworks. Naturally, while creating these new experiences, we wanted things to be simple. But that raised an important question:

What kind of simple?

What do we mean by "simple"?

We just launched generated static sites! 🎉 This has been an in-flight feature for a long time, and something I’m really excited to finally see out in the world. There are a lot of moving pieces, but the most important thing to take away is this: generated static sites allow you to run a development process and, when you’re done editing, Glitch will run your `npm run build` script and upload that optimized build to the glitch.me domain every project gets free.

The new starter projects were created for remixing. This bumps up our two templates (hello-express and hello-webpage) to four (website, node, react, eleventy) with opinionated and minimal versions of each. Thinking through the technology choices for each starter and choosing the packages that we were endorsing was an exciting challenge, and we were able to build on the incredible work the open-source community has been doing since we last created new starters. Let’s walk through the new starters and what powers them to give you a better idea of how they’ll help you get started building your idea in seconds.

Our previous Node.js starter, hello-express, was in daily use but starting to fall behind modern Node best practices. Looking at the landscape of Node web servers, there was a clear choice: Fastify. The speed gives us the ability to serve more pages, faster, from the glitch containers. It’s also great how easily extensible Fastify is. Having validation built-in didn’t hurt. We are really excited about what Fastify will allow us to build going forward and how to leverage it for Glitch users; plus, we can build Glitch-specific plugins to interface with our asset management, fully-powered terminal, etc., in the future. There isn’t a lot of boilerplate needed to instantly create an API, so we were able to keep both the opinionated and minimal versions of the Node.js starter fairly straightforward.

We’ve had trouble in the past getting the React development process to be performant on Glitch servers, so solving the speed problem was the #1 priority. Fortunately, our team didn’t have to do much of the work here and instead could rely on Vite to do the heavy lifting. It starts immediately, supports TypeScript and JSX, and has hot module reload enabled by default. That significantly reduced the surface area we needed to build ourselves to support a lightning-fast React workflow.

One way Vite achieves these incredible speeds is by bundling all of your dependencies (in ~glitch-hello-react they are: React, Wouter and react-helmet-async) with ESBuild. ESBuild is an extremely fast JavaScript bundler written in Go. Most likely you aren’t changing your dependencies nearly as much as your code, so it can do that once and only build again when you add a new dependency or upgrade the version.

When you close the editor and stop working on your site, it runs the Vite build process in the background which creates an optimized bundle with Rollup. That means you can take advantage of the wild world of Rollup plugins. We serve this fast production bundle at your free glitch.me domain until you start working in the editor again.

Static site generators are all the rage today, and for good reason. Eleventy cares about speed, ease of use, and—most importantly—the experience of someone browsing your site. When you run the Eleventy build script, it takes all of your files and creates a bundle that can be loaded by those still using AOL dialup. (Please let us know if you are still using AOL dialup!)

The Eleventy starters list is a scoreboard with Lighthouse scores, pushing Eleventy builders to make a performant site that anyone on any connection can view. As website bundles get more and more bloated, Eleventy pushes for as little JavaScript as possible, and uses it only where you need it.

Our  ~glitch-hello-eleventy starter has support for blog posts in Markdown, beautiful styling, and instructions for adding more complexity if you need it. The minimal template was built by the Eleventy team.

Along with support for Eleventy, we’re supporting all of the Eleventy projects that others have built. Want a high-performance blog with image optimizations and analytics? Check out eleventy-high-performance-blog. Something a little more designed, that uses Tailwind CSS and a JS framework (Alpine.js)? Try 11ta.

These are just our starters using the new generated static site functionality. You can apply the same concepts to a Vue site, or Svelte! Any code you can run in the build script that outputs to a build folder can take advantage of this new functionality. Just add this configuration to your package.json:

"glitch": {
  "projectType": "generated_static"
},

That will tell Glitch to treat your project as a generated static site so you have a development environment when you want it, and a production site on your glitch.me domain when you’re done.

So, why not remix one of these starters and create a new project right now? 

Glitch engineer, Keith Kurson, discusses the tech stack and opinions behind our new lineup of Glitch starter apps

A closer look at the new Glitch starter apps

We’re excited to announce some new updates that will have you building even faster with new starter apps, support for generated static sites, and a clean new look that makes the Glitch experience faster and fresher than ever.  

Get from idea to “Hello World” in seconds with our new lineup of starter apps, along with new and improved support for generated static sites

We’ve created new, fresh and fast starter apps to get you building websites and Node apps in seconds. In addition to a refresh of our static website and full-stack Node app starters, we’re improving our FREE static sites to support generated static sites, too! This was something our community has been asking for, so we’re excited to give you the benefits of fast and free static sites with the power to configure how your sites are built. 

Try it out by remixing our brand new React and Eleventy starters or updating your app’s package.json file. 

We picked a powerful set of tools to help you create full-featured apps on Glitch. 

There’s so much anxiety about which JS framework or build tool to pick, so we made some really good default choices for you. Our new Node starter now uses Fastify to give you a faster, extendable developer experience when writing Node. We chose React and Eleventy for their versatility, documentation and the wealth of developer content created by their communities. And we harness the powers of Vite to further improve the development and build experience in our React starter. 

You get all of the benefits of these tools without having to do any setup. But if you do want to configure your app or use other tools, go for it! Glitch won’t lock you into the platform or abstract away the code that is powering your idea. Don’t forget the rewind feature is always there if you need to backtrack—mistakes are welcome and encouraged!

Build a web app in less than a minute on Glitch.com

Syntax highlighting support for more file types

With this new update we’ve added support for syntax highlighting to make your code as clear and concise as possible. Open your Glitch editor to see syntax highlighting in action for the following file types:

These updates can help you go from idea to app in seconds, or serve as an introduction to a whole new world of frameworks. Don’t see your favorite framework listed right now? Our community is already collaborating to make the next wave of super-easy starters for Glitch. Join them and let us know what you want to see next.

Our newly updated “Create Project” page is available for everyone now, featuring our new official starters as well as Github import. Watch this space for more useful starter apps, as well as projects curated from and by our community!

There’s always something new to inspire you at Glitch

Whether you’re just beginning to experiment with Glitch or a remixer extraordinaire, we are excited to introduce—or reintroduce—what Glitch is all about to everyone. Yes, you can use Glitch to go from idea to site in seconds, but not just any site: a reliable, performant, accessible site (or app!), backed by some of the most powerful tools on the web. These updates and features are the result of a lot of careful consideration for our amazing community of explorers, dreamers, and builders, resulting in a Glitch that is faster and fresher than ever. 

If you have any fun or interesting projects you’re building using our new starters, feel free to tag us on Twitter, share in our support forum gallery, or email community@glitch.com so we can share with the community! In the meantime we’ll be hard at work making the Glitch experience the most reliable, intuitive, and friendly place to build the web. ✨

Take your apps to the next level with a Pro account

Glitch is the fastest way to go from code to deploy. You can build anything from small static websites to complex full-stack apps for free! All Glitch users get our powerful and collaborative in-browser editor, with Github import/export and Prettier support. Static sites come with free always-on hosting; full-stack apps sleep to save resources but wake on demand. Upgrade to a Pro account to get all of that and more: access controls, private projects, and the ability to Boost 5 full-stack apps for more disk space, memory, and always-on status. Check out our pricing page to learn more and subscribe!

Get a React or Eleventy app up and running in under a minute with the fastest, most powerful upgrade to Glitch ever. Now, it’s quicker to build a real website on Glitch than with a no-code tool.

Remix a whole new Glitch

Starting today, Glitch members with paid subscriptions can easily control who accesses their code and who sees live projects. 

We’ve made sharing your app easier than ever. Control who has access and who can edit a project all without having to build some complicated authentication system for your project.

Here are just a handful of things you can do with this feature:

Stay in stealth mode until launch. Developer advocates can build demos and keep them private until the big announcement. 

Share code with students or workshop attendees. From classrooms to conferences, you can control who sees assignments and projects.

Build internal tools. Whether you’re prototyping a new feature or using Glitch for your latest greatest Slack integration, create apps with your colleagues in mind.

Interview candidates. We’ve heard from teams who use Glitch to evaluate new team members. Now it’s even easier to share code examples with potential hires.

Grow your own private blog or newsletter. Have something you want to save for your inner circle? Share your best ideas with a select audience.

Build a project and hit the “Share” button in the top left just like you normally would. You’ll see a new pop up with a drop down menu where you can set your project’s sharing settings. 

Public is the default setting, which makes your project visible and its code remixable for everyone 

Private limits both your code and live site to project members

Private Code keeps the live site visible, but restricts code to project members 

We’ve eliminated the ability to join projects with share links and instead, are now asking project owners to explicitly invite collaborators via email. This implementation is more secure and gives projects owners greater visibility into who has access. 

Current free users with “private” projects will still have their code only visible to members of their project. However, changing a project from private to public on a free account can’t be reversed. 

We’re spending a lot of time thinking about how to better enable groups of users on Glitch and what collaboration looks like in a professional setting. Since we launched our paid tier in the spring, we’ve seen lots of individual creators build more powerful apps and also introduce Glitch into some of their professional workflows - from hiring and onboarding team members to prototyping new features and internal tools. We’ll share more on this front as our roadmap evolves.

If you have any fun or interesting projects you’re building using today’s news, feel free to tag us on Twitter or email community@glitch so we can share with the community! 

Starting today, Glitch members with paid subscriptions can easily control who accesses their code and who sees live projects.

The easiest way ever to control who you share your app with

When we think about our plans for Glitch and what we need to build, it’s usually in service of two things:

How can we empower creators to build the web and make the experience fun and accessible?

How can we help as many people as possible and grow our business in the process?  

Today we’re excited to share some changes that make the Glitch experience better while also offering more transparency about our free tier and paid membership. 

Since Day 1, we’ve always put Glitch projects to sleep no matter how big or small. It was just a general rule that we enforced in order to keep our servers happy and run more efficiently. Over the last month or so, we’ve made some significant changes to our back-end, which now means  your Static Sites never go to sleep — even for free users!

We pride ourselves on being a great full-stack solution for web apps, but we also know that so many community members just want a quick and easy solution to create and share simple web pages. From students sharing out a resume for the first time to local Pet Adoption centers, we’ve seen a whole range of pure HTML, CSS, and JS goodness. 

If you have static sites on Glitch, check your projects view and you’ll see a little label that says “Static Site”.

Important note: If you’re not seeing the “Static Site” label and you know the project is static, just wake it up or hop into the editor and you should be all set!  

Back in April we launched Boosted Apps, which is a paid upgrade on Glitch. Members who opt-in get up to 5 boosted projects, which keeps them on and also increases rate limits, disk space, and memory. 

One question that kept coming up for some users is, “How do I know if paying for Glitch is right for me?” Here’s our official take. 

If you want to build something quickly or you're just tinkering, get started for free. (We don’t even make you sign-in if you wanna give the editor a spin; just create an account if you need to save your work.) 

If you want to make a lot of stuff, but don’t need projects to run all the time, the free experience might still be enough. Here’s where today’s update comes in. 

We’re introducing Project Hours to give you greater insight into the resources that your projects are using without the typical complexity associated with cloud hosting. We don’t want you to have to think about things like compute, transfer, dynos, and droplets. All you need to know is every month you’ll have 1,000 hours for your projects to run and they’ll reset back to 1,000 on the first of each month. This new policy will go into effect August 1, but you can see and monitor your July hours in your dashboard now. 

If you find that the 1,000 hours isn’t enough, that’s when you should upgrade. You’ll get the 1,000 hours plus the 5 boosted slots, which you can rotate projects in and out of.

In short, there’s a lot that comes with the free Glitch experience. As of today, you’re getting static sites hosted for free without going to sleep. You’re getting a full-stack container and in-browser editor that’s simple enough for beginners, but powerful enough for professionals. And you’re getting 1,000 hours of free hosting time. 

If and when you need more magic under the hood, upgrade and support the community. In the meantime, we’ll continue working to make the Glitch experience the most reliable, intuitive, and friendly place to build the web.

Fast and free static sites on Glitch and new Project Hours

One month ago we talked to you about the increased number of incidents that Glitch was experiencing at the time, and how we’re committed to keeping Glitch reliable so that you can focus on creating and sharing:

“In the coming weeks, we’re going to be making significant changes that will have a big impact on uptime and stability. On top of that, we’re working on improving your experience with managing projects on Glitch.”

We wanted to give you an update on how things are going and a peek at more good things to come. 

We have seen a significant improvement in uptime over the past few weeks. The platform is experiencing fewer and shorter incidents. This is a huge win for us and wouldn't be possible if our community hadn’t helped us make some key decisions like reducing the impact of pinging services on the site. Thank you so much for sticking with us through the turbulence. 

Also, special shout out to our Support Forum regulars. You all have been super helpful and welcoming to newcomers asking about service incidents, policy changes and general questions about code and Glitch!

Something we quietly launched earlier in the month was a more straight-forward way to manage what you make on Glitch. If you’re logged in, you can try it at https://glitch.com/dashboard, and you can also get to it by clicking “Your Projects” from your user menu on the top-right of the homepage. 

We want building and sharing apps to be frictionless and intuitive, which is why we've always shielded you from having to know the complexities around how projects are run. That said, we've heard many of you say you want more information about your projects and greater control over how you manage them. This new tool is a step towards creating that experience — and it’s going to keep getting better.

A lot of the changes coming up are all in service of empowering creators like you to quickly and easily host projects, but also give you the stability and control you might expect from more conventional hosting providers. 

We have to strike a balance between keeping things simple and free, but also give everyone the tools and transparency to manage more resources if they need them. Launching boosted apps was a big first step in this direction, but it’s just a start.  

Hopefully you’ll find our next set of updates a nice enhancement to the free Glitch experience and also an upgrade for those of you looking for more power. 

An Update On How We’ve Been Making Glitch More Reliable

We’re doing a ton of work behind the scenes to make our infrastructure more stable.  As we mentioned in last week’s post:

One of our big challenges is dealing with third-party services that ping Glitch to keep apps awake. Not all of these services are as reliable as we’d like, and sometimes when there are problems they can cause as much load on our systems as a malicious attack would. We’re not banning the use of pinging (or “uptime”) services on Glitch right now, and we’d like to not have to. 

We did some more investigating and started to temporarily block traffic from ping services to help reduce the load on our servers. The temporary block allowed us to see just how intense a strain they put on the platform. 

Despite our attempts to find a happy medium, we’re making the tough call to block this type of traffic permanently. While we’re sorry for the inconvenience this causes some users, this policy change puts us in a much better position to make Glitch more stable for everyone. 

If you currently rely on ping services for your project, know that your project or account won’t be suspended. They just won’t work any more as intended. Please email support@glitch.com if you have questions or are seeking advice about what to do with your projects.

Ping Services on Glitch

He also serves on the boards of the Electronic Frontier Foundation and the Data & Society Research Institute, and was formerly a contributing editor of WIRED. He’s been blogging since 1999 and won’t stop telling people about that one time he was on the Desus and Mero late-night show.

Incidents

The Workers Who Keep the Web Safe in an Unsafe World

Animal Crossing Helped Me Get Back to Real Life

New Rules of the Classroom: Remote Teaching in the Age of Covid-19

Better Tech: Why We Need Calm Technology Now More Than Ever

Function with Anil Dash

Open World is a fiction anthology podcast about how science and technology serve as a backdrop for imagining a better future, helping us envision the positive influence that science and tech can play in a real future. 

Open World is produced by Keisha "TK" Dutes and hosted by critically-acclaimed podcaster Rose Eveleth, for Glitch. By speaking to the pressing concerns of our times through love, friendship, community, compassion, and sustainability, the host will help listeners imagine new ways forward into a future that is less scary and more positive, and something we can start working on constructively.  

Open World launches weekly episodes in Spring 2020. Want to contact the show? Email youropenworld@glitch.com.

Open World

Shift Shift Forward is a podcast that showcases everything that makes Glitch the best place to create on the web. We’ll talk to some of our top creators, explore cool apps, and even hear from the people who work at Glitch!

Shift Shift Forward

From idea to code in seconds, build and learn alongside the most creative coders on the Web

Product Updates

You Might Also Like