Posts by Telesphoreo

Probably not. It depends on what you're actually using it for. It's actually designed for pros this time around. It's not necessary for playing Minecraft or writing emails and word processing. I have the M1 MacBook Air and it does everything I need it to. I can edit 4K 60fps video on it smoothly and do programming on it. It also runs my Parallels VMs smoothly and it's only getting better with the parallels updates. I hardly doubt you need it, especially for now expensive it is

Vouch

Object since you haven't really elaborated on any actual issues rather than personal preference

↩  Tizz I switched the build system to gradle because it took me 2-5 minutes every to compile. (I had done many tests and optimizations to try and speed up the process. Mind you, these tests were conducted on a 1000/1000Mbps internet connection. It was even slower at home where I only have a 100/10 connection. It now takes 1 minute and 30 seconds to build if you completely delete your .m2 and .gradle folder and only 7 seconds for subsequent builds. I spent a lot of time optimizing Gradle and frankly I think it was worth it). The great thing is a maven and gradle build system can coexist. And yeah changes were made. I upgraded it to 1.17. If you don't like the changes then do it yourself but I can see that's not going to happen soon

To fully clarify, the Maven build system will work with 1.17. The only thing that would need to be changed is the spigot dependency from 1.16.5 to 1.17.1 itself. There isn't some black magic going on with Gradle. Everything else in the pom.xml was exactly the same in the 1.17.1 update. I literally switched to Gradle AFTER upgrading to 1.17.1, so it's not some sort of impossible thing. It's just a cheap shot and a cop out.

↩  FromTimeToTime I have no idea what this means

↩ @'Ryan' What? When?? When did I ever do this. I still have the dev tag because I am a developer of TFM. Seth is still in the list and he deleted the server... It's been determined many times that developer != staff and if I recall I literally was a developer as an OP at one point. No one was claiming about me 'pretending' to be staff then and I don't think anyone was at that point either. Further, removing my name from FUtil doesn't make a tag that I set in game go away. You never brought this up before either. I had asked you many times in the Discord about this and you had never given a response.

And the TFMC thing was a joke. It was funnier when I sent it but you took a month to write back and by then the timing was bad. My bad on that part

↩  Tizz I already gave my two cents on how to convert the data which was ignored. I also updated every plugin to 1.17 including TFM which was also sweeped under the rug. It's really not my job to be a developer, especially without credit since wild thought it was a great idea to remove my name from the tfm credits for no reason or explanation.

↩  videogamesm12 i mean you could investigate the issue and try to fix it rather than do nothing but talk crap about the system which means nothing happens

Vouch most of them dont need to be pinned and also for someone who is not logged in its literally a full page worth of sticky threads every time

↩  videogamesm12 idk what you expected Mypal seems like a sus name for a web browser

↩  videogamesm12 some of these symptoms feel like a failing GPU. did they go away when rebooting the computer

1.16.5 is still using Java 8 I believe which is so old it still supports Windows XP. Try getting 1.17.1 with Java 16 running then I'll be impressed

↩  Panther we have a plugin for that already (VulnerabilityPatcher). It's difficult to maintain without an extensive understanding of nbt and/or the exploit in detail. That could be updated to patch more exploits but it hasn't

↩  Panther I somewhat agree but I think the biggest thing holding TF back is all the exploits and how much stuff is blocked due to exploits. Switching to a permission system would make the initial setup easier, but wouldn't fix any of the exploits. I've said this many times as well but the TF- plugins have other modifications besides the permissions. Some of them like disabling disguises and the granular control over essentials cannot be done with permissions alone

I'll reference what I've said to you and in my developer resignation thread:
"the master plan was to stop TFMs 2020.x.x releases and essentially create a stop gap between TFM and Plex. TFM 6.0 (which AMG never merged by the way) was supposed to be the start of a major cleanup and debloat of TFM. essentially, 6.0 would fix a lot of the long standing bugs and freeze ALL features. then the plan was to start a prototype of Plex with its new way of organizing code and see if the community wanted development of Plex to continue. that way, both outcomes win. If yes, then TFM get retired and and Plex becomes the new TFM and then we start extensively testing it and really making it "drop in". if the community didn't want Plex, then that sucks but at least it was coding experience and some of the code could potentially make it into TFM. but if the community said no then remember that TFM 6.0 would exist. so even though TFM has underlying issues, when i resumed TFM development, i wouldn't be swamped fixing gazillions of bugs (they would've been fixed / i would've been better prepared to fix them). and of course as you know the plan was to have two separate dev teams (the plex team which we had) and then the TFM dev team which fixed super critical issues and handled normal plugin updates so that the server wouldn't entirely be locked in one state"
and
"The November update was underwhelming (and ultimately never actually got deployed unfortunately). I was planning for a mid November update which fixed a bunch of bugs within TFM and would have made things better. The plan was that after the mid November update was done, to start getting rid of a bunch of obseleted and useless features in TFM. I was going to skip December for an update since that's holidays and time you should be spending with family (or, well, at least not hooked to a computer screen imo). TFM would have been cleaned up for the January update to tide us over until Plex which would have been done by mid 2021. Making threads to intentionally piss me off is a douche move, especially when I'm actually active and working on Plex and TFM at the same time as a one man job. If I was inactive or not doing anything, then I do think bitching about it would have been perfectly justified. But I was actively working on everything and making those kind of threads drains me and adds to how already burned out I am. I was planning on appointing (or having the community vote on) taah and super for being devs if they wanted when Plex was done. I don't know (or really care) who becomes the new Dev / Lead Dev and what their direction for the server is. Anyways even though I may have had the shortest run of an executive position in the history of TF, I'm fine being an admin because it's a fun way to relax and chill with people."

This is the plan you should have followed

Minor bump but this might be relevant for anyone considering UniFi. So it turns out you can actually update the firmware on switches / access points without having to upgrade your controller (Ubiquiti now calls this the "UniFi OS Network Application"). It seems as if people aren't having major issues with the newest firmware versions for switches / access points. All the big issues with UniFi are with the actual controller itself. It seems as if using 5.14.23 is still the best version for the controller. I just upgraded from 4.3.20 on the access points and switches to 5.64.8 and 5.43.46. There are no immediate issues so far. I'll update if there are any issues. Reverting to older versions on switches / access points is extremely easy. Reverting the controller is not. You have to reinstall it and lose all your data. If you take a backup beforehand, all the data will restore. Reverting the cloudkey back is also relatively easy. It's still on 1.1.13 as that version doesn't force a Ubiquiti account.

17

Congrats!

Congrats!

sudo rm -rf / --no-preserve-root