i3ision

Viewing this in 12/14/2023 the bandwidth on the advanced blogger is still very limited by modern standards. 750MB of Drive Space? No mention of SSD? Nvme? or just HDD? 2.5 GB of Bandwidth? Very limiting the estimated data flow on the internet by 2025 is 175ZB yes Zeta Bytes of data? The cost here is 2.99? so the cost vs the services is still debatable as if you where a blogger for example running videos even using a cdn to display images and videos to offload you would burn threw this limit very fast in modern internet society. Note: i have not used the service just reviewing the cost vs whats given namecheap among other sites use similar shared hosting scenarios with a 2-3 $ increase with vastly different resources. While something like folkinet offers a low cost with ddos protection and Web Application firewall with more initial upfront costs. Just my two cents owning a web hosting company none that i have listed of course as its rude but running a company no matter shared or a pure shared reseller what we look for is over selling when paying for anything with hard limits. Many say unlimited and that annoys me as nothing is infinite so this service is decent for a new user but other options are around. It's all what you use it for for a PBBG that uses minimal images and offloads quite a lot to a CDN say backblaze as its a cheaper yet good alternative to amazons s3 well this would be suitable. i will give this a shot just because all hosting requires a proper review many high end hosting have caveats that they don't tell you until after payment.

seeing i should introduce myself as its customary to do so on a forum, I am older now and married i started making browser based games ( mainly text based with imagery ) starting at source forge then moving various places getting my start at pvpgamers, ragezone and few other forums during this time frame some i will list others i will not due to legality. Still running three games with a small team of web developers mainly core php vs annoying frame works like laravel, code ignition and recently annoying updating slime i mean slim php. 😛 I came here out of curiosity to see if the community and gaming community are still in love with PBBG's as a whole seeing telnet based mud's haven't died off yet i found that many web based games haven't either with a low player base but still enjoying the old like games while improving them to meet modern internet standards. I say hello to everyone from the united states and among the internet it's nice to meet you and i look forward to posting and chatting with you on this lovely forum and messenger the is provided. 🙂

Times have moved to a mobile first logic many forums just don't have the same traffic nor do people wish to wait for a new post most have moved to discord and most people even on IRC ( still am quite often ). We live in a current internet society that is mobile first and desktop for most basic users come last, site loading speed if its over 3seconds most people leave and don't return unless its something they really wish to read or play. Seo also has become more secure meaning HTTPS:// is required to even be ranked properly in most search engines its very annoying from someone getting started in web development as a kid in the late 90s using good ole xhtml and vanilla js. People come and go quite often i was part of other forums before joining this one initially just out of curiosity to see if people are still around that i knew among the PBBG communities oddly enough many aren't as its not as popular nor do people care for it. I just refuse to leave something i love even if its more or less an unprofitable hobby that cost me and my team money. Times have changed too much in my opinion but change is the nature of technology and the human race ( minus politicians and lawyers 😛 lol )

I like the fact that you are using w3.css not many people use it as well its less heavy on page loading speed than what we use bootstrap.min.css, bootsrap.js.min, popper.slim.js and so on for the hamburger menu to display on mobile devices. w3.css uses a simple stylesheet and vanilla js to handle these thing and is faster on loading using pagespeed and other seo tactics the page speed at google is 100,100,100,100 using w3.css vs bootstrap being maxed out at the same on desktop and mobile being slower ms but still 100,100,100,100 For the code itself to improve security you should be using filter_input and FILTER_VALIDATE_INT to make sure no modifications happen before and after the processing of the form happens while also validating any user input and output to the screen. You could also improve it further using Object Orientated Programming so if you use database back end say PDO or mysqli this then allows for pure OOP something you do not want to mix but this is a recommendation not a requirement not everyone wants complex code in many ways procedural style mysqli adds more lines but improves readability with the same level of security. All in all i love the idea you have going here we use something similar but use dungeons and dragons 100 die logic here something we used coming from dice games that runescape had at the grand exchange ( sorry bit a runescape nerd so this is where our inital logic for it came from ) ps: i got told i type too much by the lovely wife 😜

I have been running various persistent browser based games since the early 2000's and GDPR policies that have came out only specify the following coming from the legal team i asked about having existing features to view a admin, member, player and so on. I was told by a lawyer that specializes in privacy and advocacy that when viewing user data user the reasoning of checking for abuse of any kind that violates the set Terms and Conditions or any other possible abuse for it is legal but must be documented when viewing content. Say they use a stolen card it dictates that viewing private data is allowed only by authorized personal and must me logged and documented then once it has went one way or another it must be secured and encrypted or removed if no abuse is found. Notification is not required unless abuse is found but publication is not required to be sent the intended person or persons. In case of say harassment or any other non financial abuse it can be viewed but logging is required across the board to check the user i find to be intrusive anyways in someones privacy as GDPR is a privacy protection for the end user. example: Investigating abuse through user account access can be legitimate under GDPR, but it must be done cautiously, proportionally, and transparently, minimizing data access and respecting user rights. This is pulled from conversation i had with a lawyer so its a grey area either way with current GDPR standards meaning it could be an issue or it couldn't be an issue as always consulting a lawyer is key. ( also expensive ) I personally create logging mechanisms to track user messages, send and receiving aka logging into a database with a salt key so only administration have access to the key to decrypt their messages. Logging should track payment records, time, date, cost, ip address and so on in an encrypted manor. Logging should also track for harassment if you allow sending of messages, posting on profiles, comments and so on should also show a searchable interfaces to check for only certain users data and so on. while logging just about anything that can be seen as possible abusive routes While accessing data you must notify if anything is found this is the grey area as some GDPR lawyers say you must notify just for viewing data not if anything is found as it violates privacy while others argue that unless abuse is found there is no need unless they ask has my data been acccessed. Then you are required to send all info that was accessed so its debatable and best case is don't view anything under current laws without detailing everything you view so if the end user or say abuse happened or didn't happen. Logging for you and the end user should be held to the same high standard. GDPR in my opinion is a joke it requires higher logging requirements for your website and the end user so in the end it protects the company mainly not the end user but of course this is my personal opinion after dealing with various cases along the same since its inception. It's similar to fraud we are required by law in most countries to log IP access data, GEO LOCATION, last 4 of the card, or say paypal, stripe and so on account that used to pay for it. While still accounting for user privacy and payment privacy meaning accessing the data should only be by dedicated staff with insurance on them so if they do something or the user says they did something illegal you are covered. The current game my team is working on is in the early stages using modern PHP 8.x+, while using logging at every step of the way i find this to be more abusive to privacy but this is what is required to honor the GDPR, California's Privacy (US), and COPPA policies logging is required for all staff and all users so the right to remove is there. The Terms of Service and Privacy Policy also must explain what is logged and a link has to be easily accessible to download their personal data on request this causes unneeded over head for a small website or small group of web developers like my sites have with limited overall profit on each game. ( currently we have 3 active games that i will not disclose due to legal reasons their are forms for this on our sites if you want that data ) I will end this with GDPR, COPPA, California's Privacy and other right to removal requirements actually require you to log more information to stay up to legal standard that accessing data and removing anything unless a legal case arises for small sites vs the requirements of say a large multi-million dollar company so it hurts smaller development teams more than big companies and the end user is logged even on smaller sites to great extent while staff now have to log anything they view that is "private data". This is just my two cents after having to deal with a few cases of abuse and right to removal in the real world because one of our oldest games closed due to cost to redo existing source code to stay updated would cost more than the site was making thus closing was sadly the cost effective option We where in the process of updating a game that dealt with fake currency, marketplace, trading and selling of digital items what got me in this case was if we made zero profit from allowing users to buy coins vs showing them ads that violated privacy and harassed them to donate would have been easier legally than taking money with minimal logging. The current privacy frameworks are a harm to smaller development teams that protect privacy more than big companies, we had a remove all data button before big social media companies even offered it after running forums for over two decades we felt it was key to allow for this the fact they had to tell companies that it has to be added is the problem. protecting the rights of the end user should be the same either way its rather annoying but this is again my personal experiences you may have had a different one and please read the notice below . NOTICE: Remember, this is a complex legal topic, and the specific application of GDPR to this scenario depends on the individual circumstances. For definitive guidance, consult with legal professionals specializing in data privacy and the GDPR.