pfp

I was really hoping this was about chemistry or biology...

Then again, 4 commits, 0 forks, 3 watchers... I don't really care what these people get their knickers in a twist about. Someone on the internet is offended, more news at 11.

Estonia has had electronic signatures since 2002. Cryptographically signed PDFs (or any files), backed by the government, free to use, and widely used by common citizens. All you need is residency (an ID card) and a cheap USB reader.

https://en.wikipedia.org/wiki/Digital_signature_in_Estonia

(yes, "free to use" means tax-funded, no need to point this out)

He's selling (up to A2 or so) prints via https://astroanarchy.zenfolio.com/ . Maybe you can contact him & ask for something larger.

Like I said, 14". They also make a 13" model.

Too bad all their products are limited to 1080p displays, even the 14" one that you can order with 64 (!) GB RAM. For me it's an immediate deal-breaker.

I'd really like to see this too.

Building a scanner would be interesting, but the mind-numbing idea of turning pages manually isn't very enticing

The latter. I don't care about buttcoins one way or another

> there's always going to be users

... that fit those predictable load patterns I mentioned.

Indeed. It should be common knowledge that shared platforms work because the company can make assumptions about load patterns and provision resources accordingly. Some might call that fair use, others overprovisioning.

Mining crypto under such a cost structure would force other users subsidize your buttcoins. Personally I wouldn't feel too happy about such an income transfer.

> transfer the costs to the customers (for example for excessive IO, energy consumption,...)

That would be fair, but enabling it might have costs beyond the plain consumed resources: io/cpu/etc schedulers that take the exceptional loads into account and mitigate performance impacts, metering and other business overhead, productisation, investments into all that, etc.

Don't negotiate. Dictate.

I'm not joking either. I tried negotiating this (pre-covid), only to get a "final offer" of a measly couple of remote days etc. Being on the spectrum, I took their word at face value, found another job that does 100% remote, and put in my resignation. Surprisingly that "absolutely final" position wasn't that final anymore, and they'd've rather had me remote than not at all. Had the new job not been a lot better substance-wise, the whole exercise would have been total waste of time.

Of course you'll want to dictate from a position where you can follow your ultimatum if need be.

The nearing end of Covid is where people like us can - indeed must - make a stand against the returning suffocating madness of boring commutes, noisy open plan offices, incessant context switches; against sacrificing one's creativity, flow and personal space to placate the emotional instincts and biases of the excessively social who rarely do the heavy lifting in our sector.

Stay determined and keep up the good work.

I would rather suggest not succumbing to self-censorship & chilling effects.

Though I find myself wondering whether a screenshot of a .mkv of a copyrighted film is really tactful for a Serious Project aimed at mainstream audience. Chilling effects again. Maybe the user just ripped his own DVD/BR for personal convenience.

Judging by the emoji characters in commit messages, it's impressive that even infants can write code nowadays.

SEEKING WORK | Remote, EU time | DevOps AWS Linux Go Python Systems | ~ 10h/week

  Location:  Amsterdam, Netherlands
  Remote:    Yes
  Tech:      AWS, OpenStack, EC2, ElastiCache, AWS in general
             CloudFormation, Terraform, Ansible, some Saltstack
             MySQL (clusters, HA, inhouse, RDS)
             PHP (-FPM), Nginx, Apache, HAProxy
             Go, Python
             Docker, Mesos, Chronos, Marathon
             Debian, CentOS, RedHat, Linux in general
             TCP/IP, iptables, DNS, SMTP, networking in general
  Languages: English, Finnish

DevOps / Systems / Backend Engineer with 20 years of experience in startups and on high traffic websites. I can help you with cloud automation, monitoring, scalability, performance and general operations related issues and also take on some small-scale Go, Python and PHP development.

My approach is pragmatic, conscientious and results-focused; I can strike the proper balance between continuity, cost and correctness depending on your present needs and constraints. I never compromise on stability or performance, unless expressly required.

I currently have about 10h/week available; I'm open to both short term assignments and longer, "slow burn" type projects.

https://www.linkedin.com/in/ppar

https://github.com/ppar

Email: pfp [at] iki [dot] fi

Exactly. They are ambiguous, increase visual clutter and not backwards compatible with older systems.

Even if they manage to convey a meaning, like the other poster said, that meaning is emotional instead of factual.

Why would anyone ever wish to express emotions in a commit message, or even in a business communications tool like Slack, is beyond my comprehension.

For personal communication they can serve a purpose, but that's not the topic here.

It's not nice to seem it work and I know exactly how I feel about them.

Originally Finland, currently working in a multinational based in Germany. Same experiences in both countries, I've never felt any "soft" pressure of the kind described in this thread that'd call for such legislation.

On call hours are controlled by legislation though, at least in Finland. Compensation for being on call isn't just "included in your regular salary"; employers are required to pay 50% (IIRC) on top of that just for the fact that you're able to work (read: sober and not innawoods) during a certain defined time period, and if you're actually called in, salary for the actual overtime hours worked. Obviously this gets pretty expensive for employers though so they tend to make optimal use of their on call people, but at least the rules are pretty clear.

I really, _really_ don't understand the constant fuss about after-hours email. It's not a phone call or an IM, it's mail. It's expected to be an asynchronous and a somewhat slow medium, and I've never encountered a workplace that expected immediate responses, let alone after hours responses at all. Maybe this is some US/Anglo specific issue?

Personally, I work at silly hours, from the afternoon til 2-4 AM. If I had to delay sending emails because of such odd sensitivity, I'd never be able to contact anyone in time. When I'm not at work, I'm not touching my work mail, IMs etc - don't even have them configured on my personal devices, so I don't get any notifications. Pretty simple IMHO.

Fully agreed. I tend to find non-native English speakers' accents more understandable than many native British or American accents, ironic as it is. Salvatore's accent is quite easy on the ears.

Same goes for a tendency of many native speakers to indulge in idioms, archaic vocabulary and convoluted syntax just for the heck of it. Non-natives just cut to the chase, which is exactly what you want in a technical discussion.