Hi! I'm at the cafe, thanks for meeting up with me to discuas the new round of funding. Look for me under the guy just jorkin' it.
Chana
There was fog in so many places. You don't even know.
"The waters" is still a common way among Christian nerds to refer to the deluge, i.e. God's most famous genocide. But only among the worst nerds.
So muddy it makes you think of dinosaurs.
I'm a good writer.
I know a Maoist "anti-imperialist" group that shows up "in solidarity" with US weapons contractor workers when they go on strike. They just show up and say, "unions are great" and then go home.
Israeli spokespeople were calling it antisemitic before anyone had heard of a manifesto. It's a knee-jerk hasbara.
Hexbear lionization of adventurism isn't allowed until we have sufficiently pathologically sexualized him.
This is entirely expected but I would guess that this kind of confirmation is valuable for pushing forward any bureaucracy that could respond.
Remember when "the adults in the room" actively denied that SARS-CoV-2 could be spread by aerosol and they were telling you to not buy masks and to instead disinfect your produce?
That's good! And good to focus on union affiliation questions early. It will determine how much support you get during the campaign and some unions are so bad at this as to be counterproductive while others will send you a ride or die comrade.
Relationships with management often result in surprising "changes" when you try to unionize. Companies are top-down dictatorships. Except in extremely rare circumstances, the reaction will come from the top and filter down through management, who will need to choose between losing their job and engaging in union-busting: sharing information (perhaps naively) with their own "superiors", stalling, helping build anti-agitprop, and eventually firing organizers. Smart companies will try to leverage personal relationships to undermine the campaign, "sure they fired KatySosa, but the guy who announced it is such a nice person and they said it was for performance reasons. That guy has us over for parties and I've met his kids! He wouldn't do anything for a mean reason."
You should go into any unionization campaign expecting to be fired and for your coworkers to need to strike / do walkouts for your resinstatement. Are your coworkers ready to do that? I don't mean to discourage, the advice I'm giving is meant to increase your chance at success. You want to build up with structure tests and a committee before showing your hand or the compsny will just fire you and kill the campaign early through this intimidation.
I haven't checked but if you're the person who got active in part with PSL support I think it should be noted that they are not a known quantity in labor organizing. They might be more interested in radicalization than a successful campaign, e.g. suggesting agitprop before building a committee or a list (list building is always step 1! Always!). Or PSL mighy just be naive.
Others already have good recommendations for the provider so I will add some other notes.
First, please note that with the way DNS works, your home IP will now be recognizable as "the IP this domain points to" so make sure the chain of networking devices are secure, starting at your router. At minimum make sure the router firmware is up to date. The only way to avoid this kind of thing is to have a VPS as an intermediary, essentially a tunnel, though there are fancy new ways of making tunnels more powerful, like self-hosting tailscale-like services. But that has its own security downside, which is trusting the VPS provider. I think a DNS entry for your own home IP is generally better in terms of security vs. time invested but the VPS can be made theoretically superior by being careful with cryptographic strategy.
Second, yes you can, generally speaking, forward external requests on a given port to a local network IP and port. This is a decent way to slightly obfuscate ssh. By default it is port 22, so instead of opening 22 externally, you make some high-number (like 55342) port externally route to a server on port 22 locally. When sshing externally you just specify the high number port. Your router firmware may limit how well this works.
Third, yes the IP changing can cause DNS problems. You can set up a dynamic DNS service that changes your DNS records if your router external IP changes. If you run router firmware like OpenWRT the router itself can run this service. But you can also run dynamic DNS on a local server and have it do the same thing. Using a provider with a good API like porkbun makes this easier.