Nick Brutanna
Jun 16, 2015, 9:06:52 PM6/16/15
to sessionbud...@googlegroups.com
"How to Locate Session Buddy Data on Your Computer"
OK, question one.
Does Chrome REQUIRE you to store stuff in the directories selected? Because it's probably one of the worst POSSIBLE places to store session data. If Chrome F***s up, the session data gets F***ed up.
Session data -- if possible -- OUGHT to be stored in an entirely separate location, which is INDEPENDENT of Chrome's installation, etc.
The entire purpose of saving sessions is to allow later referral to them. And if Chrome F***S up, and mine did, you can lose a LOT of saved information.
Question two:
Session data -- if possible -- OUGHT to be stored in an entirely separate location, which is INDEPENDENT of Chrome's installation, etc.
The entire purpose of saving sessions is to allow later referral to them. And if Chrome F***S up, and mine did, you can lose a LOT of saved information.
Question two:
Assuming the answer is, "Chrome forces us to save stuff under its aegis", then the obvious question is, can you at least rig it so that session data gets SYNCed, so there's at least SOME chance of recovering stuff after Chrome eats its shorts, as it's going to do somehow once every year or two in my experience.
Even if you had a standalone program that echoed the chrome saved sessions to a backup location, that Would Be A Real Good Thing. Then you could run it once in a while and only lose recent sessions.
as it is, I lost session data going back almost a year.
All because Chrome is designed by idiots (the recent "bookmark improvement" crap shows that).
=====
For anyone reading this: Microsoft's "BIG BALL OF GOO" storage mechanism is a completely F***ED up and incompetent programming design. It's usually for lazy idiots who won't, or can't, be bothered to learn how to write stuff out to files on their own, and instead use some idiot API call to do it that stores things in some giant "ball of goo" storage location that is susceptible to pretty much ANY problem that screws up a program.
So don't be a lazy programmer. Avoid storing stuff in the "ball of goo" whenever possible -- whether it's Chrome's or Microsoft's Registry or whatever -- and store stuff in your own location with your own methods using just slightly higher levels of the storage classes -- even if this is just a backup copy of the relevant information. Yeah, it's more work but the result is a MORE ROBUST application that can recover properly and ELEGANTLY from crashes and all the little and varied screw ups that are an inevitably part of programming within contexts you have no direct control over.. And there's a reason people curse at Microsoft and Bill Gates -- because Windows is BRITTLE, and breaks when you look at it funny. There are limits to what you can do about that, but emulating their abysmally incompetent design patterns is one thing all programmers can make it a case to avoid... preferably like the plague.
Even if you had a standalone program that echoed the chrome saved sessions to a backup location, that Would Be A Real Good Thing. Then you could run it once in a while and only lose recent sessions.
as it is, I lost session data going back almost a year.
All because Chrome is designed by idiots (the recent "bookmark improvement" crap shows that).
=====
For anyone reading this: Microsoft's "BIG BALL OF GOO" storage mechanism is a completely F***ED up and incompetent programming design. It's usually for lazy idiots who won't, or can't, be bothered to learn how to write stuff out to files on their own, and instead use some idiot API call to do it that stores things in some giant "ball of goo" storage location that is susceptible to pretty much ANY problem that screws up a program.
So don't be a lazy programmer. Avoid storing stuff in the "ball of goo" whenever possible -- whether it's Chrome's or Microsoft's Registry or whatever -- and store stuff in your own location with your own methods using just slightly higher levels of the storage classes -- even if this is just a backup copy of the relevant information. Yeah, it's more work but the result is a MORE ROBUST application that can recover properly and ELEGANTLY from crashes and all the little and varied screw ups that are an inevitably part of programming within contexts you have no direct control over.. And there's a reason people curse at Microsoft and Bill Gates -- because Windows is BRITTLE, and breaks when you look at it funny. There are limits to what you can do about that, but emulating their abysmally incompetent design patterns is one thing all programmers can make it a case to avoid... preferably like the plague.
Hans Meyer
Jun 16, 2015, 11:24:42 PM6/16/15
to sessionbud...@googlegroups.com
Yep Chrome requires the target of automated local data saves to be under its directories, for security's sake. I believe this is true for all browsers. It's problematic for SB because the recoverability of the local storage mechanism is not industrial strength, which is one reason we're working on a cloud storage and sync solution.
We rolled out in-app manual backup a while ago to help mitigate data loss scenarios in the interim. See: How to Back Up and Restore Session Buddy Data. This is currently the quickest/preferred method for backing up SB data. We also recommend that you include the SB local user data folder in your scheduled system backups.
If you're using Windows 7, you may be able to recover your SB data from a shadow copy of the local user data folder. Let me know if that's the case and I can walk you through the restoration process if you like.
Hans
--
You received this message because you are subscribed to the Google Groups "Session Buddy Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sessionbuddy-dis...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages