ImTO1 to F-Droid@lemmy.mlEnglish · edit-26 months agoMercurygram | Telegram FOSS with UnifiedPush support.f-droid.orgexternal-linkmessage-square6fedilinkarrow-up154arrow-down11file-text
arrow-up153arrow-down1external-linkMercurygram | Telegram FOSS with UnifiedPush support.f-droid.orgImTO1 to F-Droid@lemmy.mlEnglish · edit-26 months agomessage-square6fedilinkfile-text
minus-squareImTO1OPlinkfedilinkEnglisharrow-up3arrow-down1·edit-26 months agoUnifiedPush is a key feature and not the only one. You can read more about it on its github repository: https://github.com/drizzt/Mercurygram UnifiedPush was suggested to Telegram FOSS about 2 years ago. But it didn’t happen until now: https://github.com/Telegram-FOSS-Team/Telegram-FOSS/issues/577
minus-squarebizdelnick@lemmy.mlcakelinkfedilinkarrow-up3·6 months agoThere are also forkgram, nekogram x, whatevergram… I use negkogram x, in particular, and I don’t want to switch to another fork to get unified push but losing other features. I guess forkgram users also stick to its features. Etc.
UnifiedPush is a key feature and not the only one. You can read more about it on its github repository: https://github.com/drizzt/Mercurygram
UnifiedPush was suggested to Telegram FOSS about 2 years ago. But it didn’t happen until now: https://github.com/Telegram-FOSS-Team/Telegram-FOSS/issues/577
There are also forkgram, nekogram x, whatevergram… I use negkogram x, in particular, and I don’t want to switch to another fork to get unified push but losing other features. I guess forkgram users also stick to its features. Etc.