[deleted]
Remove “This incident will be reported.” from user warnings
261–270 of 302 posts
Re: Remove “This incident will be reported.” from user warnings
#262Guys. This commit was made Feb 3, 2022. Stop spamming the GitHub repo with dumb memes. It's not Twitter. The comments are for developer collaboration.
Re: Remove “This incident will be reported.” from user warnings
#263What does the "F" mean in the comments?
Re: Remove “This incident will be reported.” from user warnings
#264So, we're posting commits from almost 2 years ago as if they just happened today? Half of the comments in here can't tell it's an ancient commit; some people say celebrating saying "Glad they're finally doing this." What?
Bit ridiculous to see all the pointless spam/graffiti in the comments on that commit now.
Re: Remove “This incident will be reported.” from user warnings
#265Earlier quoted context omitted.
It always annoyed me that the Unix terminal subsystem is too dumb to handle multiple writers to the same terminal at once without them potentially corrupting each other’s output. There are some techniques to reduce the incidence of this but none of them are foolproof, whereas a better design could be. Maybe that was too hard when people used to use hardcopy terminals (actual ttys), although even there it possibly cou…
>Or, to avoid putting too much in kernel space, the tty subsystem could live in a user-space daemon On Unix, that's what "pseudo ttys" are for (i.e. /dev/pty*)! For example, that's how Emacs lets you run multiple shell sessions in sub-processes, such that they have full job control (i.e. ^Z and ^C works to interrupt or stop sub-processes in the shell, since they're handled by the TTY). That's also how xterm and the M…
> >Or, to avoid putting too much in kernel space, the tty subsystem could live in a user-space daemon
> On Unix, that's what "pseudo ttys" are for (i.e. /dev/pty*)!
No, that’s not what I was talking about. On just about every Unix, even with ptys, the line discipline code (or STREAMS modules for SysV-derived systems) still runs in kernel mode.
On Linux, you could implement something like what I was talking about with CUSE - have a character device which implemented the termios ioctls in a user-space daemon instead of in the kernel tty driver. That’s very different from how most Unix systems implement ptys
But what I was actually thinking about was a daemon which exposed over IPC an API a lot richer than termios. Something closer to curses.
Re: Remove “This incident will be reported.” from user warnings
#266Earlier quoted context omitted.
Then there was Jordan Hubbard's infamous "rwall incident" of March 31, 1987. It was waaaay more than just reported to the local sysadmin, and almost got UCB kicked off the ARPANET. https://en.wikipedia.org/wiki/Jordan_Hubbard#rwall_incident https://news.ycombinator.com/item?id=31822138 Jordan Hubbard wrote: "One of the people who received my message was Dennis Perry, the Inspector General of the ARPAnet (in the Penta…
So many acronyms
remarkably few, considering the organizations involved :(
Re: Remove “This incident will be reported.” from user warnings
#267Earlier quoted context omitted.
What does UUG stand for? That's the only acronym that ChatGPT didn't give me a guess for from your comment. The other guesses were: CDE - Common Desktop Environment, MTC - Missionary Training Center. GPT is much better than web search for this, I'll say that. It's ability to use context is invaluable.
This is an interesting example of the Clever Hans Phenomenon. You think you're comparing GPT and Google equally but you're actually giving GPT much more manual help. A search as simple as "UUG acronym" gives me the answer in a box at the top: "Unix Users Group" (tested in incognito). GPT is useful, but there's an annoying tendency of it's proponents to promote it with examples they haven't validated.
Interesting. The same search term returns "UUG is an acronym for: Uniface Users Group. Universal Underwriters Group." in the top box for me. Also in incognito.
Re: Remove “This incident will be reported.” from user warnings
#268Earlier quoted context omitted.
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 ARTIFICI…
I did a summer program at MIT around then and remember a program that let you send popup messages in xwindows to other users or to a channel. You could subscribe to any channel and use wild cards. I remember being hacked by someone to subscribe "*" and being unable to use my terminal for a while until i figured out how to unsubscribe without being able to see what i was typing under the wall of messages. I thought it…
You might be thinking of Zephyr, which was part of Project Athena. My school was using Athena, and I occasionally received zephyrgrams from people at MIT.
http://web.mit.edu/sipb/doc/working/izephyr/html/izephyr.htm... https://en.wikipedia.org/wiki/Zephyr_(protocol)
Re: Remove “This incident will be reported.” from user warnings
#269Earlier quoted context omitted.
Just because we’ve never seen him doesn’t mean he hasn’t at some point quietly summoned a curse on us
I am 100% sure I had some petty manually-initiated retaliatory action taken against me by a sysadmin at my university. I never heard a peep through any channel, official or otherwise.
You can't simply allow this many people to hang on a cliff that high!