Ah I see.
Reading through all the posts, and thinking about the goal, preventing underage users from participating on the forums, it this seems like it may be a tough thing to accomplish, especially with the chance of an at-age user copying and pasting a link that an under-age user posted.
Lest, there’s something like a hidden code that’s copied over with the link, possibly some HTML code implemented into all roblox links, of course being the same in all links so that the website backtracking (like web.archive.org) can still be used, but it would start up a little counter thing that would track how many times the link was copied and whether the user that copied it’s account was of the correct age. It would also tell if the user that posted the link was the original copier (the one that took it form the site) , and if the original copier originally copied a “web.” link, then it would notify something, sending that data to someone for review, to possibly understand the context of why it was posted as a “web” link, incase the user actually is of the correct age.
The code for reading the data and notifying the data to something could all be stored on the actual webpage instead of in the small html code, or whatever is chosen to be used for the storing of the small amounts of info.
Another thing that could be done, in order to prevent users from breaching this by use of browser extensions or software, is make so it can never be turned off, unless it’s actually deleted from the roblox servers. Now software could be coded to create a sort of “false state” where the site believes the code has been deleted. Unfortunately there’s always a way people can work around a system, but it is possible to create a line of code, possibly a very long one, that could mix up the code in some way, but the servers or something can still somehow read it, but developers trying to code their way somehow around it wouldn’t be able to decypher it, like what was done with radio signals a while ago by the U.S.A. .
The mixing up of the code and the html code would definitely be the most challenging things from what I described above, the code mixing most definitely being the greatest challenge.
In conclusion, internal server code mixed with external server code could possibly solve the problem of the under-age usage on the forums.
P.s.
If a user does get kicked from the DevForum for being underage, I’d like it to be where the posts they may have made are still on the forums, however they are not able like, comment, respond, edit, or bookmark them. Perhaps not even view the posts if they were in non-public threads. But their posts would still be there for if they ever choose to come back to the forums once they’re old enough, and if anyone wants to use the information they provided, (if they made a really good descriptive helpful post perhaps) .