3 ms·

While I'm unsure about the inability to join calls, I can at least agree that the Linux client is terrible. I finally caved a few months ago, got an account, a

by i336_ 11y ago

While I'm unsure about the inability to join calls, I can at least agree that the Linux client is terrible. I finally caved a few months ago, got an account, and started using it ("oh wow it handles 's/woops/fixed/', that's awesome")... until the client began freezing, chewing 100% CPU for as long as I patiently left it running, and not getting itself sorted out. Removing ~/.Skype (XDG, anybody?) and re-signing in worked... for about 3 minutes, at which point my profile data re-synced, and the client began choking again. Last I tried the Web-integrated version (Skype icon, top-right of outlook.com et. al., takes a minute to become clickable) I couldn't even type "/me ..." - the line would send verbatim. At that point I gave up completely. I used to use IRC but I find it too Spartan nowadays, but on the other hand I don't want to have to remember what chat tab is in what window, and I can't handle the idea of running 15 isolated instances of Webkit for all the separate chat systems out there, so that kills websites and most current "desktop" chat clients. I don't use the Internet to communicate much, somewhat ironically. Everything drives me to distraction. Notes: - XDG: TL;DR = says stuff should be in ~/.config, ~/.cache, etc. https://wiki.archlinux.org/index.php/XDG_Base_Directory_support https://wiki.archlinux.org/index.php/XDG_Base_Directory_supp... - I cannot help but admire the reverse-engineering going on at https://github.com/EionRobb/skype4pidgin/tree/master/skypeweb#skypeweb-plugin-for-pidgin https://github.com/EionRobb/skype4pidgin/tree/master/skypewe... to make the outlook/skype web integration programmatically consumable. I have no idea how it works but the commits are very recent, which is a big positive sign.

lucaspiller 11y ago
> until the client began freezing, chewing 100% CPU for as long as I patiently left it running, and not getting itself sorted out. The same happens for me on iOS and OS X quite often. I disabled mobile data and push notifcations on iOS as it sucked up tonnes of data (I've seen 30MB/day even when I haven't opened the app), and repeated or delayed notifications. Whenever I open a conversation I have to leave it 30s - 1 minute until it updates with the latest messages.
- i336_ 11y ago
  ooh wow. I have to admit, searching for "skype 100% cpu" or similar shows lots of people having this problem on Windows and OS X, so I wonder if I'm not just seeing disasterousness in a shared part of the codebase. I never even touched the mobile app though; 30MB/day is insane. Wow...
masklinn 11y ago
> XDG: TL;DR = says stuff should be in ~/.config, ~/.cache, etc. XDGBDS is such an unstandard even xdg-utils doesn't care for it. And Skype predates XDGBDS (let alone whatever the current version of XDGBDS is this week). Also you're wrong, XDG doesn't say stuff should be in specific directories, it defines envvars specifying directories with various defaults, defaults which are at best only correct on Linux distros which purport to follow XDG, which you can't test for because XDGBDS didn't see fit to define a way to say it.
- i336_ 11y ago
  > XDGBDS is such an unstandard even xdg-utils doesn't care for it. :o, TIL > And Skype predates XDGBDS (let alone whatever the current version of XDGBDS is this week). Of course, but that's no real excuse for it not to get with the times. > Also you're wrong, XDG doesn't say stuff should be in specific directories, it defines envvars specifying directories with various defaults, you are of course right; I overly-condensed my TL;DR. Those are the default directories, yes, but it defines XDG_CONFIG_HOME (~/.config), XDG_CACHE_HOME (~/.cache), etc. > defaults which are at best only correct on Linux distros which purport to follow XDG, which you can't test for because XDGBDS didn't see fit to define a way to say it. Another TIL... and that's just crazy. What about OS policy being that "all shell environments shall be supplied with stock configuration that defines the XDG environment envvars as a sign of compatibility and compliance"? Keep them at ~/.config et al., just define them - because if they're defined, that indicates the environment is very likely to be sanely configured (for (stereo)typical values of "sane").
  - ars 11y ago
    > Of course, but that's no real excuse for it not to get with the times. It is a very good excuse: Backwards compatibility with older installations. I suppose it could have two search paths, but why add complexity?

by i336_ 11y ago

lucaspiller 11y ago

> until the client began freezing, chewing 100% CPU for as long as I patiently left it running, and not getting itself sorted out. The same happens for me on iOS and OS X quite often. I disabled mobile data and push notifcations on iOS as it sucked up tonnes of data (I've seen 30MB/day even when I haven't opened the app), and repeated or delayed notifications. Whenever I open a conversation I have to leave it 30s - 1 minute until it updates with the latest messages.

i336_ 11y ago
ooh wow. I have to admit, searching for "skype 100% cpu" or similar shows lots of people having this problem on Windows and OS X, so I wonder if I'm not just seeing disasterousness in a shared part of the codebase. I never even touched the mobile app though; 30MB/day is insane. Wow...

masklinn 11y ago

> XDG: TL;DR = says stuff should be in ~/.config, ~/.cache, etc. XDGBDS is such an unstandard even xdg-utils doesn't care for it. And Skype predates XDGBDS (let alone whatever the current version of XDGBDS is this week). Also you're wrong, XDG doesn't say stuff should be in specific directories, it defines envvars specifying directories with various defaults, defaults which are at best only correct on Linux distros which purport to follow XDG, which you can't test for because XDGBDS didn't see fit to define a way to say it.

i336_ 11y ago
> XDGBDS is such an unstandard even xdg-utils doesn't care for it. :o, TIL > And Skype predates XDGBDS (let alone whatever the current version of XDGBDS is this week). Of course, but that's no real excuse for it not to get with the times. > Also you're wrong, XDG doesn't say stuff should be in specific directories, it defines envvars specifying directories with various defaults, you are of course right; I overly-condensed my TL;DR. Those are the default directories, yes, but it defines XDG_CONFIG_HOME (~/.config), XDG_CACHE_HOME (~/.cache), etc. > defaults which are at best only correct on Linux distros which purport to follow XDG, which you can't test for because XDGBDS didn't see fit to define a way to say it. Another TIL... and that's just crazy. What about OS policy being that "all shell environments shall be supplied with stock configuration that defines the XDG environment envvars as a sign of compatibility and compliance"? Keep them at ~/.config et al., just define them - because if they're defined, that indicates the environment is very likely to be sanely configured (for (stereo)typical values of "sane").
- ars 11y ago
  > Of course, but that's no real excuse for it not to get with the times. It is a very good excuse: Backwards compatibility with older installations. I suppose it could have two search paths, but why add complexity?