If this was any other company like Microsoft, Every one will enjoy.
Google Calendar Unexpectedly Leaks Private Information
131–138 of 138 posts
Re: Google Calendar Unexpectedly Leaks Private Information
#132A quick note to say I've received an email from Google - the calendar team are treating this as a bug and are implementing a fix.
Hopefully it should make it a lot more obvious to users when a meeting invitation is about to be sent.
Re: Google Calendar Unexpectedly Leaks Private Information
#133Re: Google Calendar Unexpectedly Leaks Private Information
#134Privacy, where it exists, creates impedance in Google's cash flow because it requires designing for some n sigma tail where n does not entail statistical significance and the case analysis must be very fine grained. Google doesn't have a category labeled "private" information". It never has and creating one is not planned. Privacy is not amenable to computer science. It is a social concept not a technical one. The cl…
Do you have a source for this? I've worked on user data and privacy-related stuff (I work on Maps, not Calendar) and everyone involved took it extremely seriously. We sent PMs back to the drawing board more than once when we found edge cases with potential privacy issues.
Google's single identity policy is an obvious example.
Sharing that Google identity with other websites when that identity is logged into Google is a less obvious one.
Analytics, cookies, personalized search results, etc. take it to Google's very core.
Driving around collecting WiFi data, storing WiFi passwords, reading documents via Docs and email via Gmail, and just plain crawling the web don't embody any common language notion of privacy.
Instead security stands in for it. Two factor authentication for a Google account is an example. It keeps a person's account secure but does not enhance privacy because Google will still share and slice and analyze everything that can possibly be associated with that account.
Re: Google Calendar Unexpectedly Leaks Private Information
#135Earlier quoted context omitted.
Despite the name Pydio seems to be developed in PHP too.
Which changes nothing.
It changes nothing but it is a fact. The original ancestor of this thread was put off Owncloud by the fact it was PHP and Pydia was offered as an alternative. The name suggest at least to me that it would be Python based.
Now whether the PHP should put us off is a separate question. I have probably unfair doubts about the quality of things developed in PHP based worrying about the sort of people who would choose it when they have a free choice (see fractal of bad design post). However I personally don't want to learn PHP so I would prefer something in Python, Rails or possibly even Node (I've a feeling that I'm going to need to learn Javascript one day), Java, C or C+++ so that the barrier to me tinkering/fixing is lower.
Re: Google Calendar Unexpectedly Leaks Private Information
#136Earlier quoted context omitted.
Which changes nothing.
It changes nothing but it is a fact. The original ancestor of this thread was put off Owncloud by the fact it was PHP and Pydia was offered as an alternative. The name suggest at least to me that it would be Python based. Now whether the PHP should put us off is a separate question. I have probably unfair doubts about the quality of things developed in PHP based worrying about the sort of people who would choose it w…
You read too much into things:
> The original ancestor of this thread was put off Owncloud by the fact it was PHP and Pydia was offered as an alternative.
No, I said I preferred Pydio over ownCloud. You added the subtext to my post.
> The name suggest at least to me that it would be Python based.
Only if you place too much emphasis on naming conventions. Names are in fact just arbitrary labels, thus not everything that begins with "py" has to be written in Python.
> Now whether the PHP should put us off is a separate question. I have probably unfair doubts about the quality of things developed in PHP based worrying about the sort of people who would choose it when they have a free choice (see fractal of bad design post).
I'm aware of the Fractal Of Bad Design blog post and you're using that to justify your conclusion that 2+2=5. Just because a language might be -in our opinion- complete garbage to develop in, it doesn't mean all code developed in that language is garbage. And you're also making the assumption that all developers choose PHP because it's easy; where as many of these projects are actually written in PHP because it makes it easier for end users to deploy.
> C or C+++ so that the barrier to me tinkering/fixing is lower.
If you think writing a web application in C or C++ (two pluses) lowers the barrier of things that can go wrong or the amount of tinkering you'd need to do, then you clearly don't know what you're talking about. Sorry, but that last part just struck me as the stupidest thing I've read in a long time.
Re: Google Calendar Unexpectedly Leaks Private Information
#137Earlier quoted context omitted.
It changes nothing but it is a fact. The original ancestor of this thread was put off Owncloud by the fact it was PHP and Pydia was offered as an alternative. The name suggest at least to me that it would be Python based. Now whether the PHP should put us off is a separate question. I have probably unfair doubts about the quality of things developed in PHP based worrying about the sort of people who would choose it w…
You read too much into things: > The original ancestor of this thread was put off Owncloud by the fact it was PHP and Pydia was offered as an alternative. No, I said I preferred Pydio over ownCloud. You added the subtext to my post. > The name suggest at least to me that it would be Python based. Only if you place too much emphasis on naming conventions. Names are in fact just arbitrary labels, thus not everything th…
Sorry I though this: https://news.ycombinator.com/item?id=7107851 was an ancestor I got my thread branches slightly confused. I wouldn't have posted it if I hadn't.
Most computer software named pySOMETHING is Python but I didn't assume and went and looked in the repo.
I said that my feelings about code written in PHP were unfair and you are right that ease of deployment is a valid reason to develop in it. I did not say that all code developed in it or developers for it are garbage but I do treat it as a slight warning flag. The big thing is that I don't want to learn enough to be working around gotchas in the language.
Yes C or C++ aren't the obvious choice for a web framework and would probably put me off to some extent but I am sufficiently familiar with them to evaluate how clean the code is and tinker here or there if necessary. Of languages that I don't currently know well that I might be prepared to learn some more to tinker are the functional programming languages (Scala, Haskell, ML) I might be interested in anyway or JS/Node.
In terms of the stupidity of using a C/C++ based web framework Apache can probably be used as a basic web framework and I've heard about people using Postgres to do the templating not just managing the data so it isn't implausible to use C/C++.
Re: Google Calendar Unexpectedly Leaks Private Information
#138Earlier quoted context omitted.
You read too much into things: > The original ancestor of this thread was put off Owncloud by the fact it was PHP and Pydia was offered as an alternative. No, I said I preferred Pydio over ownCloud. You added the subtext to my post. > The name suggest at least to me that it would be Python based. Only if you place too much emphasis on naming conventions. Names are in fact just arbitrary labels, thus not everything th…
Sorry I though this: https://news.ycombinator.com/item?id=7107851 was an ancestor I got my thread branches slightly confused. I wouldn't have posted it if I hadn't. Most computer software named pySOMETHING is Python but I didn't assume and went and looked in the repo. I said that my feelings about code written in PHP were unfair and you are right that ease of deployment is a valid reason to develop in it. I did not s…
> Sorry I though this: https://news.ycombinator.com/item?id=7107851 was an ancestor I got my thread branches slightly confused. I wouldn't have posted it if I hadn't.
That's ok, we've all done similar things :)
> Most computer software named pySOMETHING is Python but I didn't assume and went and looked in the repo.
This isn't named 'pySomething', this is named 'Pysomething'. It's not camel cased like a lot of python software is.
>I said that my feelings about code written in PHP were unfair and you are right that ease of deployment is a valid reason to develop in it. I did not say that all code developed in it or developers for it are garbage but I do treat it as a slight warning flag. The big thing is that I don't want to learn enough to be working around gotchas in the language.
When you're rolling out software that's accessible to the world via the web, then all languages will have their "gotchas" which you need to work around. Even C++ (in fact especially C++ since it's prone to buffer overflows and that's a pretty common attack vector for remote code execution)
> In terms of the stupidity of using a C/C++ based web framework Apache can probably be used as a basic web framework and I've heard about people using Postgres to do the templating not just managing the data so it isn't implausible to use C/C++.
Apache is only the web server, a web framework would consist of the tools required to build dynamic web pages (including the templating you mentioned in Postgres, but not just limited to), parse the HTTP request data (which Apache does do) and connect to the db. This is where things like CGI come in to play, but that's massively slow. Other languages have their own C++ hooks that compile into Apache (perl -> mod_perl, Python -> mod_python, etc) so they can provide a webframe work while tying closely with the Apache web server, but Apache on it's own wouldn't give you enough tools to provide a web framework.
In addition to that, you don't want to offload your templating to your database because that will be slow and will cripple your site. In fact most sites are built around minimizing DB queries rather than thrashing the database. This is why templates are cached (in fact whole pages are where possible) and even db lookups are cached with tools like memcache.
So even ignoring the fact that you're missing a whole stack of essential frameworks to build modern web applications, you're also setting yourself up for building a slower and buggier site than most of the PHP sites are that's already online.
If you really want to develop sites in a C/C++-like language, then you're much better off developing in Java, Go (lang) or C#. But honestly, trying to build a pure C++ website would cause you more problems than if you developed in PHP.
I'm sure you're very adept in C++, I'm not trying to dismiss your abilities here, but I genuinely post from experience as I've developed in about a dozen different languages, build websites and manages web servers for a living. Like yourself, I've spent a lot of time in C/C++ over the years and even I wouldn't dream of building a website in either of those languages (in fact since my work as drifted more towards web and sys admins roles, I've found I rarely touch C++ these days)