Hacker Newsnew | past | comments | ask | show | jobs | submit | chrisperkins's commentslogin

> emergency dispatchers should not expect this from callers

Why should emergency dispatchers not expect a civil working environment?

I do not condone the response of the emergency dispatcher here but I genuinely want to know why an emergency dispatcher must be required to withstand hostile behavior as part of their job?


"emergency" rather definitionally indicates that "not normal" or "out of the ordinary" situations are occurring. For most callers, this may be the worst day of their lives - emotion/stress/danger/death/etc.

They're not required to interpret a caller's phone voice as 'hostile' either. Unless the caller actually says something like "I'm going to come find you and kill you or your family" or something along those lines, I don't think there's any reason anything a caller says should be interpreted as 'hostile' to the dispatcher. If they're agitated/upset - well... they're having an emergency.

Should medical staff not expect "sick people" in their office/hospital?

Someone who can't handle someone yelling or swearing on the phone should't be in a dispatcher role, and... yeah, I think it's gotta be stressful for them too, and they probably shouldn't do it a whole lot, as they'll burn out quickly.


To this - surely this would be part of any psychological testing done to screen dispatchers for suitability, no?


I would draw parallels here (though it's nowhere near in scale) with:

* firemen often risking their lives approaching (and sometimes entering) buildings in fire. It's a hostile environment, but it's their duty, whether they are paid or not (volunteer firefighters).

* policemen answering a call in a dangerous/hostile neighbourhoods (or just roaming). It's hostile environment, but it's their duty to be of service there.

Compared to the above, expecting dispatchers to emotionally detach and not take anything said personally is a smaller ask, in my opinion.


> why an emergency dispatcher must be required to withstand hostile behavior as part of their job

Emergencies make people stressed. Stressed people often curse.


Why? Because impoliteness shouldn't be punishable by death.


That's what I was thinking ... "I don't care that (you/your wife/you child) is dying, call back when you can keep a civil tongue in your head."


Also the one dying is (usually) not the caller.


“But why should I object to that term sir,” she says. “See, in our century, we’ve learned not to fear words.”


Can we do vertical splits in screen without having to install additional plugins? How?



> As a ruler. Want to know how big something on your screen is in pixels? Fire up an xlogo, line it up with one edge of the thing, resize until the opposite edge lines up too, and if your window manager puts up a tooltip during window resizing (which I think all the ones I've ever used do), then you know the size.

I don't see a tooltip that shows the window size. I am using Xfce.


Yeah, I wondered about that too. I remember older, traditional window managers like TWM, FVWM, OpenBOX, etc. show this but most newer "Desktop" environment's window managers like XFCE's and Gnome's do not.

Interestingly when sizing a terminal window these WM's show the size in columns and rows and when sizing a "real" window it shows the size in pixels.

Probably an option somewhere to turn it on in newer environments but it's been a while since I used anything but cwm[1] (which does show the window size on resize) so I can't be sure.

[1] calm window manager - https://en.wikipedia.org/wiki/Cwm_%28window_manager%29


> Interestingly when sizing a terminal window these WM's show the size in columns and rows and when sizing a "real" window it shows the size in pixels.

IIRC there's a window property the app can set on itself to tell the WM of its "resize increment", as well as a "base size". Since the main use case for that is terminal windows (anything that displays fixed-width text), I think most WMs assume that anything with that set on it cares about rows and columns rather than pixels.


Are you using cwm on OpenBSD or on something else? (Just curious.)


OpenBSD is where I discovered it and started using it. First on a laptop that I use to install Beta's and then a few machines at home.

I use a Slackware box at work and was delighted when I found a Linux port[1], now I use it everywhere except on Windows.

[1] https://github.com/zenlinux/cwm



> Being a client-server application, it allows to run its backend on the remote machine and connect to it from your local Emacs (or Vim, if you must, with SLIMV).

I have used Slimv and found it quite enjoyable on Vim. Has anyone here tried Vlime? Has anyone tried both? Which one of the two do you recommend?



I have been using Xfce for 5 years and it never disappoints me. Light, minimal, and very customizable. I hope it does not undergo radical change at the cost of performance just for the sake of redesign that many other desktop environments have gone through.

I still have 15 year old hardware lying around in my home and they come to a stall while running some of the desktop environments that have modernized themselves. But Xfce continues to run fine on them. It would be great if Xfce remains the way it is for another 15 years so that my old hardware continues to work for me.


Congratulations on your product launch! I am not your potential customer but as a fellow software developer I would like to know the technology/programming languages driving your product if you don't mind.


Thank you!

It's Clojure + ClojureScript, using a view library called Rum :).


Wow! I love Clojure. Unfortunately never got to use at work and of course never built anything serious with it.

Would you like to share more about your experience building a live product with Clojure? Did you face any challenges due to the smaller community and smaller set of libraries compared to something mainstream like Python or Go?


I love it :)!

I've built products with Python, Ruby and Node before and Clojure has been super fun!

Not missing anything particular. Since it has interop with both Java and JS you can often find libraries if you like to.


awesome


Can someone explain what the GitHub org and GitHub repo for https://github.com/moscow-technologies/blockchain-voting is about?

If this was about to be used for elections, shouldn't such a critical piece of software have more developers working on it? Why is there only one contributor to the whole project? Why does it have only 37 stars? Is this project well known among the citizens?


This is a small pilot project, it will be run in just a few districts of Moscow for municipal elections this September. Also, as of now, only about 1% of the population of those districts have registered for online voting, around 500 people.

So it's more like a proof of concept, and a first step in making larger-scale electronic elections possible in the future (from technological, political, organizational, and public trust standpoints).


I can translate the README:

> This repository contains the code for electronic voting that will be used for Moscow City Parliament elections.

> Purposes of creating this repository

> The repository was created to allow examination of a source code. Although the purpose of the system is electronic voting, we ask to leave comments and open issues only on technical questions. All comments containing political statements will be deleted.

But the code is incomplete. For example, PHP code looks like a "module" for a larger CMS and cannot be run independently. Also, here [1] there is a header that says "prototype" in Russian. And in several files where there should be the rules and explanations for users there is just a placholder, for example in this file [2]. So I assume this is just an early version of code.

This code was published as a part of a challenge to break the encryption used in remote voting.

There is no git history probably because this is just a snapshot, github is not used for development.

[1] https://github.com/moscow-technologies/blockchain-voting/blo...

[2] https://github.com/moscow-technologies/blockchain-voting/blo...


A translation of another README from here [1]

> Testing cryptographic strength

> Data for testing are in the following directories:

> - data - contains randomly generated data set for applying encryption keys

> - keys - contains encryption keys

> In the beginning of every day, the `data` folder will contain a file with encrypted data and `keys` folder will contain a public key. The task is to decrypt the data in time that is equal to voting duration - 12 hours.

> 12 hours later, original data will be published in the `data` folder and `keys` folder will contain a private key.

[1] https://github.com/moscow-technologies/blockchain-voting/tre...


They likely published to GitHub after it was finished


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: