Client/server telnet text editor?

[Spartrekus]

Hello,

Would you have ever heard of a client/server telnet text editor ?

Since terminal and telnet has been used, this software for the console/terminal might be surely existing.

With best regards,
Sp.

 

[SirDice]

Would you have ever heard of a client/server telnet text editor ?

Simple question, why? What's the point?

Since terminal and telnet has been used, this software for the console/terminal might be surely existing.

What issue/problem would this solve? Almost all applications are born out of some sort of necessity. What's the need that would warrant the existence of such an application that can't be solved with existing tools?

 

[D-FENS]

What do you mean with "telnet text editor"? There is a console text editor and telnet provides you with a console. So you can run any console text editor in telnet - vi, nano, ee, emacs or whatever you prefer.
I have not heard recently anyone using telnet for anything else than testing TCP connections. It's completely unencrypted and it should be used at most on the localhost interface.

 

[Spartrekus]

1) Run a server to edit a text file.

2) clients use the old good telnet to connect and work on same doc.

In 1969 was dev of telnet. It might be quite a good number of years, so it must exist.

 

[SirDice]

1) Sorry? Why would I need to run a server to edit a text file?
2) Telnet has been deprecated a long time ago due to its inherent insecurity. Barely anybody uses it nowadays.

In 1969 was dev of telnet. It might be quite a good number of years, so it must exist.

So, after 50 years it still doesn't exist. Don't you think that's a clue your "solution" might be wrong? Do you really think you can do better than 50 years worth of the world's brightest and most innovative people coming up with ideas?

 

[Spartrekus]

1) Sorry? Why would I need to run a server to edit a text file?
2) Telnet has been deprecated a long time ago due to its inherent insecurity. Barely anybody uses it nowadays.


So, after 50 years it still doesn't exist. Don't you think that's a clue your "solution" might be wrong? Do you really think you can do better than 50 years worth of the world's brightest and most innovative people coming up with ideas?

who care about security?

There are computer scientists, not only web developers.

 

[SirDice]

who care about security?

The whole world, except you apparently.

 

[D-FENS]

1) Run a server to edit a text file.

2) clients use the old good telnet to connect and work on same doc.

In 1969 was dev of telnet. It might be quite a good number of years, so it must exist.

There are far superior tools for working on a common text file than telnetting and editing a file on the server. Just use git, subversion or any other version control system. It will help you merge and resolve conflicts instead of overwriting each other's work without history log.

 

[D-FENS]

2) Telnet has been deprecated a long time ago due to its inherent insecurity. Barely anybody uses it nowadays.

As remote shell - no. But it's great for testing out server sockets and protocols. I use it mostly to validate that a specific server is accessible and the firewall does not block it.

 

[shkhln]

Just use git

Spartrekus actually refuses to use git.

 

[Spartrekus]

Spartrekus actually refuses to use git.

I install only what is not needing too much dependencies or that is not touching user data privacy and spying tool/machines, such as Cloud Microsoft, Apple, Facebook, Google... Subversion for instance is better.
Support *Free* Opensource, just use free opensource.

There are far superior tools for working on a common text file than telnetting and editing a file on the server. Just use git, subversion or any other version control system. It will help you merge and resolve conflicts instead of overwriting each other's work without history log.

Who care about GIT? This is for developers.

 

[Spartrekus]

The whole world, except you apparently.

You are wrong. Telnet still exists, like Unix does.

There are many people still using telnet for large non-public research and computer sciences, behind highly secured network infrastructure(s). Those are usually very specific use, which can not be generalized to larger usage/public/audience.

 

[rufwoof]

tmux is good for cli based collaboration. Multiple participants ssh into the same box and userid and one starts tmux, the others attach to that session. Open vi or whatever text editor you like and you can all type into the same document(s). Obviously some control is needed to avoid 'fighting' for control at the same time. You can detach and leave the session running, and later reattach again from the same or another location/device.

Public telnet is predominately just for old bbs's nowadays. Or for other 'fun' asci art type things such as telnet towel.blinkenlights.nl (Star Wars)

 

[Spartrekus]

tmux is good for cli based collaboration. Multiple participants ssh into the same box and userid and one starts tmux, the others attach to that session. Open vi or whatever text editor you like and you can all type into the same document(s). Obviously some control is needed to avoid 'fighting' for control at the same time. You can detach and leave the session running, and later reattach again from the same or another location/device.

Public telnet is predominately just for old bbs's nowadays. Or for other 'fun' asci art type things such as telnet towel.blinkenlights.nl (Star Wars)

vi cannot allow two clients simult. on a single buffer.

 

[rufwoof]

vi cannot allow two clients simult. on a single buffer.

Log into a box and run tmux. You, or another, log into that same box and userid and run tmux attach

You both share the same tmux terminal session and either of you can open vi, type text in ... and the other can take over typing at any time.

Just tried it myself to confirm that's the case with vi.

 

[Spartrekus]

Log into a box and run tmux. You, or another, log into that same box and userid and run tmux attach

You both share the same tmux terminal session and either of you can open vi, type text in ... and the other can take over typing at any time.

Just tried it myself to confirm that's the case with vi.

Strange method, while network exists today.
Try to type on line 1: and line 5000: at same time on same latex doc...

 

[kpedersen]

vi cannot allow two clients simult. on a single buffer.

To be fair, I am more than fine with that. This kind of multi-user collaboration is a "cloud" gimmick and not actually that practical for real work.

For real work we have many VCS systems (i.e svn, git, cvs) available to merge text.

 

[Spartrekus]

To be fair, I am more than fine with that. This kind of multi-user collaboration is a "cloud" gimmick and not actually that practical for real work.

For real work we have many VCS systems (i.e svn, git, cvs) available to merge text.

In your world, but you may eventually see that people can have various jobs and computer usages for other areas.
Your world is your unique own world, your work, experiences and patterns.

 

[rufwoof]

Strange method, while network exists today.
Try to type on line 1: and line 5000: at same time on same latex doc...

Doesn't work that way, unless two of you were battling to enter text at the same time. In effect you're both using the exact same vi session so either keyboard can enter commands/text. If one is jumping to line 5000 whilst the other is entering text then you'd end up with a random outcome.

 

[Spartrekus]

Doesn't work that way, unless two of you were battling to enter text at the same time. In effect you're both using the exact same vi session so either keyboard can enter commands/text. If one is jumping to line 5000 whilst the other is entering text then you'd end up with a random outcome.

The program can calc where the cursor shall be, depending to type at same place.

 

[tommiie]

Spartrekus actually refuses to use git.

Yet he does use git and github. He even has 600+ repositories so I would say, quite an avid user even.

 

[kpedersen]

In your world, but you may eventually see that people can have various jobs and computer usages for other areas.
Your world is your unique own world, your work, experiences and patterns.

I see you point but still don't entirely agree. Just because I am a "techie" and they are a "casual user", doesn't mean that they should be allowed to use the incorrect tool for the job or a shortcut. This kind of thinking is why Windows went from being pretty decent (around Windows NT 4.0) to a weird on-line only consumption tablet OS (Windows 10.1809).

I.e I notice we have two kinds of academic writers at a Uni, the Microsoft Office guys and the LaTeX guys. Neither group would say they are computer techies... but the Microsoft Office guys are definitely the least productive. The LaTeX guys can merge correctly (i.e with the TortioiseSVN GUI) whereas the Office guys have to just flap around copying around work and manually merging it.

 

[shkhln]

Yet he does use git and github. He even has 600+ repositories so I would say, quite an avid user even.

You didn't see all those "Add files via upload" commits, did you? Although, now that I think of it, they should also have verification label…

 

[tommiie]

You didn't see all those "Add files via upload" commits, did you? Although, now that I think of it, they should also have verification label…

Indeed, I did not notice those commit messages.

 

[SirDice]

But it's great for testing out server sockets and protocols. I use it mostly to validate that a specific server is accessible and the firewall does not block it.

Use netcat(1)