In the wise words of Polaris Seltzeris:
QuoteThat's a funny joke you just made there buddy, locate a John Deere brand tractor and cum.
In the wise words of Polaris Seltzeris:
QuoteThat's a funny joke you just made there buddy, locate a John Deere brand tractor and cum.
I'm still using my budget Android phone from 2017 and it has worked perfectly fine since then. Why use something that's going to break in a few months when you could use something cheap, reliable, and usable for years?
Why is an admin who has been suspended for logging in as other admins and linking to horrid websites trying to sue a brand new admin who hasn't even been suspended yet?
Late 2013.
You can view some logs from my early sessions here, including the ban that led me to create a forum account on the ProBoards forum (see 2013-11-04-2.log at the very end):
https://github.com/VideoGameSm…/master/TotalFreedom/2013
@fionn#10284 Shut up fionn.
@chargenation1158#10250 Yeah, but he changes his skin so often it wouldn't even matter anyways.
This is the 1,000th thread on the forum. I have a secret I would like to reveal.
Click here for more information.
You could tell their accents apart?
There was a window of time in 2019-2020 in which you could view real-time bans using a module in the HTTPD server, as bans were still stored in a YAML file. However, this HTTPD module stopped working after we started migrating our data to SQL databases.
Kanst all the way, baby.
@Miwojedk#10141 Flarum's modular nature means that many extensions we rely on could at any given moment stop being updated. If this were to occur, we'd have to either stay on the last known good version where the extension worked or we'd have to find alternatives. The more extensions we add, the more likely we'll run into a scenario like this in the future.
Of course, for the sanity of this community and the folks running sysop, we could just dodge these hoops entirely and use ProBoards or WoltLab instead but oh well.
@ScubaSteve#10112 By default, no. Many files are locked behind closed doors. I'm just publicizing some files I have saved from when I was an Archivist (former official title) from February 2019 to April 2020.
How dare you make a mockery of our lord and savior! I shall have you stoned for this!
Intended title: Ban system incorrectly saves and loads expiration timestamps, causing it to always think the ban is expired
Just for the record, this is the bug that is causing bans to not load in properly. I've already informed the developers and Ryan himself about my findings and I'm hoping this gets fixed quickly.
When the TotalFreedomMod saves a ban to the SQL database, it does not include the milliseconds value when it saves the expiration timestamp. When it tries to load this entry later on, it divides the expiration timestamp by 1,000 under the assumption that it contains the milliseconds value when in fact, it does not.
This behavior can be observed if you modify the plugin to spew messages when the relevant functions are called, as shown here (this was from a reload):
[07:14:13 INFO]: [TotalFreedomMod] --- CONSTRUCTOR FOR NEW BAN CALLED ---
[07:14:13 INFO]: [TotalFreedomMod] --- FUtil.getUnixTime(Date date) CALLED ---
[07:14:13 INFO]: [TotalFreedomMod] Unix time is 1614521600
[07:14:13 INFO]: [TotalFreedomMod] When divided that is 1614521
[07:14:13 INFO]: [TotalFreedomMod] ExpiryUnix is 1614521
[07:14:13 INFO]: [TotalFreedomMod] --- FUtil.getUnixTime(Date date) CALLED ---
[07:14:13 INFO]: [TotalFreedomMod] Unix time is 1614521600
[07:14:13 INFO]: [TotalFreedomMod] When divided that is 1614521
[07:14:13 INFO]: [TotalFreedomMod] --- Ban.isExpired() CALLED ---
[07:14:13 INFO]: [TotalFreedomMod] Comparing expiration unix with current time
[07:14:13 INFO]: [TotalFreedomMod] Expiry unix is 1614521
[07:14:13 INFO]: [TotalFreedomMod] --- FUtil.getUnixTime() CALLED ---
[07:14:13 INFO]: [TotalFreedomMod] System time is 1614435253488
[07:14:13 INFO]: [TotalFreedomMod] System time when divided is 1614435253
[07:14:13 INFO]: [TotalFreedomMod] Unix time is 1614435253
[07:14:13 INFO]: [TotalFreedomMod] --- FUtil.getUnixTime() CALLED ---
[07:14:13 INFO]: [TotalFreedomMod] System time is 1614435253488
[07:14:13 INFO]: [TotalFreedomMod] System time when divided is 1614435253
[07:14:13 INFO]: [TotalFreedomMod] videogamesm12's ban is expired, therefore they should be unbanned
Display More
After the plugin loads the ban with the incorrectly-divided expiration timestamp, it then checks to see if the expiration timestamp is less than the current time. As the expiration timestamp has already been butchered, it ends up returning true every time. As a result, it removes the entry. This should be fixed as soon as possible as it is a major bug in an important part of the plugin.
TL;DR - A bug in the banning system caused ban expiration timestamps to be 0.001% of the actual timestamp when loaded in, causing bans to be incorrectly marked as expired.
If the spirit of this suggestion is to block pornographic HD heads entirely, then I object. We shouldn't be regulating the HD head ecosystem beyond the bare minimum (e.g. dealing with laggy, game-crashing, or crash chunk creating heads) as it would be difficult to enforce and has the potential to create a black market.
However, if the spirit is to prevent these heads from being placed near spawn, there's a similar rule set into place already regarding pornographic builds:
I believe that this would apply to HD heads better than the rules about posting pornographic links as they are quite literally pornographic builds.
It feels like the quality of threads in this board just keeps getting worse and worse overtime.
Object.
@hammelhopfan#9937 There used to be a rule on the forum that if you were indefinitely banned from the server, you could only use the forum to appeal until you were unbanned. If you used it for anything other than appeals, you could have been sanctioned for it. Not entirely sure what happened to that.
This is a bunch of small collections of miscellaneous files pulled from the main directory of the Minecraft server. I've separated them by date.
One of the files contain some incoming messages from a channel on the old Discord.
You can download it here.
https://archive.org/details/to…iscserverdata-jul-27-2019
One of the files contain a very colorful choice of words for a password.
You can download it here:
https://archive.org/details/to…iscserverdata-mar-19-2020
SkinsRestorer was a plugin we used to have on the server back when we were still a cracked server. It was originally added in June 2015 and was removed in 2020 after the decision was made to stop being a cracked server.
This is the SkinsRestorer database circa October 17, 2019. It has 3,771 files.
These files consist of the following information:
You can download it here:
https://archive.org/details/to…insrestorerdb-oct-17-2019