>>>>> Paul Edwards <
muta...@gmail.com> writes:
>>>>> On Sunday, 5 August 2018 04:20:50 UTC+10, Ivan Shmakov wrote:
>>>>> Paul Edwards <
muta...@gmail.com> writes:
>> I've seen "virtual server" offers that'd easily allow for such
>> forwarding going from about 5 USD/month, but there're reportedly
>> even cheaper options.
> Actually I'm already paying for web hosting at
dreamhost.com - my
> website is
http://www.mutazilah.org Maybe I can run qemu on that.
Perhaps. But note that even if they offer "shell" access, they
may still forbid port forwarding. A sure sign that you can do port
forwarding is that you have "root" access to the remote system.
>>> That would solve an additional problem in that I think I need to
>>> pay another $10/month if I want a static IP from my ISP.
>> And I gather they don't offer IPv6 as an option?
> I don't know. I might ask them on Monday when I ask them if they are
> blocking all inbound traffic which is what it looks like to me.
If they charge $10/month for allowing inbound connections,
I wouldn't expect them to offer IPv6, especially free of charge.
It should still be possible to get free IPv6 network allocation
and forwarding from SixXS, though.
>> If you have a globally-routable IPv4, you can try running a Tor
>> relay. That will allow you to receive incoming connections for
> I'd rather not get too involved with that. The serial port was meant
> to provide a simple solution to me instead of having to drive a
> network card.
Tor redirects incoming connections made to a TCP port of a
".onion" hidden service name to the configured TCP/IPv4
host:port pair. Which may very well be a Bochs (or QEMU) TCP
socket representing the VM's serial port.
Then again, Tor requires inbound connections, and once you
have them, you can (AFAICT) go without Tor.
Unless, of course, you want encryption and "pseudonymity" Tor
provides.
>>> The focus of my BBS is being able to use the serial port rather
>>> than having an "authentic" socket experience.
>> My main concern is that as proposed, it seems that this BBS would
>> rather faithfully replicate the "one user at a time" aspect of the
>> dial-up systems of the old.
> Yes, and it will have a 10 minute limit on it too. I used to run a
> BBS called the Ten Minute Limit which only gave BBS users 10 minutes
> - enough time to download the appropriate software (some of which I
> wrote, like a Telix SALT script) to connect to my BBS automatically
> and do file requests etc.
> So I guess I am trying to get back to the state of affairs I had
> then, before pushing forward again.
I'm unsure that you can force TCP disconnect from within the VM,
however. I suppose you'd need some "dispatcher" code forwarding
connections from the outside world to the VM, disallowing them
when the "line" is "busy" (which Bochs should already do) and
terminating them on timeout (which I doubt it does.)
An alternative would be for said code to manage lists of "free"
and "busy" VMs and forward the connections appropriately. Or it
could start new VMs automatically (up to a specified limit.)
That, however, implies that VMs do not communicate to one
another in any way, which would preclude them from being used as
"proper" BBSes.
> Note that I am trying to consolidate a position using public domain
> (explicit notice) software as far as possible.
As I've mentioned in this very group back in 2013, having
a "public domain" notice may not be enough, as there're
jurisdictions which do not recognize such a notion. (Assuming
that you /do/ care that your software will be free worldwide,
and not just in selected countries.)
Cf.
http://en.wikipedia.org/wiki/Public_domain:
In 2009 the Creative commons released the CC0, which was created
for compatibility with law domains which have no concept of
dedicating into public domain.
And later in the same subsection:
In October 2014 the Open Knowledge Foundation recommends the
Creative Commons CC0 license to dedicate content to the public
domain, and the Open Data Commons Public Domain Dedication and
License (PDDL) for data.
I still do not seem to understand the necessity of the software
to be "public domain," however. Even though I've published some
works under the CC0 Public Domain Dedication myself, it seems
that about the only thing it's good for is that it makes possible
for some Big Money, Inc. to take your code, improve it, and hide
it forever from the prying eyes of their users.
Another thing to note are digital rights management (DRM)
measures, which are generally illegal for the user to circumvent
-- regardless of the copyright status of the work they're
applied to. Which is why contemporary copyleft licenses, such
as GNU GPLv3 and CC BY-SA 3.0, expressly forbid the use of DRM
while distributing the covered works.
> My needs are fairly minimal. I'd like to talk to people like you
> using the English alphabet. I used to be able to do that via
> echomail groups on my BBS. I would be happy to return to that state
> of affairs, but change things like I now have a public domain
> operating system too, and it seems like it might be good enough to
> drive a BBS.
If anything, I hope that your BBS will use Usenet-compatible
formats for "groups," as opposed to those compatible with
FidoNet echomail.
> I already have a public domain zmodem too.
> I have to start from somewhere.
I wonder if you can also adapt Pdlzip [1], a public domain
compressor based on the LZMA encoding, to run on your system.
I have expected that the Free Software Directory would reveal
many more CC0-licensed packages, but apparently it has none on
file [2]. However, there're some "public domain" ones [3].
[1]
http://nongnu.org/lzip/pdlzip.html
[2]
http://directory.fsf.org/wiki/Special:WhatLinksHere/License:CC0
[3]
http://directory.fsf.org/wiki/Special:WhatLinksHere/PublicDomain
http://directory.fsf.org/wiki/Special:WhatLinksHere/License:PublicDomain
--
FSF associate member #7257 np. Symphony No. 9 (Beethoven) -- Papalin