04-23-2019
Update:
I wanted to add to the status post above.
A few long time team members (and very strong contributors) are not happy with me and have become inactive recently. The reason for this "unhappiness", in my view, is the fact that trying to manage difficult issues like retooling and remodeling a site like this requires more than just communicating via text messaging. The team members I talk with on the phone (by voice) on a regular basis and I do not have any misunderstandings. Misunderstandings often arise when people only want to communicate by messaging. Ultimately I have to make the changes the site needs. We cannot continue as "rusty, legacy forum". When we complete building out the new Live Chat and other new systems, I plan to disable the legacy infraction system forever.
Recently I bought a condenser mic so I could talk to people while working (taking a much need break from coding) and have been trying to talk to people by Skype, What's App or Line (by voice) more so there are less misunderstandings. Ravinder and I talk on the phone at least once a month and by chat often.
Recently one of our most beloved long time contributors left the site, who was someone I dearly loved, because I typed something like " we need to bring in new moderators and not only have the "old guard" moderators" , which I thought at the time was a kind of endearing term, since I'm also getting as old as dirt myself and like to make fun of the fact we are all getting older and need to be more accommodating and responsive to the needs of the younger generation(s).
If we had of been talking on the phone, everyone would have heard my voice and laughed, but instead, text messaging caused people to misunderstand each other and get emotional. Text messaging does not work. The leadership team must be willing and happy to talk on the phone, and often. Later this year, I may disable the current private messaging system and use a variation of the new chat features I'm building now.
This is the problem when we are making big changes. Text messaging. I am really getting disappointed to see how people are so set on living in a "text only" world. Text is cool; but we also need voice communications.
Moving forward, I want to build a closer community of forum leaders This means we will seek new team members who are willing to talk on the phone one-on-one or in small groups (because the time zone differences are too huge to conference all at once), and who will work with users in Live Chat (or something similar as we evolve) and who fully support our changes as we modernize the forums.
Today, in Live Chat a new member told me we had the best forum on the net and he loved the "dark mode" and our Live Chat support. That same user told me he had never had any site respond to him like we did today using the new Live Chat area.
This is our future.
Responsive, mobile savvy, new member focused.
This User Gave Thanks to Neo For This Post:
5 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I believe i have most of samba configured right but i get this error each time time try to run it. I was given suggestion that i touch the file, i did, but i still cannot rid myself of this error.
Any suggestions (2 Replies)
Discussion started by: macdonto
2 Replies
2. Red Hat
I have successfully installed RedHat 8.0 onto a Dell PowerEdge SC1425 today. This server has two SATA hard drives, and an IDE DVD-ROM drive.
Using the following kernel parameters, i successfully installed across both hard drives from CD:
ide0=0x1f0,0x3f6,14 vga=791 resolution=1024x768 expert... (5 Replies)
Discussion started by: fishsponge
5 Replies
3. What is on Your Mind?
I have been wondering how do Systems Administrators do the jump into Systems Engineering? Is it only a matter of time and experience or could I actually help myself get there?
Opinions? Books I could read?
Thanks a lot for your help! (0 Replies)
Discussion started by: svalenciatech
0 Replies
4. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
5. Programming
Dear Team
I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update )
Scenario
We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
Discussion started by: Perlbaby
1 Replies
TALK(1) BSD General Commands Manual TALK(1)
NAME
talk -- talk to another user
SYNOPSIS
talk person [ttyname]
DESCRIPTION
Talk is a visual communication program which copies lines from your terminal to that of another user.
Options available:
person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on
another host, then person is of the form 'user@host'.
ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal
name, where ttyname is of the form 'ttyXX' or 'pts/X'.
When first called, talk contacts the talk daemon on the other user's machine, which sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to that user. At this point, he then replies by typing
talk your_name@your_machine
It doesn't matter from which machine the recipient replies, as long as his login name is the same. Once communication is established, the
two parties may type simultaneously; their output will appear in separate windows. Typing control-L (^L) will cause the screen to be
reprinted. The erase, kill line, and word erase characters (normally ^H, ^U, and ^W respectively) will behave normally. To exit, just type
the interrupt character (normally ^C); talk then moves the cursor to the bottom of the screen and restores the terminal to its previous
state.
As of netkit-ntalk 0.15 talk supports scrollback; use esc-p and esc-n to scroll your window, and ctrl-p and ctrl-n to scroll the other win-
dow. These keys are now opposite from the way they were in 0.16; while this will probably be confusing at first, the rationale is that the
key combinations with escape are harder to type and should therefore be used to scroll one's own screen, since one needs to do that much less
often.
If you do not want to receive talk requests, you may block them using the mesg(1) command. By default, talk requests are normally not
blocked. Certain commands, in particular nroff(1), pine(1), and pr(1), may block messages temporarily in order to prevent messy output.
FILES
/etc/hosts to find the recipient's machine
/var/run/utmp to find the recipient's tty
SEE ALSO
mail(1), mesg(1), who(1), write(1), talkd(8)
BUGS
The protocol used to communicate with the talk daemon is braindead.
Also, the version of talk(1) released with 4.2BSD uses a different and even more braindead protocol that is completely incompatible. Some
vendor Unixes (particularly those from Sun) have been found to use this old protocol.
Old versions of talk may have trouble running on machines with more than one IP address, such as machines with dynamic SLIP or PPP connec-
tions. This problem is fixed as of netkit-ntalk 0.11, but may affect people you are trying to communicate with.
HISTORY
The talk command appeared in 4.2BSD.
Linux NetKit (0.17) November 24, 1999 Linux NetKit (0.17)