Marius;
On Tue, 2019-07-23 at 09:06 +0000, marius--- via 44Net wrote:
+1
But, afer almost 20 years playing around witht his topic, I think the lack of specific network services on 44net is the actual element preventing the spread of its usage. The original goal was conectivity, global if possible. But there simply is no incentive for using it anymore. Dx clusters are reachable on the regular internet, repeaters and reflectors too. Specialized sites dedicated to contesting are homebrew stuff, or whatever, use regular internet access. They can not rely on a network where only 10k users are reachable. And BBS systems are outdated and replaced by forums, mailing lists and discussion groups on various platforms. Unless we can find desirable services that really need a "private" globally routeable network for them to work, there will be no real new users influx beyond the occasional network enthusiast.
The one key thing however about using 44-net as a source IP is that when you visit another ham's services no matter what they may be, that ham for the most part (not always due to spoofs) can be rest assured that you're a licensed ham using their facilities whereas this is much more difficult when using a DHCP public IP from an ISP... especially if your services involve the remote usage of amateur radio frequencies.
It also allows you to host services under a static IP schema vs that of a dynamic DNS config. In the case of running a mail server such as sendmail, postfix, exim, etc. you have the availability of RDNS whereas dymamic DNS offerings do not offer this. In many mail server configs, RDNS is required to match forward DNS as a means to help filter spam. Mail server services (at least here) by default are often filtered by the ISPs as well where amprnet allows for usage of one.
In support of your case, I think I'm the only one on this list who uses an MTA on amprnet.