No, after Crimea, there was widespread expectation Russia will try to take more. Not least in Ukraine itself, which led to the military preparations there that have made it so expensive for Russia.
687 karma · joined October 4, 2018
But this is your outgoing email authorized by DKIM... an attacker can use it to take over most of your accounts via Forgot Password flow. I think it is a false economy to have that depend on a shared VM.
> would my custom domain be free from being marked by spam?
The receipient's mail service gets to choose if it thinks your email is spam, this will happen whatever your sending arrangements, outlook is not immune from sending spam and is no magic guarantee others will give it a free pass somehow.
Recipients score your email on a variety of characteristics, many of which are under your control. A major consideration is the sending netblock, eg, residential ADSL blocks are likely to be rejected or scored to hell. Garbage netblocks like linode with a terrible reputation likewise. A clean (no history of spamming) IP in a clean (reputable) netblock will be scored higher. You can look up sender reputations here, which is the service the big email providers use.
So to send your own mail, you should rent a dedicated server on your own IP, you can do this for $30/mo or so. All you need to run there is postfix + SASL auth to forward your (and only your) emails.
Then you must configure DKIM etc correctly and check your emails are validly signed, DKIM requires being able to add TXT fields to your DNS.
It's very possible to do this yourself securely after a bit of a learning curve and have it require minimal ongoing maintenance.
HN is full of 100% black or 100% white theses that are the equivalent of guerning youtuber clickbait. Most of it is true under some conditions and false under others... it would be better to put it that "Sometimes you have to pick if v1 or v2 of your api is more likely to kill your project".
You can trust your selfhosted infrastructure as far as it goes. But even then if the country you live in has laws that put you personally in a bad situation for providing services to some class of people - Iranians already went through all this - you too will take it down.
Same as Fedora, Debian seems to package linux-firmware?
Other firmware the cpu microcode is handled via packaging.
There has been a lot of work packaging peripheral firmware for things like mice... it's not like it is going to go away. This is also distributed in packaging in Fedora now.
It's not ideal that these are proprietary blobs but some accommodation is needed I think.
You were paid to write the code by these guys, they own the copyright and can do whatever they want with it. It is not "your code", you cannot "keep the code".
You should have insisted to simply get paid since nobody knows the future. I would take it from the rest of your story you will never see another cent of that from those guys since they stop working with you and "get another developer".
The best thing you can do is negotiate a cash fee only about the AWS handover task since the rest of it is already lost. Genuinely help them migrate, take the fee, and learn from this what not to do next time.
If you're a wageslave and it's really someone else's client, you have to discuss with your manager.
> The exchange rate is no longer free-floating and the currency would be at a very different level if barriers were removed.
So you should solve this by only working on work stuff using work devices, or, eg, ssh into your work box to do stuff from home.
Yeah... I read the article thinking, "these guys have no R&D".
What causes the most teeth grinding is when it is questions about their proprietary code. I don't care if their garbage never works! It's not going to help me or anyone else either way.
Yeah. And I eventually came to realize: lazy.
I agree it's confusing but it is what they called it. It's like an old Xilinx 2064 with a risc-V added on top, except the chip itself is OSSHW, not just the board.
sed s/metaverse/Second\ Life/g