We have built new functionality into System40 that will obtain new Bluesky API tokens once every 3 minutes for each bot application. This has resolved the rate limiting issue that we were experiencing with our live playlist bots for J1 and Michi-FM. These bots are now running stable. Those bots are located at:
REC has released myLPFM version 3.6. This version adds a new option for stations to add their Bluesky handle. This change can be made on on the visibility page (book icon). Simply enter your Bluesky handle (the part after '@') including the 'bsky.social' portion unless your Bluesky handle is associated with a Personal Data Server (PDS) or with a custom domain name where you would use that instead of the '___.bsky.social' format.
Bluesky addresses can now be listed in RadioDNS.
REC has started to launch services on the Bluesky social media platform. Bluesky offers an alternative to Twitter/X without the advertising and the questionable leadership. REC will be phasing out remaining operations on Twitter/X in favor of using Bluesky. We will not completely remove our Twitter/X presence for historical purposes and to reach a wider audience when necessary, especially during this time when many of our readers start a transition to the Bluesky platform.
REC has been using a third party service Uptime Robot to monitor system readiness for REC systems operated both internally and by third party providers as well as monitoring the various systems at the FCC that REC utilizes on an interactive basis.
We have installed a new application that will monitor the API at Uptime Robot to store the uptime data for all monitored applications.
On November 6, 2024 at 6:55PM EDT, the legacy server has been permanently shut down.
The REC System40 transition is now complete.
We will still be checking for bugs. We appreciate your bug reports.
Thank you for your patience during this transition.
Launched MantisBT (bug tracking software). A public view and reporting method is available at https://bugs.recnet.com
Finished recoding and completed transition of FCCdata.org.
Reported and resolve 24 bugs. The high bug rate was expected due to the complexity of this program.
With FCCdata being transitioned, we have discontinued the eLMS dual operation mode. eLMS is now running every 10 minutes during the weekdays, 30 minutes in the evenings and 60 minutes on the weekend.
As part of the System40 Transition Project, REC Networks will be transitioning FCCdata.org to the new server over the course of this weekend.
During this time, you may experience site outages, SSL error messages (stating that the site is unsafe), or on-screen errors.
Like with any system upgrade, you may experience issues. If you experience any bugs (such as error messages in an orange box), please visit https://bugs.recnet.com for information on how to report bugs.
This weekend was dedicated to the recoding of the FCCdata.org codebase to PHP8.
This site is going to require more testing than the others. FCCdata will transition over either this next weekend (11/2~3) or the next holiday weekend (11/9~11).
FCCdata is the last major public facing service that is still on Legacy. Once FCCdata is transition, we are going to start the wind down of the Legacy server.
Over the past weekend, we had transitioned myLPFM.com and Internal Application N01.
At this time, we have shut down lpfm.ws (Voluntary Public File) as we determine what will be the future of this service. We want to bring this back and it may come back after we are able to integrate the station interface into myLPFM.
We have been dealing with some very serious database performance issues and therefore a lot of time has been spent on trying to adjust the mySQL settings and taking other actions to improve the database performance.
RECid is a product of REC Networks which maps a 7 digit application ID with the 32 character hexadecimal LMS application ID to provide a more user friendly identification of applications as well as to integrate with applications that may have been originally designed for CDBS which used an integer as an application ID.
Update freeze now in effect - Server transition projected for 10/19.
This long weekend consisted of extensive work to ready eLMS on the System40 server. A working version of eLMS is now residing on that server.
We temporarily stopped eLMS services on Legacy in order to do a complete copy of the frozen database to Sys40. eLMS services have been restored on Legacy (see information about dual operation below).
Copied census and application JSON files generated by eLMS to Sys40.
Converted from perl to PHP, the program that is in the eLMS suite that parses the authorization PHP files from the FCC and saves information to the database upon application grant.
Commenced manual testing of the eLMS suite in the test environment.
Released advisories related to the upcoming commencement of dual operation for both the database copy exercise and for the period of time REC will be in dual operations.
Precoded 17 applications that are part of the morning run. Most of these programs interface with eLMS.
From Monday October 14, 2024 until further notice, the frequency of updates provided by REC through eLMS will be reduced from every 10 minutes to every 15 minutes on weekdays.
On October 12~14, 2024, eLMS application handling services will be temporarily stopped. This will not impact the ability to view data on systems.
Please show your support by using the Ko-Fi link at the bottom of the page. Thank you for supporting REC's efforts!
