🤠 Everyone is welcome to ask and answer 😌 Please be nice 🗣 Let's use English so everyone can participate 😳 Keep media posts like GIFs and stickers to a minimum 🤖 Don't add bots to the chat More Info - t.me/TelegramDesktopTalk/7
Hi I' wondering if i'ts posible to communicate with a signal use through
Читать полностью…😂 When I click on links of the 🤒 form /channel/keralajs/20463/26116 TDesktop 5.15.4 crashes ☠️ #bug 👽 😤 Crashed with this link 👍 🎉
❌ Clicking on 😮💨 message link does not crash if I use 5.12.3 👺
🫡 Does not crash on links of the 🤡 form /channel/TheForum/289/1290 😮
what do I know what's causing that error message. it's not like telegram doesn't obfuscate the real reasons for server-related behavior elsewhere!
Читать полностью…what do you mean? doesn't error say that it's "currently unavailable"?
Читать полностью…or they are moving to grok translation or something
Читать полностью…I guess something irreplaceable must have caught fire or exploded with the translation service
Читать полностью…https://x.com/telegram/status/1938311068679606595
Читать полностью…I mean sure, but doesn't that just suggest an if..else block for it on the server?
Читать полностью…Undefined behavior is bad and exceptions will trickle further down, so it's good that it was considered at the time
Читать полностью…If there's an error message it means they probably care and are aware of it?
Читать полностью…hello, desktop chat! what are we upto? anything new and interesting?
Читать полностью…Used to crash, doesn't crash anymore after fetching the message
Читать полностью…Now that you mention it… Could be yeah, considering those previous mentions by Durov that he and Musk would pursue further collaboration. Hopefully it’s not a precedent to “move fast and break things”, but I suppose it’s not an easy change either…
Читать полностью…it still tells you that it's temporarily unavailable
Читать полностью…which basically means it's temporarily offline
Читать полностью…I don't need to know the reason but what bugs me the most is that if it wasn't for other users I wouldn't even know that the problem is caused by something server-side
Читать полностью…maybe they ran out of credits in their google console
Читать полностью…i am sure telegram have backups of everything, and multiple copies
Читать полностью…At least they're aware of and working on it, that's good... Hopefully it's nothing too bad. But something like this is what I'm imagining. Reject incorrect input (inner else), and fail gracefully / perform read-only behavior for everything else. Project is still proprietary, so screenshot only and all rights reserved.
Читать полностью…It's that else, do this in every other condition, that I imagine this to be in for when a connection to a translation service fails or such
Читать полностью…All apps are showing the same, and it's not related to the clients
Читать полностью…Eh, I'd imagine that to be more of a "people like Preston cared about it when it was implemented" kind of thing
Читать полностью…no message from telegram about this either
Читать полностью…are translations disabled for anyone else or just me?
Читать полностью…There is another thing I would like to talk about, and that is "unused RAM is wasted RAM". Generally it gets me quite violent, I'll refrain from that here. But as someone else replied, that "unused" RAM goes to filesystem cache. And that's orders of magnitude faster (both in bandwidth and latency) than even a premium NVMe drive.
Every PC has CPU cache, RAM, and storage. Those are tiered, in the hopes that the data you want is always as close to the CPU as possible. So that unused RAM that holds cache, is actively making your system more responsive — by a long shot. Even RAM runs circles around any storage media available today. You can make exceptions to that, e.g. contemporary SSDs have reached the bandwidth of DDR(1) RAM (~300MB/s). Maybe NVMe has reached DDR2 by now, not sure but it seems reasonable. But I hope it conveys the orders of magnitude difference that these media have.
There is another way that this argument became prevalent in my watch project. It seems easiest to pick either 8MHz with internal RC (default), or 1MHz for the ATtiny85 chip. At 1MHz the chip would spend about 80-96% time active. Not only is it too close to 100% (limiting expansion and even tuning), but it also negates the power savings that 1MHz would normally be chosen for. 4MHz seemed like a good trade-off, even if that means that 75% of that time would be "wasted". As with everything in engineering, it's a trade-off. And those tend to be a lot more complex than just "not using resource X for purpose Y means it's useless".