Because Microsoft is going to turn on your webcam which happens to be directly pointed to you having naked sex then put it on display on a huge screen at a public mall's parking lot. And they support other people to do the same.
I was talking from a non-computer-related perspective
Gravity understood it XD
but now apply that to your personal information, with the new form of control that's being found in windows, you tell me the dangers there.
if you wanna say there is no danger, then go build a house next to an active volcano and see how long you live
But in all seriousness, I've never had a problem with Windows 7 security, and know nobody who has. Windows XP is no longer updated, so there's really no reason to want to keep it on there.
keep in mind MS thinks you're only using their stuff and doesn't consider stuff like Comodo. XP is still very much suppported when you look at the standards there
I'm actually glad they stopped the updates to a point...
and you wanna know why you havn't had a problem with Win7 security? do you know why MS pulled back the market control features on the XBox One?? MS: "People aren't ready for them" (meaning they will put these features to use in the future)
look, if you want to continue using Win7 and putting your personal life at a potential risk to the public, go for it. just keep in mind, I'm not for that type of monstrous control and will NEVER support it.
if you want my support, move back to freedom and leave MS in that concealed hole they're digging.
get WinXP x64 or get Linux, with those, you give yourself more freedom and personal security. rather than limiting yourself to a not so configurable environment.
when it comes to tweaks and customization, Linux can easily do what you have to jump hoops to do in XP, and good luck with 7 and up as you're constrained and forced to use the environment they give you, along with them watching everything you do.
if you want your freedom and safety, don't listen to a corrupt company like MS. I may not have the knowledge to verify that XP is ENTIRELY safe, as I can say linux is safer (to a point). but I can verify that XP x64 is safer than other XP installations and doesn't have the MS-control implementations that've been found in 7 and up. (Vista is only questionable)
must I mention I'm a Windows hacker to know this. :/ (relax, I'm white-hat, not gonna hurt anyone) ^ black-hatters make me sick, though they do provide better information as they ACTUALLY look into the stuff.
one of my black-hat friends (online) has a friend who disabled a Win8 RAT on one of his schools compys using Python and surprized his computer teacher.
I'm trying to get info on it, but my friend hasn't been able to get in contact with him...
I was wanting to take control of the MS RAT only to post a dialog warning everyone how unsafe they are with that OS. but I can't do that, I'll possibly get jailed for it. one of my local friends knew about black hat software when it was just coming out (which the initial intent there was to help people) and they were jailed for breach of privacy on local networks. (the same thing can be applied to me if I was to take my action)
it's just like our corrupt gov't to jail someone for helping people 9_9
so yea, the absolute BEST I can possibly do is warn everyone that the RAT exists in newer Windows OS's and hope they're smart enough to move away from it.
if you don't know what a RAT is: it stands for either of "Remote Administration Tool" or "Remote Access Trojan". what a RAT does is allow a host to take control of a user's computer and even disable the user's input.
normally the infection would be done using a catalyst (an EXE disguised as an installer or patched with the RAT client)
x86 builds of WinXP (which again I state are not safe) also have their own RAT known as csrss.exe
I believe this was patched and fixed in XP x64. XP64 also removes most unsafe ActiveX controls and improves stand-alone network security (same implementations as 7 I believe)
Aero (from 7) can most likely be ported over XP wih wrappers and extended libraries. (along with version control to extend the support wrongfully blocked by MS)
yes, this means most of the stuff that now works with 7 should work near flawlessly with XP. I just wish someone would actually get off their lazy butts and actually port it. (I can't as I can't program in C++, and as everyone knows, have UMC/UGC/UGE to deal with)
aren't programmers supposed to evolve with the media they are working on, instead of keeping on the same outdated version just because reasons?
so you're saying you want programmers to evolve and support a life where you have no freedom over your personal belongings and are fully controlled by a corrupt company??
or let me put it this way... would you want to have naked sex in the middle of your most public mall's parking lot with everyone looking at you?? (I know I wouldn't, and this is why I don't support WinVista and up)
I'm not for that, where MS has been basically supporting it and enforcing it (I know I'm putting it waay loosely here)... think of what happens when people take control of the MS RAT (which I'm finding out some people already have, though it's not verified yet). ^ I can't post proof as I don't have a recording of the call >3<
I'm trying to get people to think smarter... I only support what's safe, and if that means you guys can't use it well (if at all) then oh well, use something better than what MS is taking advantage of the public with. (use something I support and you won't be harmed much by outsiders while being able to be free)
don't just use what's being blindly thrown at you and expect it to work as everyone wants. be smart about it. go back and do research on it to verify these arguments. don't listen to anything by MS, listen to what people have found in windows by MS.
heck, I don't even know everything about how windows works, but I do have enough sence to know I don't want to be controlled.
MS dropped XP because they built an interface that seems to work much more decently (Aero) and put a RAT in the kernel of every OS running Aero so they could enforce their control.
MS only says they remove stuff or certain things are safe and what not... if you know as much about windows as me, you'll be able to see them lieing through their teeth. 7 is not much more safer than XP, which XP64 is alot safer than any x86 version of XP.
have you been paying attention to what MS has been doing since Bill Gates retired?? they've basically become 10x more corrupt (and that's putting it lightly)
people need to wake up... I personally am sick of all this following standards BS and crap going around... what's this garbage about XP being dropped because it's 13 years old? isn't Linux older? I don't see people dropping support there... in fact, I see the support getting even better with NO control on Linux
if you wanna try to argue with me, get about 5 years of knowledge about everything first before even addressing me on it.
so in other words... ur program wont work for Win7 or 8 users? if so, then thats an issue ur gonna have to handle as most ppl dont use XP anymore... as for me, I don't even know any1 that uses XP anymore lol
oh I'm not saying it won't work but I can't promise you won't have issues, despite the fact I'm only using cross-platform libraries features.
if you do have any issues, I will blindly try to fix them.
just to mention I feel sorry for anyone who stores personal information on a Win-Aero compy (if you think you're safe and private, think again) (Aero is not used by XP or lower)
XP64 is the safest OS, it has most of the safety improvments in Win7. I'm not going into a whole rant over it, I'm just saying I've done the research.
just switched to Linux :3 expect Wine support by the update ;3
*hopes this doesn't break windows support* (I'll need to install a VM before I'll be able to test on XP64 again)
Why XP64 and not 7 or 8? even through VM, I will never support MS's new RAT (Vista, 7, and .
other info: apparently XP (x86 builds) also had a RAT interface that I just learned about... csrss.exe, which provides network access to remote administration and allows processes to be started and overridden anonymously.
if it can be patched, great I think XP64 already has it patched, and does not include the newer RAT. (XP64 works on x86 systems)
well, I won't say it's a bad idea, but letting it happen will make me lose faith in the project...
I have no faith in a project when the developer is doing things for money rather than for the benefit of others.
if the result is still for the benefit, then great, but due to the money aspect, brbx will never look good to me if done like that.
if (as a retort) you want me to pick it up, don't bother: 1: I now hate C# with a passsion and will only learn it for reading code (not writing it) 2: I'm already working on something far more advanced and have many more communities (not just hacking communities) supporting the idea
to add a bit of personal info to that, and it's something that's always been known... I hate money, and will always do what I can for free. (I would rather make an attempt to get rid of money than try to actually make it)
You guys should continue developing BrawlBox so that it can be compatible with PSA, as well as add other functions like importing from Blender to BrawlBox, or those bugs with Sawnds imports and stuff.(I've heard a lot of complaints about those 3 things, though the importing from Blender I myself have complained about.)
I only kindof agree... I say just to fix the DAE export so materials don't mess up with blender... (that, and the normals have to be fixed after importing)
the only part of me that says to drop the multi-format support is because of my program, UMC... once UMC's capable of importing and exporting an MDL0 of any version, BrawlBox won't really need those extra formats.
the up-side, when a format in UMC doesn't work right, it'll be extremely easy to correct. (unlike BrawlBox, UMC isn't hard-coded, and the language is fixed up for noobs) ^ with UMC, there's no jumping through hoops to add support for a new format.
not trying to promote my program... (even though it REALLY sounds like it) I'm just stating my feelings as to why brbx should stay MDL0 only.
once this gets fixed, I can start work on the material, texture, and image export functions, and then hit up the import interface as well as the header function. (everything should work the same as it should (and more) in the 3.0 release) I also have to work on the data functions, which unfortunately won't be able to type-check like in 3.0... the interface there is a bit complex to simply merge
So you already have it figured out have to fix the mdl0 for exporting into brawlbox? If so I'm not really needed then. Because I be honest i really wasn't sure on what I needed to do.
oh so that's what you wanted to learn the scripting for. well, I havn't really been able to work on MDL0 exporting as I didn't have a solid interface.
if you want to help out with finishing the script, I can add you to my box though it may take a bit before I have anything to test out the script on. >_> (for one, the pointer system in 3.0 will help to do it properly)
but in any case, you lead me into believing you wanted to add a format to UMC. again, please wait until the next release, where I'll have a solid scripting interface.
Okay I'm looking at the python 2.7.7 shell thing right now. And I noticed in umc there is a mld0 format somewhat done I just wondering where that is at in function and that it what i should be editing/figuring out since I was going for a mdl0 format.
ah, you can find that in UMC/scripts/NTDO_MDL0.py though with the current release, you can't export well enough... (nothing more than what the OBJ format supports really)
this next release here soon should fix that as I've ported the export functions and am currently working on the import functions. though right now I'm porting the OBJ script to test that the export functions at least work.
in the current version you have, the scripting interface didn't follow any standards, and as such it was designed horribly.
as for the error, I'll be sure to look into that not sure why that hasn't happened to me :/
basically, a UMC script IS a python script, but you don't use import or open()/file(), and everything needed is already handed to you in it's simplest form. there are some occurrences where you may need to import, but file management is entirely done in UMC.
I'm trying to work on simplifications for everything, so tell me if something's a little too complex for comfort.
Show Posts
.