Live data from Hacker News

Remove “This incident will be reported.” from user warnings

github.com

211–220 of 302 posts

Re: Remove “This incident will be reported.” from user warnings

#211

Earlier quoted context omitted.

Strong agree on that. One person doing so was possibly amusing, everyone else jumping on the wagon is just irritating noise, and I’m not even responsible for trying to sift through that for legitimate feedback.

The point of the joke is that it's a bandwagon joke.

I disagree that it's a joke, because they're absolutely nothing funny or clever or original about it, but you're right that the point is to jump on a bandwagon, and it's intentionally ironically disrespectful of everyone's time and attention, which is also the point. It's really just a spammy childish 4chan troll.

All Due Respect: Press F for Farce. Recently, Call of Duty: Advanced Warfare became roundly mocked when images showed a funeral event where the player is asked to “Press [F] to Pay Respects.”

https://www.gamedeveloper.com/design/all-due-respect-press-f...

>On the other hand, Call of Duty forces the player to Pay Respects for the game to proceed. It’s a mission objective just like any other, complete with an interactive reticle floating above the coffin. Furthermore, it’s embarrassing to ask the player to take this action explicitly. This is a military funeral! What else would you do, blow a raspberry? It’s no wonder players feel insulted.

Ludonarrative Dissonance:

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

>Ludonarrative dissonance is the conflict between a video game's narrative told through the story and the narrative told through the gameplay. Ludonarrative, a compound of ludology and narrative, refers to the intersection in a video game of ludic elements (gameplay) and narrative elements. The term was coined by game designer Clint Hocking in 2007 in a blog post.

Re: Remove “This incident will be reported.” from user warnings

#212
post #60

Earlier quoted context omitted.

It's a low-effort addition to the dialogue, but it is a legitimate communication of a viewpoint. Who gets to draw the line of which comments should be nuked? (My view, the repo owner should (and maybe already has that power))

Why would somebody care about low effort dialog more than a year after the commit?

And my question to the github management is why can't any registered user report any low effort useless or offensive comment to the moderators, whoever they may be, like almost every other online discussion group outside of 4chan?

Re: Remove “This incident will be reported.” from user warnings

#214
post #143

Earlier quoted context omitted.

There's the talk command on Unix. We used to do a 'who' to find out who're on the system and 'talk' to them.

That was such a mind blowing experience coming from a DOS background. It would split your terminal horizontally and you could see each other type in real time. Before the days of SMS, and even before the days of instant messengers like ICQ and AIM, I taught the split-screen `talk` command to my girlfriend so we could chat while I was working. We've been married for 20 years now.

Long before Unix talk, ITS (the Incompatible Timesharing System at the MIT AI Lab) had a program called UNTALK, written by a user named UNCOLA, that supported split screen text chat, back around 1992 or earlier.

Incompatible Timesharing System:

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

Getting Started Computing at the Al Lab by Christopher C. Stacy. MASSACHUSETTS INSTITUTE OF TECHNOLOGY ARTIFICIAL INTELLIGENCE LABORATORY WORKING PAPER 235 7 September 1982:

https://dspace.mit.edu/bitstream/handle/1721.1/41180/AI_WP_2...

>6.10.3. TALK

>If you want to link to someone who is on another ITS machine, you can use the TALK program. The program is run by typing:

>*:talk uname@host

>To exit TALK terminating the conversation, the user who initiated TALK must type ^C.

>This method of comlinking is less versatile than the backnext commands, and only works across ITS machines (not locally).

>Another useful comlink program is UNTALK. UNTALK is similar to TALK but does not work across machines. However, on a display terminal, UNTALK splits the screen horizontally and allows the two people to type at the same time on their part of the screen.

The "backnext commands" he referred to would actually let you not only perform a text chat link (albeit not split screen), but also take over another user's TTY, to type into and see the output of their DDT shell and programs. There was no security other than obscurity on ITS, and that feature of linking to and sharing another user's TTY was meant for collaboration, helping, and teaching people, and also initializing and configuring output-only serial devices like line printers.

History of the Net is Important, by Keith F. Lynch:

http://www.ais.org/~jrh/acn/ACN8-1.pdf

>[...] ITS stood for the Incompatible Time-sharing System, an obvious take-off on CTSS, the Compatible Time-Sharing System. (Just as Unix is a take-off on the earlier TENEX, TWENEX, and MULTICS.)

>All four ITS machines also had UNTALK, a split-screen conferencing program similar to the later “talk” on Unix and PHONE on VMS. I was told it was written by a user whose ITS username was UNCOLA and who had committed suicide. I don’t know if it was the first program of that type, but it was the first I had seen.

Even before that, ARPANET TIPs supported a low level way of text chatting (not split screen) called a "TIP to TIP Link" (documented on page 5-4 of the "Users Guide to the Terminal IMP") where each participant bounced their packets off of a port on some host, without actually logging in or going through the host.

https://news.ycombinator.com/item?id=13518273

Users Guide to the Terminal IMP (1975):

https://archive.org/details/bitsavers_bbntipADA0eTerminalIMP...

Re: Remove “This incident will be reported.” from user warnings

#215
post #184

Earlier quoted context omitted.

Schools are supposed to be the place where students can break things and break rules. It's part of the education.

learning that if you get caught you're going to be held accountable for your actions is also part of the education. it's not as if they executed OP. telling a kid to stop screwing around is pretty reasonable.

During college in the mid 2000s I discovered that the network share with all corporate data was accessible (read only) to everyone.

The only way it was not immediately obvious was because only sub folders were assigned a drive letter, and the network share was hidden in the UI. I found a way around that in the Windows open dialog and then was able to trigger Explorer to the top level directory.

The share also contained private data of applicants (names, addresses, date of birth, education history) which was most concerning to us.

With some friends we wrote a document showing what we found (not explaining how to do it) and posted it to an internal message board. We also sent copies via email to our IT teacher, sysadmin and the principle. Shortly after the sysadmin invited us for a chat and basically told us not to do that again.

A couple of hours later we were invited to the principles office. The principle was away at the time, but the vice principle - who wanted to make a name for himself - immediately suspended us all and said he'd discuss it with the principle but said most likely we would be expelled, and they may need to involve the police.

Our main concern in the post we made was that personal data was effectively publically accessible (to anyone who connects to ethernet - you didn't even need to log in). Even before GDPR, our country had very strong data protection laws which this would have breached.

A few days later a parent sent a letter to the principle, effectively restating what we said, with added threats of reporting them for violating data protection of minors. Strangely after that the issue was dropped and we were allowed back...

Re: Remove “This incident will be reported.” from user warnings

#216
post #137

Earlier quoted context omitted.

I once entered 'sudo echo hi" or something similar on a large HPCC and received an email back from a sysadmin that just said "hello".

That's an amusing anecdote, though I find it bothersome the sysadmin failed to correctly implement the echo command

Someone turned up the temperature hyperparameter.

Re: Remove “This incident will be reported.” from user warnings

#218
post #143

Earlier quoted context omitted.

There's the talk command on Unix. We used to do a 'who' to find out who're on the system and 'talk' to them.

also wall(1)

Nothing beats walling the undergrad project server.

Re: Remove “This incident will be reported.” from user warnings

#219

Why are we changing things that aren't broken? Did this message trigger some snowflake?

Per the commit message:

> Whether or not sudo sends email is now configurable, so the warning may not be accurate. It is also confusing to the user since they will not know who the incident is being reported to.

Re: Remove “This incident will be reported.” from user warnings

#220
post #137

Earlier quoted context omitted.

I once entered 'sudo echo hi" or something similar on a large HPCC and received an email back from a sysadmin that just said "hello".

That's an amusing anecdote, though I find it bothersome the sysadmin failed to correctly implement the echo command

I find it bothersome that the "yes" command outputs "y" by default instead of "yes". False advertising! Since Unix loves short concise command names, why not just name it "y"?
Post reply on HN