Recommended Posts

Colorado man Joe Lobato was fired after posting a status update complaining about work. Joe told KUSA 9News that he was feeling severely sick on the job.

Lobato said it was so bad that, "It felt like someone was kicking me in my stomach."

He went on to say that his supervisor?s response to his illness was less than sympathetic, reporting, "He told me I wasn't allowed to leave my machinery again."

At his computer, Joe logged in to Facebook and vented, posting a 9-sentence status update that included the statement, ?Guess they think a person is a machine and can?t get sick.?

Joe?s co-worker/friend reported the post to their boss, which led to Lobato?s termination for ?gross misconduct? and posting negative comments about the company on a public forum.

The National Labor Relations Board says that while employees have the right to discuss work conditions on Facebook, employers can take action against worker rants online.

Further, social media experts warn that nothing is fully private in the online space.

Now Lobato knows this all too well and says the online rant was not worth it as he is about to lose his house.

Joe would like to hire a lawyer to fight for his job back, but cannot afford one.

At a recent hearing with his former employer, he was told that his firing was justified.

source & video

Link to comment
https://www.neowin.net/forum/topic/1151308-man-fired-after-facebook-post/
Share on other sites

NEVER EVER befriend your coworker in any social network unless you don't work there anymore.

Just do what I do, make lots of imaginary friends on facebook. The only real friend I have on facebook is my dog, and even then I have to guess what he wants his status updates to be, as he can't type with hits paws :(

On a more serious note, managing your settings on the site you're using is probably going to be better then alienating your co-workers. Either make a fake account to let them spam you with cute pictures of animals and chain mail posts, or on your real account and stick them in a category that they can't see your regular post.

Some people can't entertain the idea that you're not using a social networking site, and telling someone you don't have a facebook account is actually a lot of effort (even if you don't actually have one).

We don't know the context his "friend" told his boss about the comment.. His friend could have been doing this out of concern..

Secondly, if your job makes you feel like that, you need to find another job asap.

Also, I agree with others, Don't work with friends and don't be-friend someone at work unless you no longer work there..

People should have the right to vent if they want to.

Sure, but you don't went on a public forum. employers have no right to keep employees who are not happy with being where they are or who write crap about them in public. if you want to vent, do it ina pirvate diary or to a friend.

Employers should have no right to pry into what we do in our private lives full stop. You wouldn't tolerate an employer putting a hidden mic in your home so why should we tolerate them snooping on our Facebook accounts? If this post was private and another employee had to show it to the employer, it means the employer was snooping on something they hadn't been given consent to access. The fact that it's the Internet doesn't automatically give companies elevated rights to snoop on your private affairs.

Employers should have no right to pry into what we do in our private lives full stop.

This is the only part of your post I need to read.

Facebook is NOT private.

Hence:

Sure, but you don't went on a public forum. employers have no right to keep employees who are not happy with being where they are or who write crap about them in public. if you want to vent, do it in a private diary or to a friend.

That's bullcrap. Facebook's TOS only give them access to your data, if you set your profile to private and people snoop on it without your permission they ARE violating your privacy.

That's bullcrap. Facebook's TOS only give them access to your data, if you set your profile to private and people snoop on it without your permission they ARE violating your privacy.

Sorry but, the FB TOS means bullcrap to your employer. and even if you set it to private, you're still posting it publicly online. and if other people can see it, your employer can see, it if not directly indirectly. If you have a private FB with just your 2-3 best friends sure, but you're still doing it at your own risk, posting it on a public internet forum.

use your head or lose your job. simple. just like you don't tell your next employer at the interview why you quit or got fired from your last job if you want the job.

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!