Author Topic: telegram channel issue.  (Read 6357 times)

0 Members and 1 Guest are viewing this topic.

Offline JonnyB

  • Hero Member
  • *****
  • Posts: 636
    • View Profile
    • twitter.com/jonnybitcoin
I'm back.

Don't know why or how but I'm back.  Didn't do anything differently but it allowed me to join the group again. :-)
I run the @bitshares twitter handle
twitter.com/bitshares

iHashFury

  • Guest
https://telegram.me/BitSharesDEX

If anyone is having problems joining or sending messages in this group, please add a comment to this bug
https://bugs.launchpad.net/telegram-app/+bug/1612995
and contact
https://telegram.org/support
linking the issue
thanks

Offline Chris4210

  • Sr. Member
  • ****
  • Posts: 431
  • Keep Building!
    • View Profile
    • www.payger.com
  • BitShares: chris4210
I'm still locked out from the telegram group since it was turned in to a supergroup.

This is the error I get:

Method: messages.sendMessage
Url: N/A
Result: {"_":"rpc_error","error_code":400,"error_message":"PEER_ID_INVALID"}
Stack: Error
    at Object.h [as invokeApi] (https://web.telegram.org/js/app.js:23:25735)
    at Z.l.send (https://web.telegram.org/js/app.js:29:5996)
    at n (https://web.telegram.org/js/app.js:2:17056)

Have you tried to create a new Telegram account and log into the chat? Maybe you should contact the Telegram support what to do here? Ofc we want you back Jonny!!
Vote Chris4210 for Committee Member http://bit.ly/1WKC03B! | www.Payger.com - Payments + Messenger | www.BitShareshub.io - Community based fanpage for the BitShares Blockchain

Offline JonnyB

  • Hero Member
  • *****
  • Posts: 636
    • View Profile
    • twitter.com/jonnybitcoin
I'm still locked out from the telegram group since it was turned in to a supergroup.

This is the error I get:

Method: messages.sendMessage
Url: N/A
Result: {"_":"rpc_error","error_code":400,"error_message":"PEER_ID_INVALID"}
Stack: Error
    at Object.h [as invokeApi] (https://web.telegram.org/js/app.js:23:25735)
    at Z.l.send (https://web.telegram.org/js/app.js:29:5996)
    at n (https://web.telegram.org/js/app.js:2:17056)
I run the @bitshares twitter handle
twitter.com/bitshares

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
I got this earlier today:

Code: [Select]
Method: messages.sendMessage
Url: N/A
Result: {"_":"rpc_error","error_code":400,"error_message":"USER_BANNED_IN_CHANNEL"}
Stack: Error
    at Object.h [as invokeApi] (https://web.telegram.org/js/app.js:23:25735)
    at Object.Z.l.send (https://web.telegram.org/js/app.js:29:5996)
    at https://web.telegram.org/js/app.js:15:7420
    at t (https://web.telegram.org/js/app.js:13:2586)
    at a (https://web.telegram.org/js/app.js:15:17764)
    at g.$eval (https://web.telegram.org/js/app.js:13:12666)
    at g.$apply (https://web.telegram.org/js/app.js:13:12899)
    at HTMLAnchorElement.<anonymous> (https://web.telegram.org/js/app.js:15:17816)
    at HTMLAnchorElement.dispatch (https://web.telegram.org/js/app.js:4:2788)
    at HTMLAnchorElement.f.handle (https://web.telegram.org/js/app.js:3:31557)
BitShares committee member: abit
BitShares witness: in.abit


Offline JonnyB

  • Hero Member
  • *****
  • Posts: 636
    • View Profile
    • twitter.com/jonnybitcoin
After the bitshares telegram group got turned into a supergroup, I couldn't find it and still can't anyone else got this issue?

I run the @bitshares twitter handle
twitter.com/bitshares