I use a Reading List and file away anything interesting and then immediately close the tab. When I have time, I can go back and review all the things. In truth, I don't read most of them, but filing them away makes me comfortable to move on. If your browser doesn't have a Reading List, there are myriad extensions, you can also use Pocket, or even Evernote's web clipper. Use a couple of key tags - don't go overboard on tagging.
I also just focus on article content and ignore comments on all sites. Anyone can make a comment on a site, and there's no clear indication of authoritative comments vs amateur opinion, so they're largely a waste of time - there are lots of good comments, for sure, but I just don't have the time to wade through looking for them.
That might help for a certain subset of people in this scenario, but there are also people with subtle mental conditions that, while capable of living productive lives, are also unable to deal with MFA. There are also the elderly and non tech-literate.
Gmail is already a well-known spammer. Loads of spam come from Google, I see it everyday, by far the biggest source of spam I see. Unfortunately, they're also so big, with so many legitimate users, that you can't block them wholesale if you're expecting to deal with the public, many of whom have a gmail address.
Huge amounts of spam already originate from gmail addresses, so I don't think this is a good example. That's not to say that I think security should be weakened, though - it should not, but for other reasons.
You need to ask yourself why the company hired you in the first place. You might perceive yourself to be an equal, but as shitty as it is, most likely the company and your colleagues do not. They should, but they probably don't. The company looked overseas to hire you in the first place solely because you were cheap labor. If you were not willing to work for cheap, they would not have hired you at all, they would have hired a local instead or found someone else overseas who would work for much less. That's the unfortunate reality - it's not about you as an individual, it's not about what you do, it's about what you are to them - cheap labor.
Ask yourself, if the roles were reversed, why would you want to hire someone from the United States to work for your business wherever you are based? You'd probably prefer to hire locally. The only reason you'd start looking abroad is if there was some value in doing so, and that might be for cheap labor, or it might be that when selling product overseas you want a person local to that area selling to the people of that area because they might be more successful at selling than a foreigner.
This is not about the SF-based employees, this is about the roles the company has chosen to source in lower-cost regions. For whatever reason, they've decided that they are getting a lot of value out of local resources in SF, and some of that will be about being American, some of it about responsibility, some of it about liability and local laws that they can hold the employee to. When it comes to those roles they've based overseas, they've done for the sole reason of cheaper labor. If you stop being that cheap labor, they'll just hire someone else who is. If there is no cheap labor, then they'll hire a local in SF instead. It's really that simple, and I agree it's not fair - life isn't fair.
On the other hand, the only reason the company hired someone overseas was to save money. They would not have even considered these candidates if they weren't hugely cheaper. Instead, the company would have hired from the local labor market instead.
What the submitter should be asking themselves, is whether they can pull a higher wage working from their current location with any other company. If they can do that, they should. If they can't, and it's likely that they cannot because most companies are operating similarly, then they're getting a fair market rate for their situation. That's the free market.
Well, we agree that "cheaper labor" is desirable because it's more profitable to the company right? So let's apply transitivity to your first paragraph:
"The only reason the company hired someone overseas was to make more money. They would not have even considered these candidates if they weren't hugely more profitable. Instead, the company would have hired from the local labor market instead."
Yeah, what you are describing is practically the definition of exploitation of labor by capital, and alienation of the worker from the value they create.
> On the other hand, the only reason the company hired someone overseas was to save money. They would not have even considered these candidates if they weren't hugely cheaper.
Not the only reason: I have plenty of times hired people who had skills we needed and couldn't find locally. Sometimes brought those people over on H-1B, sometimes just hired them remote. And then if we had a few in the same area, opened an engineering office (though these days I am less likely to do that unless the folks really wanted it).
But it would be a great motivator if they actually bothered to relocate you in case you showed remarkable performance and added value to the company.
"We just want someone to work for cheap without prospect of progress" tells me that job will have a low ceiling for someone that wants to progress further their career
Certainly this sounds like an issue for you and your company, but I don't see why it is an issue for the project and its maintainers. Many companies enter into support contracts with vendors whose solutions they adopt to avoid this very problem. The solution seems simple to me, your company should seek a support contract with the vendor, and if that is not possible, find a different solution for which they can. It is unreasonable to expect anything, especially in a business sense, from anyone who you are not paying to support you.
Because this is an issue with 99% of the companies.
Don't forget you are here on HN with HN developers. 99% of companies will never seek support contract with vendors. That's the reality, developers have to deal with it and get over the struggle. Maintainer have to deal with it too because companies will never change (or at least not in the few months) and get over developers asking for help which have issues with their library.
I suspect the maintainers will just ignore these kinds of requests, rather than "get over" them. If you and your company want help, you'll need to pay for it. That's the reality. If your company won't pay for it, then you'll have to "get over" your app not working.
I also just focus on article content and ignore comments on all sites. Anyone can make a comment on a site, and there's no clear indication of authoritative comments vs amateur opinion, so they're largely a waste of time - there are lots of good comments, for sure, but I just don't have the time to wade through looking for them.