for some context, there was a bug where the cookie wasn't being set properly. so it's likely you were logged in and the incorrect cookie value was set, and logging out and back in fixed it.
sorry about the delayed response to this, but just to clear out any confusion, we (lemmy.ca) don't have our own app or apk to download. i'm guessing that you probably just added a home screen shortcut to our website possibly?
anyways, as others have said, there's a bunch of different lemmy apps for android, there's a nice overview of them here, and you can filter by various things, etc: https://www.lemmyapps.com/
i would recommend against any of the discontinued apps, however.
hey! thanks for the offer to help. feel free to offer to help mod any communities, and if there's any local communities here that look unmoderated, let us know! that would be a good start.
i'm just guessing at this point, but if you send just the login command to the bot, it sounds like it should give you some options on how to login? what are the options it gives you in response, if anything? and have you tried any of them?
Telegram officially discontinued registration from 3rd party clients as of 2023-02-18, so support for it was removed in v0.13.0 of the bridge. You should sign up using a mobile client and then log into the bridge.
so not sure if that's the issue you're running into (the timing matches up, anyways).
i've never used the telegram bridge myself, but i have other bridges running successfully.
😂 while I appreciate it, i want to give credit where credit is due. shadow does 99% of the infra work, and mp3 and otter were instrumental in getting the non profit setup. i just help out where I can!
while we are happy that you're willing to help spread the word around about us, we would recommend just getting to know the site and the users and the community a bit more before getting too involved in promoting the site. thanks though!
for some context, there was a bug where the cookie wasn't being set properly. so it's likely you were logged in and the incorrect cookie value was set, and logging out and back in fixed it.