You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 25, 2023. It is now read-only.
I have one own Telegram app (currently for other purposes/bots), does this mean I have to insert my credentials?
In the telegram settings it is written that I am now allowed to give my hash to third parties but the config file is public.
The implementation I am using is not a real fork, as it is the original source from this repo (mirror) with just an additional legal hint in the footer.
regards,
Till
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
first thank you for the project.
I have one question about the js/lib/config.js:
`/*
IMPORTANT NOTICE
Do not publish your Webogram fork with my app credentials (below), or your application may be blocked.
You can get your own api_id, api_hash at https://my.telegram.org, see manual at https://core.telegram.org/api/obtaining_api_id.
*/`
I have one own Telegram app (currently for other purposes/bots), does this mean I have to insert my credentials?
In the telegram settings it is written that I am now allowed to give my hash to third parties but the config file is public.
The implementation I am using is not a real fork, as it is the original source from this repo (mirror) with just an additional legal hint in the footer.
regards,
Till
The text was updated successfully, but these errors were encountered: