tl.js.org

[ankit-chaubey]

• There is reasonable content on the page (see: No Content)
• I have read and accepted the Terms and Conditions
• The site content can be seen at https://telethonian.github.io/tl-differ/ and source https://github.com/Telethonian/tl-differ inside gh-pages branch.

👋🏻 Hello,

I would like to request the subdomain tl.js.org for my project, TL Differ (Type Language Difference Finder).
This tool helps track changes in Telegram's Type Language (TL) schema by identifying newly added definitions and modifications in existing ones.

The project is a fork of an existing tool, and this version will be actively maintained with new content and improvements.

• GitHub Repository: https://github.com/Telethonian/tl-differ
• Live Website: https://telethonian.github.io/tl-differ/

I believe tl.js.org would be a simple and intuitive subdomain for this tool.
Please let me know if any further information is needed.

Thank you for your time and consideration!

[ankit-chaubey]

should works fine now..:))

[ankit-chaubey]

Done ✅

[indus]

@ankit-chaubey I looks more like a python project and not so much JS related?!? Am I missing something?
Besides that I would expect to be named tl-differ.js.org to meet the name that is used in the repos...

[ankit-chaubey]

It's a Type Language viewer that displays changes in the Telegram API, including additions, removals, and replacements, for all 201 layers. Users can view these details and utilize the API methods in JavaScript, Python, or any other programming language.

This website is primarily built with JavaScript, while Python is used for scraping, updating data, and making modifications via the terminal. The repository contains HTML and Python code for managing data.

As you mentioned, tl-differ is the website’s heading, designed to quickly highlight differences between previous and current layers. However, the project also provides a comprehensive view of all 201 layers, including their API data, keys, and new updates. Future layers will be added sequentially, making it more than just a comparison tool—it serves as a complete Type Language stuff.

The tl-differ code will be organized under the tl folder, with structured layer data (tl-layer-1, tl-layer-2, ..., tl-layer-201...n). Each layer will include its description, methods, and type language details, making it a full-featured package for TL, not just a differencing tool.

I hope this clarifies everything. Looking forward to your response regarding tl.js.org. Thank you!

[indus]

A lot of pages use JavaScript as a technological driver but that doesn't make them related to JavaScript...
@MattIPv4 do you have another opinion?

[ankit-chaubey]

Are JS.org subdomains only for websites built entirely with JavaScript for javascript? Or can they also be used by sites that primarily deliver information using JavaScript technologies, such as those that compare different APIs layers, track changes, and analyze additions or removals?

For example, a website that processes Type Language (TL) data from Telegram’s MTProto API (https://core.telegram.org/mtproto/TL) using JavaScript—allowing users to compare layers, view layer contents, and analyze modifications—would it qualify for a JS.org subdomain?

Just to clarify, TL is a data format used in Telegram’s official MTProto APIs, mainly for defining and processing structured data.

Note: Python and sell codes used in repository is primarily for extracting information and pushing to github! my website is entirely in JavaScript.

[MattIPv4]

Are JS.org subdomains only for websites built entirely with JavaScript for javascript? Or can they also be used by sites that primarily deliver information using JavaScript technologies, such as those that compare different APIs layers, track changes, and analyze additions or removals?

Whether a website uses/is built with JavaScript or not is not really a factor -- what we care about is wether the content is relevant to JavaScript developers and the JavaScript community or not, more-so than any other community.

[MattIPv4]

@MattIPv4 do you have another opinion?

I don't see how this is relevant to the JavaScript community particularly -- it seems to just be a report on generic API changes in Telegram.

Also... it is an unmodified fork of https://github.com/Lonami/tl-differ which is already hosted at https://diff.telethon.dev/ for anyone to use -- I don't see why an identical copy needs to be hosted on a JS.org subdomain.

[ankit-chaubey]

Are JS.org subdomains only for websites built entirely with JavaScript for javascript? Or can they also be used by sites that primarily deliver information using JavaScript technologies, such as those that compare different APIs layers, track changes, and analyze additions or removals?

Whether a website uses/is built with JavaScript or not is not really a factor -- what we care about is wether the content is relevant to JavaScript developers and the JavaScript community or not, more-so than any other community.

It’s certainly not limited to JavaScript developers or the JavaScript community. It’s for any developer interested in using MTProto to build a Telegram client, regardless of the programming language—whether it's JavaScript, C++, Python, or any other. In fact, a JavaScript library for this already exists.

[ankit-chaubey]

@MattIPv4 do you have another opinion?

I don't see how this is relevant to the JavaScript community particularly -- it seems to just be a report on generic API changes in Telegram.

Also... it is an unmodified fork of https://github.com/Lonami/tl-differ which is already hosted at https://diff.telethon.dev/ for anyone to use -- I don't see why an identical copy needs to be hosted on a JS.org subdomain.

If you check the commit history of both repositories, you'll see that I pushed updates to both, including the one that hadn't been updated. My commit has also been merged. So, in any case, it won’t be an identical copy but will be based on the primary project, which is a fork.

[MattIPv4]

So, in any case, it won’t be an identical copy but will be based on the primary project, which is a fork.

At present, they are identical copies.

I do not see why we would accept a request for content that is seemingly not related, and is already hosted elsewhere. Feel free to re-request a JS.org subdomain once your fork is clearly different from the existing hosted version, and is relevant specifically to JavaScript developers.

[ankit-chaubey]

I do not see why we would accept a request for content that is seemingly not related, and is already hosted elsewhere.

"already hosted somewhere" is for the project on which it's based not for my modification, additions, or further improvements.

Anyway, this isn't just about pushing and making changes to the script—I’ve already made numerous modifications to this fork (local repository), with changes in more than 10 files. many of them are already built, but I was waiting for my commits with fixes to be merged before releasing my updates, which I’ve been working on and am interested in.

main point (about my website): It’s certainly not limited to JavaScript developers or the JavaScript community. It’s for any developer interested in using MTProto to build a Telegram client, whether they use JavaScript, C++, Python, or any other language.

I'll look for another service. Thank you!