Telegram Desktop Talk

13 July 2025 06:04

That's when HAL (Project Treble) was introduced

Telegram Desktop Talk

13 July 2025 05:55

Interesting! I run LineageOS too, albeit official but not a GSI image. My platform is OnePlus 6T (fajita). However, I also remember the stock OxygenOS to be quite a bit more bloated... I think it's just down to OnePlus having not spent as much effort as they should on the software side. Maybe it was even an omen into what eventually became a split into RedMagic for engineering, and the skeletal remains of OnePlus for the bean counters. I'd imagine GSI to be Pixel-exclusive, but perhaps it was a similar story with Google's official firmware still?

Telegram Desktop Talk

13 July 2025 04:47

Sorry for not having considered it, I should have... Out of curiosity, which ROM(s) was/were that/those? I've only built Android from source once, and quickly steered clear from it since. 200GB of SSD storage and 32GB RAM are things I have, but wasn't willing to give. But there's that, as well as an enormous amount of differences between different ROM vendors... Could that be attributed to memory management alone? There's only a handful of custom ROM vendors I consider good enough to be one of my daily drivers, notably Pixel Experience and LineageOS.. and things are getting worse, with Google's current activities. Perhaps we could consider those devices in terms of arm32 / aarch64 programs built over ADB / Termux, ... But can we extend that to system-level usage as a whole?

Telegram Desktop Talk

13 July 2025 04:38

I just told you a story of a 64 bit phone ROM consuming so much more ram that the ram becomes never enough lol

Telegram Desktop Talk

13 July 2025 04:27

It has only 2 GB of RAM iirc

Telegram Desktop Talk

13 July 2025 04:25

Pointer size is a thing...

Telegram Desktop Talk

13 July 2025 04:21

Gotta say though, Telegram Desktop's memory usage on my Windows session is nothing short of incredible — only 60MB! I remember it being way more on Linux, easily 10x that much. That would leave me wondering why that is so... Are there shared memory segments that are just part of Windows itself, that Linux doesn't provide, or are not implemented there?

Telegram Desktop Talk

13 July 2025 04:13

Heh, true. I remember someone not too long ago, that mentioned how Telegram Desktop consumed too much memory on their 6GB system. I guess in that kind of situation, even a couple hundred MB is a lot... Makes me wonder to which extent it's reasonable to want more applications to run at once, without investing in a better system. Probably there's some supply-demand curves involved there... Not to mention people's individual ability to get a given computer system, within their own life constraints. To which extent do we wish to cater to that, what is reasonable for those systems that are not our own?

Telegram Desktop Talk

13 July 2025 04:08

Different people claim that resource consumption is high and low at the same time xd

Telegram Desktop Talk

13 July 2025 04:05

I mean, one of the reasons why I joined Telegram in the first place, was because of such performance considerations. Put it next to the competition of WhatsApp, Discord, Slack and such, and Telegram comes out as a winner on just about all of them. Memory demands being low, meaning that it can easily live in the system tray while not in active use. Instant delivery so that anything time-sensitive is not delayed. Open development platform that allows people to integrate it with just about any third-party application we desire. It's a bit of a "gazing at the sky" point, I'll admit... But I'd like Telegram and its clients to stay that way. This is just a reminder of that I guess.

Telegram Desktop Talk

13 July 2025 04:00

Honestly just to keep system restrictions in the back of our heads while writing and/or building the software for our users. People like you and I may have copious amounts of resources on our systems, but that does not mean that our users have it too. Chances are that they don't. That's the kind of thing that the ATtiny chip reminded me of tonight. That even compared to an Arduino Uno, both the "system architecture" and the system resources are way different. I think that is the case with contemporary PC systems too. Something like an Atom or a Pentium or such, with 4GB memory and eMMC for storage, let's say. I don't think that the systems commonly used in development are even in the same league, even if the architecture is technically the same. What that gives us is a common build target, but not much more than that... I like reducing myself to the lowest common denominator, as well as considering it as a foreign system that I can make no assumptions about. It makes for better design.

Telegram Desktop Talk

13 July 2025 03:46

If I may, I would add another suggestion here: maintain focus on performance and compatibility. I remember making a launcher for Telegram Desktop, that would copy the tdata directory into a tmpfs before launching the client, then write the results back to disk when Telegram Desktop would close (both graceful and on crash, it was a wrapper). That taught me that Telegram Desktop can run on 32-bit x86 hardware, just needs a little bit of help with cache, just like e.g. Firefox does. It's a matter of compilation and library mess that makes it unattractive, especially with me being one of 5 people who still cares about that architecture. But it is an interesting exercise, and that's half the reason I still maintain that system.

Tonight, I experienced that again when migrating my wristwatch code into an ATtiny85, coming from Arduino Uno and Mega. The ATtiny85's system requirements are.. 8kB of storage, and 512B of memory. And more importantly, 8 pins total. The pins are all in use, while the storage and memory are at 3854 bytes (47%) and 218 bytes (42%) respectively. In addition, none of the libraries I used previously work on the ATtiny85. Serial had to be done in software, same for I2C to the display module. And there's not enough pins for the both of them.

That introduces some hard limits, as well as some soft ones. Soft limits as in, the hardware for serial and I2C just isn't on that chip. But it can be done in software, I believe people call it bit-banging. And hard limits in that serial and I2C can't run together, and require rewiring. Not only that, but I2C seems to want the reset pin, which is mandatory for reprogramming. That really throws a wrench into development, requiring both rewrite and a serious pondering about whether I even want to drive a display with these, at least until the very end of this project.

But both of those things can likely still be done, even at that level of restriction. It just takes effort, and for it to be worth doing. For me, that is worth doing, I will be wearing that thing on my wrist for the foreseeable future, counted in years or even decades. Whether that is worth it for Telegram Desktop.. I don't know. But I want it to be so, even if only as a design principle.

Telegram Desktop Talk

12 July 2025 21:15

00:18

Disappearance of messages in some supergroups

#bug
#tgdesktop


windows 10
V 5.16.3 X64

Telegram Desktop Talk

12 July 2025 19:41

I do think an inappropriate assumption of admin access was made, but I doubt it for "tele team".

Telegram Desktop Talk

12 July 2025 19:38

By someone I meant Dan.

Telegram Desktop Talk

13 July 2025 06:03

GSIs could be installed on any device coming with Android 8 and later

Telegram Desktop Talk

13 July 2025 05:44

Lineage OS GSI from Andy Yan

Telegram Desktop Talk

13 July 2025 04:39

The difference should be 2x though, not 10x

Telegram Desktop Talk

13 July 2025 04:35

Now that you mention it, maybe... Granted, could pointers be that capable of increasing memory usage alone? I'm not familiar with heap management and pointers yet (it's one of the things I appreciate the most about Arduino, that it's C-like but not by that much), but so far I consider integers to be the foremost format, and then things like char to be formatted derivatives of those. I guess a float could also be encoded as an extension of an int? Just needs a decimal point and a +/- sign really. So pointers to a 64-bit value in a 32-bit system.. couldn't you just assign twice the amount of a 32-bit dword (I think Windows encodes it as qword?) and call that as part of a core library like windows.h? It would increase the memory by a little bit, sure.. but only for pointers, and only up to double at most. Or am I missing something?

Telegram Desktop Talk

13 July 2025 04:27

I remember a phone very lagging on a custom ROM... It was an arm64 ROM while the factory ROM was a64 (32-bit userspace with 64-bit kernel). After installing a custom a64 ROM, it started to work better than with the factory ROM.

Telegram Desktop Talk

13 July 2025 04:24

The biggest difference could be that you use a 32 bit build on Windows while a 64 bit build on Linux?

Telegram Desktop Talk

13 July 2025 04:20

I feel like the resource optimization is commonly of unimportance for many devs. “Hardware is too powerful” now and can keep up. Maybe they think there is now need. 🤔 🤷

Telegram Desktop Talk

13 July 2025 04:12

schrodinger's memory consumption

Telegram Desktop Talk

13 July 2025 04:07

That's kind of 'there's only two genders' meme

Telegram Desktop Talk

13 July 2025 04:01

So you have nothing concrete in mind?

Telegram Desktop Talk

13 July 2025 03:53

I've read the message but not sure what do you ask for after all 😅

Telegram Desktop Talk

12 July 2025 21:17

Disappearance of messages in some supergroups 00:18

#bug
#tgdesktop

windows 10
V 5.16.3 X64

Telegram Desktop Talk

12 July 2025 21:15

00:18

Disappearance of messages in some supergroups

#bug
#tgdesktop


windows 10
V 5.16.3 X64

Telegram Desktop Talk

12 July 2025 19:39

Does "tele team" insinuate employment? Or was an assumption made regarding it?

Telegram Desktop Talk

12 July 2025 19:38

Make no mistake, I have at no point insinuated direct affiliation like employment. What I do acknowledge is an elevated level of access that most of us — including both you and me — don't have.