![]() |
|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#61
|
||||
|
||||
Quote:
![]() That being said, I agree that if you don't agree with a companies privacy policy, then your only real alternative is to go with another company/solution.
__________________
Batch Metadata Tools (User Guides) - SageTV App (Android) - SageTV Plex Channel - My Other Android Apps - sagex-api wrappers - Google+ - Phoenix Renamer Downloads SageTV V9 | Android MiniClient |
#62
|
|||||||||||||||
|
|||||||||||||||
Quote:
In the grand scheme of things, that's correct. However, in general, the loopholes aren't nearly as great. Quote:
If you think that a dissenting opinion qualifies as trolling, than you need to grow up. Quote:
They have the same reason many companies do - profit. If they started selling useage data, it would be a windfall. But you're ignoring the other part of why I dislike call home routines - the data transferred is almost never properly encrypted, which means that it's at risk from others. Quote:
Sure. That's not an analogous comparison. This isn't about hiding, it's about protecting. My posting on a public web forum doesn't give out any information I'm not aware of, and I know exactly when it happens. You can't say the same about a call home routine. Don't take a slice of my stated concerns out of context. Quote:
At this point in time, that's fine. I'm satisfied with the solution of a third party EPG (well, semi-satisfied, given the difficulty of implementing it cleanly). At this point, I'm simply responding to general comments about the concerns about a call home routine. Quote:
You don't understand - this has nothing do with with any privacy statement. It has to do with minimizing the chances for a data leak. With Sage, the developer and the place you're logging into for EPG is the same. Couple that with their existing statements that they *do* collect data, and the motivation to collect more, and you have a situation where you're putting all your eggs in one basket - so to speak. On the other hand, if I use a third party app to get data from a third party service (not the same as the app's developer), than the chances of a breach are much much slimmer. In addition, it's very easy to configure your firewall so that the app can ONLY access the service's site, and you prevent it from calling home to the developer even if it was set up to do so. You can't do this with Sage (with its standard setup), because you can't block access to the developer without blocking access to the primary EPG servers as well. So, it has nothing to do with who to trust - you simply minimize the possible ways for your data to be leaked without your knowledge and consent. Quote:
My position as a future customer is that I don't like having to rely on anyone's word on the matter. I prefer to be able to ensure my privacy without losing functionality of the program. That's all. Quote:
Sandor, I appreciate the suggestion. The problem is that a call home routine still causes issues. First of all, I don't know if my name and serial number are being sent as part of the data exchange - I don't want either going out on the net without my knowledge and consent. There's also the potential for my system and network information to go out as well - this gives additional leverage to someone trying to break through my systems. And seperate from all that, there's the potential that useage data will be sent out - if not now, then possibly in the future. And as I said earlier, in an age where the government wants to know what books people are borrowing from the library, I'm damned well concerned about protecting information about what I watch. Quote:
Incorrect. As I stated in a recent post, you can block access to all sites except the service you choose to use for EPG data. That would prevent almost all call home routines from succeeding, unless the app was coded by the service you use (which is why I wouldn't do that). Quote:
Try learning some tolerance and having an open mind. It will do wonders for your ability to learn from people and not come off as a... well, fill in the blank as you see fit. As for why bother emailing, it was to see if there was a solution to my concern. The possibilities that have come up address the issue without having anything to do with who to trust. As for my consuming person-hours - I was trying to ask a question and have a discussion. This is usually one of the foundation actions towards learning - you shouldn't dismiss it so quickly. And my running a packet capture would be useless in this case, because the point is that if a call home is allowed, the information exchanged could change at any point. Quote:
Read my posts again. My comments had absolutely nothing to do with the developers of SageTV, personally. It has to do with the fact that when you open your privacy and data to others on nothing more than the say-so of their good intentions, you will almost always get burned. As I stated several times earlier, a call home routine is a risk even if the developer has perfectly good intentions and keeps to them. The fact that the data is being sent at all means that it can be intercepted by others. I find it ironic that people keep misreading what I'm saying, or taking things out of context - and then accuse me of trolling, or fear mongering, or insulting the Sage developers. Quote:
Quote:
I apologize if any of my comments came across as condescending. However, I did counter suggestions that I'm being over-cautious because history and experience shows that my concerns are based in fact and not paranoia. Let me turn this around - imagine if you were trying to say that it's important to look both ways before crossing the street. If someone tells you that you're being over-cautious, you have the foundation to say that it is a factually (and not just by opinion) based concern. It's also not incorrect for you to say that a person who says it's not important to look before crossing isn't aware of the dangers. That has nothing to do with being condescending, and it's not incorrect either. Quote:
Then, as sad as it is, it's only a matter of time before one of them gets robbed or worse (assuming that it hasn't happened already). I don't say this to be melodramatic or pessamistic - it's a fact of life. If you leave your money out in the open, someday someone's going to take it. Quote:
Well, my point was that I wanted to find a way to work with Sage despite my issues with their call home routines. The pick-up-your-ball-and-go-home approach doesn't always work in real life. Most of the time, you have to adapt, and that's what I was trying to do. Edit: After re-reading this, I realized how pessamistic my first comment comes off as, despite my intentions to the contrary. Let me try adjusting this by amending my example to say that if you leave your money out in the open, there's a pretty decent chance that someday, someone's going to take it. Last edited by Opus4; 06-27-2008 at 03:22 PM. Reason: merged 12 consecutive posts |
#63
|
|||
|
|||
Quote:
![]() P |
#64
|
|||
|
|||
Quote:
A non-malicous call home function usually exchanges identifying information - so you have the potential for name and serial numbers going out. Aside from that making it easy to connect a name with the IP, it also gives out a free serial number. I've seen people be accused by developers of giving out their serial numbers when the true culprit was their own call home routines making it available to anyone sniffing packets. In addition, from what Sage has openly stated, information about my system goes out. First of all, there's an issue of principles - it's like someone opening your front door and peeking in because they want to see how you've furnished your home. Just because they want it doesn't mean they have a right to it, and doing it without asking for permission first is rude and invasive. Aside from that, I'm sure many of you have seen people use personal information when naming computers, volumes, or folders. If someone named their computer after their children or pets or likes or dislikes, now the simple transfer of "technical information" isn't so simple anymore. And the information transfer isn't as sanitary and non-personal as you might have originally thought. Aside from the fact that Sage has no right to take such data without asking for permission first, I also wouldn't want any one sniffing my packets to find it either. Not even counting the personal information that could be present, knowing the OS, machine specs, and network structure gives leverage for someone to break into your network and systems. Concerns about transferring location based information should be self explanatory. And I spoke earlier about the issues of viewing habits. It's no one's business but mine, and I don't like the possibility of that going out. It has potential ramifications that are non trivial to say the least. |
#65
|
|||
|
|||
You say that they're taking this information without your permission but by installing the software you're agreeing to their EULA which probably includes an agreement to send certain data along with EPG updates.
While click-through EULA's are a bit shaky to begin with you can't say that you didn't give them permission. By installing the software you're agreeing to their terms and conditions of it's use.
__________________
Server: i5 8400, ASUS Prime H370M-Plus/CSM, 16GB RAM, 15TB drive array + 500GB cache, 2 HDHR's, SageTV 9, unRAID 6.6.3 Client 1: HD300 (latest FW), HDMI to an Insignia 65" 1080p LCD and optical SPDIF to a Sony Receiver Client 2: HD200 (latest FW), HDMI to an Insignia NS-LCD42HD-09 1080p LCD |
#66
|
||||
|
||||
It's nice to know that SageTV allows you to use 3rd party EPG data. It is essentially an opt out of the phone home at the expense of only the function that requires it. Not bad if you ask me.
Aloha, Mike
__________________
"Everything doesn't exist. I'm thirsty." ...later... "No, it's real!!! I'm full." - Nikolaus (4yrs old) |
#67
|
||||
|
||||
Twinkle, not to be an ass, but i *am* assuming you do not have a bank account or credit cards or own your own home or search using google/yahoo/etc....
i completely agree with the idea that people need to be wary in terms of protecting their personal information - heck, here in Philly we just had a twenty-something year old couple get arrested for identity theft. they lived a rich person's lifestyle on the identities of others. the kicker? they stole all the identities and credit card numbers, etc the old fashioned way - they snooped around homes and apartments when they were invited over. nothing high tech, just an old fashioned confidence trick. ...then they are released on bail, the girl moves to california awaiting trial, starbucks hires her stating "innocent until proven guilty" blah blah blah... and she gets caught copying down and using customers credit card numbers.... so yeah, technology is watching all the time, we know that, but it is the dude living next door reading your mail that will screw you royally.
__________________
MacBook Core2Duo 2 ghz nVidia 9400M GPU 46" Sammy HLP4663 720p DLP 2x HDHR, all OTA QNAP TS-809: 12.5 TB for Recordings/Imports/TimeMachine/Music HD200 via 802.11n in Living Room 802.11n client in bedroom |
#68
|
||||
|
||||
I think the original question was answered and now things are just going in circles w/a few insults thrown in here & there, so the topic is now closed.
- Andy
__________________
SageTV Open Source v9 is available. - Read the SageTV FAQ. Older PDF User's Guides mostly still apply: SageTV V7.0 & SageTV Studio v7.1. - Hauppauge remote help: 1) Basics/Extending it 2) Replace it 3) Use it w/o needing focus - HD Extenders: A) FAQs B) URC MX-700 remote setup Note: This is a users' forum; see the Rules. For official tech support fill out a Support Request. |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Audio Sync Issues with SageTV 6.3 | ptzink | SageTV Software | 19 | 05-08-2008 11:24 PM |
Refresh issues? | DualQuad | SageTV Beta Test Software | 0 | 11-14-2007 03:22 PM |
HD and transcoding issues with 6.2.10 | jvl711 | SageTV Software | 39 | 11-13-2007 08:34 PM |
My List of Issues with SageTV | dshields | SageTV Software | 5 | 05-20-2006 10:36 PM |
** Two major HDTV bugs Identifed!! ** May cause performance/stuttering/audio issues | mkanet | SageTV Software | 7 | 02-04-2006 11:43 AM |