So far I've treated a "service" as basically anything besides what's immediately needed to pass packets, so generally things that reside on things besides the networking hardware. Though this list is a bit outdated, here's what we in memphis are considering:

On-site services More Redundancy, More Internal Availability, Higher Maintenance

DNS (unbound) *
NTP *
Monitoring

On-site services, where convenient

Network Camera (Webcam on raspberry pi?)
Wideband remote receiver (WebSDR style by RTL-SDR and discone?)
ADS-B Receiver
NOAA POES APT Receiver/decoder/web interface
APRS i-gate

Point-to-point supported services

Connectivity for others’ voice/data repeater (d-star, irlp, etc)

Datacenter colocated services Less Maintenance, More External Availability, Less Redundancy

HamWAN Portal (web interface for managing authentication, static allocations, rDNS, ER firewalls, certificates)
DNS (powerDNS) *
VPN (sstp?)
Email
VoIP (Asterisk)
IRCd
Webhosting

44net facing FTP/HTTP File Drop

GIS Server (Quantum)
Echolink conference server, IRLP reflector, and D-STAR reflector (Where suited)
Some sort of social network

*: Anycast service

On Thu, May 1, 2014 at 6:40 PM, Bill Vodall <wa7nwp@gmail.com> wrote:

> A friend put up a repeater on 2 meters.

> ...

> and it's still transmitting all day long.

Is it June in Washington already? :)

> I keep hearing this, "services," but what does it mean?

A reason to 'click' the link. The web based IRC system is a good
example. It's a useful and fun resource that's worth 'clicking on'.
Too easy perhaps as that shortcuts the much great effort necessary
to do the same on Ham radio.

These days everything is so easy 'on the web' that there's little need
to do anything else.

Bill, WA7NWP

_______________________________________________
PSDR mailing list
PSDR@hamwan.org
http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org

Ryan Turner