[FEATURE REQUEST] System specs history

[bug]

I have the opposite problem, I've had too many different rigs and half of the companies are no longer around...
I know my first real DIY system used a QDI board and an AMD 5k86-P75...

I didn't have that many builds, but I still remember when I got my first (and only) Abit mobo. NF7-S v2.0 was fresh out of stock so I had to pony up for an AN7.

 

[Kursah]

If the main supporting argument for this feature request is merely to remember what we previously had, why not do it with our own local documentation methods, resources and time?

IMHO, folks need to be responsible for their own historical documentation. This responsibility for maintaining long-term system build history shouldn't fall on TPU as far as I'm concerned, that sets an inappropriate expectation for a freely accessible community.

Not only that, having more direct control of your data should be brought into consideration here, if its shared, if it is public or not, where it is stored, etc. It doesn't matter if you maintain it in your controlled environment versus TPU's databases, there is an inherent risk. Sometimes things happen with upgrades or corruption, data has been lost before that wasn't restorable. Data could be lost again...if the expectation is set that TPU maintains historical system specs for folks that can't remember, and that part of the database gets corrupted or wiped out that can't be restored for any given reason now there's a problem. If you delete it or lose it, it is your problem. That's how it should be.

My solution to this problem is by maintaining a spreadsheet over the years where each page is dedicated to build, build notes, OC info, upgrades, pictures, etc. Keeps it simple to add a new build at any time, I even have a template page that I duplicate to speed up the process. Overall I'd say that method has been extremely easy to accomplish with my own time, resources, storage, and management. Toss in cloud replicated storage for redundancy and reliability, keeps it simple and easy to manage. That seems like a win that some may favor here. If I want to look at previous build info or share it with someone I am able to copy/paste or relay it, when I don't, it doesn't matter because I have my copies regardless. K.I.S.S. principal here folks.

Even using Notepad++ or Notepad locally would accomplish the same thing just not publicly nor solely reliant on a single entity or service that could just as easily remove it, or lose data in an upgrade/modification/crash.

I am one of the ones that may be considered "annoying" by some folks here for posting my son's builds in my sig, that's okay it won't bother mobile folks at least. I also am able to fit 2 builds into my System Specs, could do more with reduced details and more separated formatting. I feel there's already appropriate solutions that exist, though I can see where some folks may want this.

 

[bug]

If the main supporting argument for this feature request is merely to remember what we previously had, why not do it with our own local documentation methods, resources and time?

Except that it's not. Seeing how people's builds evolved over time can tell you a bit about the person themselves (e.g. is this a guy that bought P4 over AthlonXP?).

 

[TheoneandonlyMrK]

I voted no.

Personally, I don't care about people's old systems, nor having a random tech forum keep a history of mine. Most have trouble filling out their specs in the first place, nonetheless have multiple systems. And if this is only for your eyes, then I really do not see a point. TPU isnt a cloud backup for you system history.

GL.

Aww i liked the idea if a system log.

If the main supporting argument for this feature request is merely to remember what we previously had, why not do it with our own local documentation methods, resources and time?

IMHO, folks need to be responsible for their own historical documentation. This responsibility for maintaining long-term system build history shouldn't fall on TPU as far as I'm concerned, that sets an inappropriate expectation for a freely accessible community.

Not only that, having more direct control of your data should be brought into consideration here, if its shared, if it is public or not, where it is stored, etc. It doesn't matter if you maintain it in your controlled environment versus TPU's databases, there is an inherent risk. Sometimes things happen with upgrades or corruption, data has been lost before that wasn't restorable. Data could be lost again...if the expectation is set that TPU maintains historical system specs for folks that can't remember, and that part of the database gets corrupted or wiped out that can't be restored for any given reason now there's a problem. If you delete it or lose it, it is your problem. That's how it should be.

My solution to this problem is by maintaining a spreadsheet over the years where each page is dedicated to build, build notes, OC info, upgrades, pictures, etc. Keeps it simple to add a new build at any time, I even have a template page that I duplicate to speed up the process. Overall I'd say that method has been extremely easy to accomplish with my own time, resources, storage, and management. Toss in cloud replicated storage for redundancy and reliability, keeps it simple and easy to manage. That seems like a win that some may favor here. If I want to look at previous build info or share it with someone I am able to copy/paste or relay it, when I don't, it doesn't matter because I have my copies regardless. K.I.S.S. principal here folks.

Even using Notepad++ or Notepad locally would accomplish the same thing just not publicly nor solely reliant on a single entity or service that could just as easily remove it, or lose data in an upgrade/modification/crash.

I am one of the ones that may be considered "annoying" by some folks here for posting my son's builds in my sig, that's okay it won't bother mobile folks at least. I also am able to fit 2 builds into my System Specs, could do more with reduced details and more separated formatting. I feel there's already appropriate solutions that exist, though I can see where some folks may want this.

Any chance you might post your template, for a great idea I have to admit, sorry for dp if dp ill correct it.

 

[Flyordie]

My 2 cents-

Maybe not make it on the front page but as an added set of information in your profile for people to look at?

 

[R-T-B]

It's to see how people's preferences change over time. I still don't understand why people actively vote against this feature even though it means nothing if you don't use it.

Because the question is whether or not it's worth "significant development time" of our resident w1zzard.

To me, it's not. Would it be cool? Yes. But not worth a lot of dev time, and that is literally how the poll is worded.

 

[Jetster]

I have a build folder on my server. I keep track of every build I have completed. I barely check others builds so I don' see a need for it here

But maybe room for two or three current builds. If you look at my specs i have two build in there. My gaming rig and my HTPC

 

[Toothless]

Pen, paper, tape, wall. This isn't a personal archive.

 

[R-T-B]

is this a guy that bought P4 over AthlonXP?

That can also be misleading.

Case in point, I did exactly that, only to go AMD afterwords so long it was almost stupid (all the way up to Phenom II and almost even bought an FX *shudders*), all in response to the Northwood Horror.

 

[Solaris17]

Except that it's not. Seeing how people's builds evolved over time can tell you a bit about the person themselves (e.g. is this a guy that bought P4 over AthlonXP?).

So like, be used to thread crap and history shame someone with a legitimate stance on a topic? Hmmmm.

I'm starting to feel bad for the mods of general hardware. Or maybe it will be a quick way to weed out troublemakers?

 

[potato580+]

as for me i usually dont use system rig feature, i can just simple write it down if someone asking for, beside im too lazy for updating the list nor click the check rig button, anyway i do voting, is a yes fro me

 

[Kursah]

Any chance you might post your template, for a great idea I have to admit, sorry for dp if dp ill correct it.

Here's the basic one I run off of, or started with rather. My personal one has been tweaked a little since with slightly different font formatting, and space adjustments where I had more settings in my AMD build to tweak versus my old i7 builds for example. I tried to keep the layout basic enough that it's easy to use, I also like to use a staggered system with spreadsheets and bullet point/indent system when in documents. So you'll see that in-place here.

I'll admit, it isn't pretty to begin with, but makes it nice to add a new sheet to be it in Excel or on GSheets or in LibreOffice or wherever and sort it out how you want. For some this might work, for others, they may hate it. But feel free to take it, use it and abuse it all you want, for me it has proven useful as a sort of index of WTF is going on with current systems, how old systems were setup (as they usually get sold, yet I still maintain them), etc.

I use this to keep track of all systems, and System Info and Sig info in TPU to advertise current systems. Which I'm good with, if we have more expandability on what users can document, cool. But I do share the same concerns that @Solaris17 expressed to @bug 's response to me about supporting arguments, and expressing that seeing a user's build history can tell you something about them. Last thing I want to see is another tool for folks to troll and shame others in this community. That is definitely a major con and nobody has made an effort to suggest a mitigation for that, which also elevates my concern as to its intended use. That being said, I still feel status quo on the system specs feature is the best course moving forward for now. Not my decision, just my opinion. The community still has this topic to express their opinions and suggestions as well.

Anyways check out the attached spreadsheet and enjoy!

 

[Splinterdog]

I'm having difficulty taking this seriously because the OP hasn't even bothered to add his system specs in the first place.
That in itself is a bit of a head scratcher to be honest.
Besides, just add any of your old systems to your sig as others have done.

 

[dirtyferret]

Except that it's not. Seeing how people's builds evolved over time can tell you a bit about the person themselves (e.g. is this a guy that bought P4 over AthlonXP?).

I admit it...I bought a Windsor Athlon X2 6400 instead going socket 775 with a Core 2 Duo but I already had the AM2 motherboard and damnit I was cold and that Windsor helped heat up my apartment at the time!

 

[potato580+]

I'm having difficulty taking this seriously because the OP hasn't even bothered to add his system specs in the first place.
That in itself is a bit of a head scratcher to be honest.
Besides, just add any of your old systems to your sig as others have done.

ah good idea, i never tho to add on my sig, i always used phone broswer, no such sig appears becouse of that, thx for the tips

 

[DeathtoGnomes]

I Voted no.

User could change system specs and take a screenshot of them and save the image. but i forget if/where we have a image storage in our profile.

 

[TheoneandonlyMrK]

Here's the basic one I run off of, or started with rather. My personal one has been tweaked a little since with slightly different font formatting, and space adjustments where I had more settings in my AMD build to tweak versus my old i7 builds for example. I tried to keep the layout basic enough that it's easy to use, I also like to use a staggered system with spreadsheets and bullet point/indent system when in documents. So you'll see that in-place here.

I'll admit, it isn't pretty to begin with, but makes it nice to add a new sheet to be it in Excel or on GSheets or in LibreOffice or wherever and sort it out how you want. For some this might work, for others, they may hate it. But feel free to take it, use it and abuse it all you want, for me it has proven useful as a sort of index of WTF is going on with current systems, how old systems were setup (as they usually get sold, yet I still maintain them), etc.

I use this to keep track of all systems, and System Info and Sig info in TPU to advertise current systems. Which I'm good with, if we have more expandability on what users can document, cool. But I do share the same concerns that @Solaris17 expressed to @bug 's response to me about supporting arguments, and expressing that seeing a user's build history can tell you something about them. Last thing I want to see is another tool for folks to troll and shame others in this community. That is definitely a major con and nobody has made an effort to suggest a mitigation for that, which also elevates my concern as to its intended use. That being said, I still feel status quo on the system specs feature is the best course moving forward for now. Not my decision, just my opinion. The community still has this topic to express their opinions and suggestions as well.

Anyways check out the attached spreadsheet and enjoy!

I hadn't considered the negative aspects, the thought of a big historical list which I slowly beat and dragged back out of my mind was appealing oddly, ill go Doc's.

 

[eidairaman1]

If the main supporting argument for this feature request is merely to remember what we previously had, why not do it with our own local documentation methods, resources and time?

IMHO, folks need to be responsible for their own historical documentation. This responsibility for maintaining long-term system build history shouldn't fall on TPU as far as I'm concerned, that sets an inappropriate expectation for a freely accessible community.

Not only that, having more direct control of your data should be brought into consideration here, if its shared, if it is public or not, where it is stored, etc. It doesn't matter if you maintain it in your controlled environment versus TPU's databases, there is an inherent risk. Sometimes things happen with upgrades or corruption, data has been lost before that wasn't restorable. Data could be lost again...if the expectation is set that TPU maintains historical system specs for folks that can't remember, and that part of the database gets corrupted or wiped out that can't be restored for any given reason now there's a problem. If you delete it or lose it, it is your problem. That's how it should be.

My solution to this problem is by maintaining a spreadsheet over the years where each page is dedicated to build, build notes, OC info, upgrades, pictures, etc. Keeps it simple to add a new build at any time, I even have a template page that I duplicate to speed up the process. Overall I'd say that method has been extremely easy to accomplish with my own time, resources, storage, and management. Toss in cloud replicated storage for redundancy and reliability, keeps it simple and easy to manage. That seems like a win that some may favor here. If I want to look at previous build info or share it with someone I am able to copy/paste or relay it, when I don't, it doesn't matter because I have my copies regardless. K.I.S.S. principal here folks.

Even using Notepad++ or Notepad locally would accomplish the same thing just not publicly nor solely reliant on a single entity or service that could just as easily remove it, or lose data in an upgrade/modification/crash.

I am one of the ones that may be considered "annoying" by some folks here for posting my son's builds in my sig, that's okay it won't bother mobile folks at least. I also am able to fit 2 builds into my System Specs, could do more with reduced details and more separated formatting. I feel there's already appropriate solutions that exist, though I can see where some folks may want this.

I'd like to see some options in the vga bios collection be implemented but seems to been forgotten...