Slashdot Mirror
What Software Should ISPs Distribute and Support?
BroadbandBradley asks: "Many ISPs give their customers a software package to install with their service like a branded browser/email package. Some also include network diagnostics tools, even remote connection VNC packages for technical reps to do remote support. The ISP will then tell customer that they'll only get help if they're using that package. What features are good or bad, and what should or shouldn't be included on the client side? My question to Slashdot readers is, what software and services should ISPs distribute and support?"
No matter what we support, the answer to most calls is still "Reboot, reconnect it should work now". No matter what is installed, 80% of our calls will be OS related problems.
"Science is about ego as much as it is about discovery and truth " - I said it, so sue me.
the answer is "only products that you have researched and are familiar with". That means that the software is well documented and that you have links to known bugs & other issues. It helps if you have an inside person in that company too. Keep a knowledge base for your employees to eliminate redundant wild goose chases.
On a side note, you must be pretty brave to be starting a business in a saturated market during an economic downturn. Know something we don't? Most ISPs have already been absorbed by the national chains (AOL, Yahoo, etc...). Good luck.
"What is the sound of one belly slapping?"
alternative browsers, ftp clients, software required for connecting to the ISP servers and that's it...the ISPs should not intrude on the users personal computer other than with software required to use the connection.
internet like monkeys'
Go ahead and mod me down for being a troll or offtopic, but take a look at the other posts here. They prove that the question was dumb to begin with.
To be more explicit, this question is unanswerable in its current form. More information is needed:
What user base are you going after? Linux users? Windows users? What OSes are you going to support? What does your technical support organization look like? Are you gunning for experienced surfers? Total newbies?
ISP's should not distribute any software whatsoever. If they chose to distribute software, or are paid to distribute software they should make it clear whether or not the software is necessary in order to use that ISP. It is OK in some instances such as Cable or DSL to include software only for the purpose of establishing a connection for security reasons.
Prime examples, 1 good and 1 bad.
Let's start with the worst, AOL. AOL requires a large piece of memory eating, slow as crap software to connect to the internet and use their service. Everything is proprietary, slow and crappy. I mean, proprietary is sometimes ok, but not if it's slower than the standard.
SNET internet http://www.snet.net. Their dial up service is exceptional. They give you a cd, but you don't need it. You can use any standard PPP connection software, like the ones built into windows or linux. All the software does it re-configure explorer to say brought to you by snet. If you don't mind it, install it. Their DSL while being fast, amazing, cheap, and everything else is equivalent. It comes with the same non-essential explorer customizing software. And it comes with the little program they use to establish the dsl connection. This is so they can require a name and password and transmit it securely. The software runs under windows. But I've made the dsl work in linux.
The best ISP in the world, college. Plug computer into wall. Auto configure lan connection with dhcp. Open any type of internet software, it works, fast, and reliable. No extra software needed.
Thats how it should be.
The GeekNights podcast is going strong. Listen!
Don't give them some heavily branded browser that is going to start a lot of junk every time you log in. Simpler is better. Don't install protocols they don't need. When I first got my cable modem, @home tried to install Microsoft Networking, a heavily branded browser and a bunch of other junk. Luckily my computer was still in transit so I just grabbed the modem and the numbers and didn't have to call them back. Why on earth would you want MS networking for a home computer to surf the net?
Do give them a minimal version of os requirement. If you tell them they need to have windows 95, and that you don't support win3.x, then you know they have a telnet client and will support that, for example.
Do require a minimum version of both ie and netscape. And then write your web pages to support both equally. Do provide unbranded versions of those browsers on cd and support the installation.
Do give them a web interface to their e-mail. Support that. And remember the minimal browser recommendation.
Do give them a real pop account so that those people that know what they are doing can set up their preferred e-mail client. Don't support those clients officially. This gives you control over the interface so your help people will always know what the customer is using.
For ftp, just pick a program you like. ws_ftpLE on the windows side and something on the mac.
Now the tough choices, newsgroups and chat. Since the chat clients are going back and forth on interoperability, you'll have to make 2 decisions. You'll have to decide if you are going to support a chat client. I'd personally say no, and here's why. Customers will want to use the client that all of their friends use, so if you tell them you won't support msn chat but will support icq, for example, you could lose customers. The alternative is to support the 3 or 4 major clients, and no more. The problem is that you'll have to keep up with lot's of different version which could be a problem. Of course, I don't do the icq/chat thing so take that with a grain of salt.
Which brings us to newsgroups. You need to decide if you are going to host them at all, just non-binaries or something in the middle. I'd say that the best reader for windows is Agent. So maybe you could get a licensing deal with them and spread the cost around. The alternative, outlook, doesn't enter into the picture because of security problems.
But that's just my thoughts.
No, seriously. The selling point of any ISP should be the connection itself. Every dollar spent on hiring a programmer to embed the ISP's icon in a custom version of netscape is a dollar that could have been better spent on more hardware, or more competent sysadmins to keep the connection running smoothly.
Feel free to give the user suggestions about what software to use, and point them to where they can obtain those applications, but don't waste resources putting together silly custom software packages that 1) eat up memory and cpu on the users' machines, and 2) half the users don't install anyway.
I've gotten CDs from various ISPs over the years. The only one I've ever kept (or even used) was one that had every single RFC ever written burned onto it. Massively helpful, instructive, and educational from a historical standpoint.
You must mean like this one. Selected quotes: