If you had an account on the old BBS and supplied an email address, your account has been migrated to the new setup. As I had to do each one by hand, it’s quite possible that I made mistakes so let me know if that’s the case and I’ll fix it. As long as you are able to log in you can also correct your details in your (A)ccount settings.
IFTTT has been working with developers over the last few months to directly add integration into apps so that you can unlock and potentially activate recipes from the apps rather than the web site or the IFTTT app itself.
Integrations with Abode, Awair, BloomSky, Foobot,Garageio, LIFX, Qapital, Roger, Skybell, and Stack Lighting are live today and Automatic, Emberlight, and Ring Video Doorbell are in development so should be live soon. Currently the only one I use is Automatic so that will be nice. All of the other home automation apps listed above pretty much require cloud support (as does Automatic) in order to link it up to your home automation system and while it’s a nice add-on, being dependent on something in the cloud to automate your home is a really bad idea IMHO.
Rather than run a virtual machine I’ve kept my Mystic setup on my Win 10 64bit desktop just because it uses less resources that way. I was finding that my system was bogging down. Until I can get some of the other stuff offloaded to a Raspberry Pi I have Plex, Jackett, Sonarr and several other things running here at the same time.
That means that until I set up qemu the old 16-bit dos games won’t work except for the ones I have set up using BBSLink. I’ll try and get some of the newer 32 bit doors loaded as soon as possible. Currently the only one I am personally hosting is Usurper. There are at least ten accessible from the BBSLink menu though.
I have a few of my Ansi menus moved and will keep working on that slowly but surely. Going to do more back-end stuff first though. I need to set myself up as a point first so that I can access my netmail and all the echomail from my phone. I’ve never set up a point system before so that may take a while.
If you have any suggestions as far as games or mods please feel free to let me know.
Shadowscope BBS is back online and the move is complete (sort of lol.) The message networks have all been moved as have a large portion of the games. I will put my Ansi and menus back up over the next few weeks and doing some tweaking but the hard stuff is all finished. Now for the tedious…
No web interface currently like there was when I was using Synchronet but I’ll be able to pull some of the info off and make a partial interface eventually. Too many pans in the fire currently though.
Door games are not currently working. My BBS laptop finally bit the dust so I have moved it to a VM on my main system and unfortunately something broke in the move. Getting this error in my Synchronet logs currently:
Fuck if I know what that means lol but I’m trying to figure it out. Anyway, I am also in the process of setting it up using Mystic BBS as well. Message boards are still online. I’ll post another update once I figure it out.
Back in June an Atlanta Police Officer fired into the vehicle of Deravis Caine Rogers as it was fleeing a NE Atlanta apartment complex. Rogers had been suspected of breaking into vehicles.
Rogers was hit in the head and died at Grady Hospital.
The Atlanta Police Department has pretty clear rules about firing a weapon into a vehicle and after review it was ruled as excessive force since there was no obvious threat to the officer.
No word on charges, if any, that may be brought against Officer Burns.
Wow. Who knew?
One of the very first posts of mine online from back in November ’99 was about Litestep, a replacement desktop shell for Windows that basically emulated a Linux desktop of the time. Apparently it’s still around. You can check out screenshots and download it at some of the links below. Talk about nostalgic. I may have to give it a spin.
Anyone familiar with having a blog or web site can tell you that spam and getting hacked are a constant thing. Hell, I had to completely redo my web site late last year after getting hacked.
Well, apparently hacking BBSes is still a thing. For the most part all of the ip addresses associated seem to be from eastern countries, China, Korea, etc…
There are a couple of simple things you can do to cut down on the traffic and false logins and there are several reasons to do so.
First and foremost, if your router is able to block specific incoming addresses, that’s the route to take because it will cut down on traffic on your internal network. Not going to go into that here because until I load DDWRT on my router I don’t have that capability.
There are several settings in Synchronet that will help cut down on the number of folks attempting to log in.
- In the Synchronet Control Panel go to File – Properties. That will open the Control Panel Properties Window. Open the Security tab. There’s 4 options here. Delay (milliseconds) is where you can set the time between failed login attempts before a specific IP is locked out. Throttle (milliseconds) is how long to delay successive logins after a failed attempt. Hack Log Threshold is how many failed login attempts from a specific IP before it’s marked as a hack attempt. I keep this set at 3. IP Filter Threshold is how many failed attempts from a specific IP are allowed before it’s marked as a hack. That’s also set at 3 here. These options are all good if you want to automate the process. It’s still going to allow a certain number through and a small amount of network traffic but it’s damn sure better than nothing.
- You can also manually block folks as well. In the /sbbs/text directory there are a few pertinent files to look for. One I use constantly is the ip.can. It’s a list of IP addresses, wild cards accepted. Mine is currently up to 175 lines. If you use this and block top-level IPs be aware you can block prospective users as well.
- name.can is a list of user names that are blocked or not allowed to be used by new users. Sysop, user*, system*, config* are all good names to be in here.
- password and phone.can should be looked at as well.
- hosts.can is basically the same as ip.can except allowed host names. It’s not as good as ip.can as the host isn’t always reported BUT it can block multiple IPs that use the same host.
Obviously this isn’t foolproof but it’s a big help. As you can see from the picture above several have been blocked this morning. More than several actually. If you view Failed Login Attempts this will give you a list of failed logins so you don’t have to scroll through the terminal server window. Here’s a small part of the several hundred from this morning I haven’t blocked yet (although now it’s done). I try and go through this when I have time so I can add them to my ip.can
Hopefully this has been a little helpful for someone out there.