• 0 Posts
  • 93 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • My condolences. And as much as I hate Posit/Workbench, some of that is on your IT department. If I’m reading your comment correctly, you’re having issues because it needs admin privileges to update some things, namely packages. That’s honestly a very simple fix, they just need to grant your user NTFS write permissions to the Rstudio/Workbench install directory locally (and maybe some registry keys, but that’s not definite). That’s it. It’s a 10-second permanent fix and no more UAC prompts for you.



  • What’s nightmarish about the installation? Is it because medical stuff is still on like Win XP?

    Anything more than the most basic bare-bones install of Workbench (formerly Rstudio) quickly turns nightmarish. Try setting it up on a Linux dedicated server with AD auth with auto-mounting of network shares per-user. Posit’s documentation isn’t great (or even agrees with itself across pages) even in the simplest best-case scenario, and if you deploy anything that’s even slightly complicated, it turns into a Hellscape. There’s a good chance you will end up on one of the Posit employees’ blog to read an incomplete explanation of setting up a feature because it’s entirely missing or incomplete in the documentation. This isn’t some crazy off-the-wall edge scenario either, it’s an (allegedly) supported configuration and would be a typical deployment scenario in a multi-user R environment.

    Their support is absolute shit too, it’s truly fucking atrocious. First-level support will not solve your issue, I promise you that, and you won’t get anyone who actually knows WTF they’re talking about until you’re escalated at least twice. And even then, they are very much up their own ass and have a VERY snobby attitude about the product, and always assume that it’s the user at fault, even when you provide absolute 100% proof that it’s their product at fault. It obviously couldn’t possibly be their Super Precious Perfect-in-Every-Way Golden God Product, because as we’ve previously established before, it is a Perfect Product Which Does No Wrong, Ever. They also love to try and shirk responsibility and say that X is not a supported configuration for literally everything, and then claim that the documentation must be wrong when you point out in their documentation that it is.

    Don’t even get me started on the Lovecraftian nightmare that is R package management. It’s even worse than the essay I just typed out, and they want to charge you essentially the entire Workbench license cost x2 to make it usable. Their logging is useless too, it has basically two settings, one of which is essentially “nothing,” and the other is “firehose of bullshit that you need to follow along in their source code to try to find anything useful.” That’s not an exaggeration, I actually had to do that to diagnose an issue and provide proof to them that yeah, it is your half-assed shit product that’s the problem.

    So yeah, if you’re not just Click-Click-Click-Next installing it, it very quickly becomes nightmarish. Posit desperately needs competition in the space, because they’re absolute shit, but they can be absolute shit with impunity since they don’t have any real competition.



  • tool@lemmy.worldto196@lemmy.blahaj.zonerule
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    8 months ago

    I have tinnitus with two different frequencies constantly blaring in my ears from target shooting and loud concerts sans ear protection.

    You’ll be able to tell the difference in a quality pair of headphones, trust me.





  • Before I replace it with something that won’t catastrophically collapse when the wind blows the wrong way, I get some sort of sick satisfaction out of doing autopsies on the house-built-of-matchsticks “solutions” that users come up with and I don’t know why. Some of them are truly fascinating and make you wonder how someone could possibly arrive at that conclusion based on what they were actually try to achieve.

    It’s also why if I’m asked to implement something, my first question isn’t “When does this need to be done?,” it’s “What exactly is the problem you’re trying to solve?”

    What a user asks for and what they actually need very rarely intersect.


  • tool@lemmy.worldtoGreentext@sh.itjust.worksAnon flies air Chad
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    8 months ago

    I literally cannot tell the difference.

    Source: am manager, and sometimes my underlings don’t toil hard enough in the PowerPoint mines.

    You should mercilessly berate them until morale improves, that’s MBA 101.

    You’re gonna be back in the PowerPoint mines if you don’t fix your soft-hearted attitude.





  • It would be better to our them on blast on social media since that sometimes gets the companies attention to try and fix PR.

    Works almost every time. I had a ticket with a vendor open at work for just about 3 months, and then only replies I’d gotten on the ticket was the “We’ve received your support request which we’ll promptly ignore!” autoresponse upon opening, and then another auto-response a month later saying the ticket was being assigned to another department. I’d replied to the ticket ~20 times asking for updates in that time.

    I finally got sick of essentially yelling into an empty room and called out the company, their marketing team, their support team, and their CEO on Twitter, making sure to @ each one of them in the message. I got a reply from their CEO and an actual human responded to the ticket less than an hour later.

    It’s shitty and a last resort, but it’s generally very effective.


  • I have a Hisense and had a similar experience. I was watching something fullscreen on an HDMI input, and then it suddenly switched inputs and showed a fullscreen firmware update prompt. I had no choice available other than to agree to update the firmware, no cancel button, couldn’t change inputs, nothing, the only choice was to update the firmware. So I unplugged the TV.

    About 10 seconds after I powered it back on, the exact same update prompt happened, still with no choice to decline it. I pulled power and booted it back up one more time just to be sure, met with the update prompt again.

    This made me very angry.

    The next time I powered it on, I had a packet capture running to see where it was phoning home. I created a firewall rule blocking all the hostnames it tried to connect to at startup, pulled the plug, and then booted it back up. No more update prompt, and it hasn’t happened again. Good thing they don’t download and pre-stage the new firmware, I guess.

    Let me know if you want the hostnames and I’ll PM them to you.



  • While on the topic, this isn’t how passwords work in systems.

    Passwords are stored as one way hashes. So it’s cryptoed only in one direction, it’s lossy, and can’t be recovered back to the original password.

    When you log on, your cleartext PW is hashed in ephemeral memory/storage and then the cleartext password is thrown away.

    That hash is compared to the hash in the DB. If the hash matches, then you have access. If it doesn’t, then your PW is incorrect.

    Oh my sweet Summer Child. This is definitely how it’s supposed to work, but there are plenty of services that just don’t know what the fuck they’re doing.

    Have you ever been on a site that has a stupid-low character limit for a password? There’s literally no reason to do that, all the hashes are going to end up the same size in the DB anyway regardless of the original string length. Even bcrypt’s max secret character limit is 70-something characters.

    Ever change a password and have it not work on the next login because they’re silently truncating it after a certain character limit? Ever get an email with an actual password in it?

    The only reason you would do things like this is if you’re storing/processing passwords in plaintext and not hashing it client-side first.

    I can think of 3 offenders of this off the top of my head. It’s a lot more common than you’d think.