Difference between revisions of "Glitch"
(git repos files from project.glitch.me URLs) |
(no .glitch-assets on project hosting) |
||
Line 23: | Line 23: | ||
Each project corresponds to a subdomain of ''glitch.me'', thus until July 8th 2025 it'll be possible to access projects via their subdomains. | Each project corresponds to a subdomain of ''glitch.me'', thus until July 8th 2025 it'll be possible to access projects via their subdomains. | ||
Each project is also a git repository which can usually be cloned by as anonymous users with the URL format <code><nowiki>https://api.glitch.com/git/PROJECT-SLUG</nowiki></code>, replacing PROJECT-SLUG with the actual project slug, e.g. <code>PROJECT-SLUG.glitch.me</code> or <code>glitch.com/~PROJECT-SLUG</code>. However, the git repositories do not include any uploaded "assets", nor databases or other data (typically stored under .data/), nor the .env file, among other things. However, the git repository may not be accessible for projects using outdated versions of Node, or suspended users. The files in the git repos can also be accessed at https://project.glitch.me/ URLs too. | Each project is also a git repository which can usually be cloned by as anonymous users with the URL format <code><nowiki>https://api.glitch.com/git/PROJECT-SLUG</nowiki></code>, replacing PROJECT-SLUG with the actual project slug, e.g. <code>PROJECT-SLUG.glitch.me</code> or <code>glitch.com/~PROJECT-SLUG</code>. However, the git repositories do not include any uploaded "assets", nor databases or other data (typically stored under .data/), nor the .env file, among other things. However, the git repository may not be accessible for projects using outdated versions of Node, or suspended users. The files (except <code>.glitch-assets</code>) in the git repos can also be accessed at https://project.glitch.me/ URLs too. | ||
Projects, including their git histories, usually include a <code>.glitch-assets</code> file, which is a [https://jsonlines.org/ JSONL] file enumerating assets uploaded to the Assets tab of that project (or a project's ancestor). The <code>url</code> and <code>thumbnail</code> properties of each object link to the CDN servers, which are usually on the domains ''cdn.glitch.global'', ''cdn.glitch.me'' or ''cdn.hyperdev.com'' for older projects. Only the latest version of the file needs processing, because file deletions just add a new item for the <code>uuid</code> with <code>deleted</code> set to <code>true</code>, and the old URL is still present and still works. | Projects, including their git histories, usually include a <code>.glitch-assets</code> file, which is a [https://jsonlines.org/ JSONL] file enumerating assets uploaded to the Assets tab of that project (or a project's ancestor). The <code>url</code> and <code>thumbnail</code> properties of each object link to the CDN servers, which are usually on the domains ''cdn.glitch.global'', ''cdn.glitch.me'' or ''cdn.hyperdev.com'' for older projects. Only the latest version of the file needs processing, because file deletions just add a new item for the <code>uuid</code> with <code>deleted</code> set to <code>true</code>, and the old URL is still present and still works. |
Revision as of 03:21, 30 June 2025
Glitch | |
URL | https://glitch.com/ |
Status | Closing |
Archiving status | Not saved yet |
Archiving type | Unknown |
IRC channel | #archiveteam-bs (on hackint) |
Glitch is a website where users can create web applications (projects) and share them.
It supports static, as well as dynamic websites though 11ty or NodeJS - the latter are only online for limited amounts of time every month.
Discovery
Users and projects can be enumerated using the API. Request these two URLs and continuously fetch the nextPage
field of the resulting JSON. Python scripts for that are available[1] [2].
https://api.glitch.com/v1/users/?limit=1000 https://api.glitch.com/v1/projects/?limit=1000
Archiving
Each project corresponds to a subdomain of glitch.me, thus until July 8th 2025 it'll be possible to access projects via their subdomains.
Each project is also a git repository which can usually be cloned by as anonymous users with the URL format https://api.glitch.com/git/PROJECT-SLUG
, replacing PROJECT-SLUG with the actual project slug, e.g. PROJECT-SLUG.glitch.me
or glitch.com/~PROJECT-SLUG
. However, the git repositories do not include any uploaded "assets", nor databases or other data (typically stored under .data/), nor the .env file, among other things. However, the git repository may not be accessible for projects using outdated versions of Node, or suspended users. The files (except .glitch-assets
) in the git repos can also be accessed at https://project.glitch.me/ URLs too.
Projects, including their git histories, usually include a .glitch-assets
file, which is a JSONL file enumerating assets uploaded to the Assets tab of that project (or a project's ancestor). The url
and thumbnail
properties of each object link to the CDN servers, which are usually on the domains cdn.glitch.global, cdn.glitch.me or cdn.hyperdev.com for older projects. Only the latest version of the file needs processing, because file deletions just add a new item for the uuid
with deleted
set to true
, and the old URL is still present and still works.
After the deadline, accounts will still be able to download their projects "through the end of 2025".
The https://glitch.com/@user and https://glitch.com/~project URLs use JavaScript, but might be archivable by hard-coding the behaviour of the page JS in a DPoS script. The https://project.glitch.me/ subdomains will mostly but not always use JavaScript, with individual domain JS behaviours being different, so not easily archivable.