mnkypete

Needs a VisualStudio option?!

This is really a great move. C# is an awesome language and deserves to have a future on Mac & Linux. Microsoft is changing for sure.

Based on the fact that you can test this via visiting an URL, I'd guess it is. I think v2.0 of the PS4 firmware is about to be released, maybe it's fixed in this version.

It is apparently based on this: WebKit CVE-2012-3748 (http://www.securityfocus.com/bid/56362)

I feel the same way. In my opionion, Outlook peaked with 2010 but they are missing new ideas. There is SO much you could do if you would think just a little bit out of the box.

One could think of contextual information added to emails, like detecting invoice numbers, intellligent attachments (e.g. recognizing Dropbox links etc.) and so on. I really hope there will be some client like this in the future, if not, we'll build it :)

We should do a support group... I haven't done recurring meetings yet, but that timezone stuff is bad enough on it's own.

That would've been too easy - instead it's now used in fewer places, but with new rules ;) When it's long-pronounced, ß is still used, like in Fuß or Stoß. In words like Fluss it's replaced with ss.

I really don't like how Samsung handles this.. I couldn't use my TV all morning to watch Youtube (I know, problems..), just because they think "If Samsung is down, don't bother opening the Youtube app". Seriously, what the heck...

Also, this is not the first time this happens.. I mean their data center was on fire (www.engadget.com/2014/04/20/samsung-com-outage-sds-fire/), but isn't there some failover?

maybe for REST, but seriously, if you ever need to test SOAP services - I hope you don't - this is probably the best there is..

I would not recommend that. I compiled Chromium a few month ago with my i7 desktop with 8gig ram and it took at least an hour to finish, if not longer. I don't think RAM is that much of an issue, but I wouldn't go lower than at least 4gig of RAM.

I think this is a very funny article because half of the stuff is simply wrong...

Disclaimer, I'm not actually using Outlook.com myself but I have a dummy account where I checked the following stuff.

1. The "delete" button, next to the navigation arrows is not a delete button. If you hover the button it says "Back to messages" and it does exactly that.

2. The top menu would be quite hard to operate if there weren't any visual cues which button you are hovering, but there are some - You can clearly see at any time which button you are going to click.. The placement of course can be discussed, but looking away while clicking will also not work on GMail.

3. It's argued that Outlook would not respect the "default" use cases. But then, I don't get why it's confusing that your e-mail is classified as junk if you click the "Junk" button. What should happen instead?

4. Reading pane is actually no mistake but used by MS since forever to name the place where your e-mail is previewed.

Great, thank you!

Thanks!

We are trying to be transparent about that - so the following is also mentioned in the installer wizard :)

TLDR; We are not sending any(!) data of your inbox to our servers. And we will never do!

When you install yasoon, there is a little registration wizard at the beginning which will register an account at our server. This is simpy to confirm that you are the owner of your e-mail address (we are sending an automated registration email afterwards). In addition, you can give a small profile which will make the UI a little more user friendly (profile image, etc.). This is also transferred to our server. However, this is completly optional and is currently not used anywhere. We may offer some collaboration features in the future, but this will also be opt-in to share your profile.

Besides that, we only log some serious errors which occur in our runtime, but we never send any data of your inbox out! No e-mail data, no tasks, no calendar items!

//Edit: In addition, the remote logging is disabled when you turn on the Dev mode, because we are only interested in production errors.

Thanks for the tip! We will look into it for sure! By any chance, do you have any resources on this topic available? When I researched this a while ago there was little to none information and all sources stated that it's impossible..

Hi,

I'm one of the founders of yasoon - unfortunately Microsoft does not offer any kind of API for Outlook on Mac. This makes it quite impossible to implement this.

In the long term we may provide something like this as an standalone app or an extension for Apple Mail - which ironically allows plugins.

Until recently I was working for a big software company (40k+ employees), where we were also using Outlook as the main communication tool (+ Lync recently).

The interesting thing was, that each person has found an own solution to the massive amount of information you need to keep and look up later. There were of course wikis, portals and stuff but most of the people always kept the most relevant information in their inboxes.

This would manifest in: - Folders with "Dummy"-Mails, used for storing notes - Actually using the notes function - 4 or 5 level deep folder hierarchies of mails - "Complex" categories on mails for finding information

I have no insight into the processes at Yahoo, but I suspect at least some of the things work similar over there. The problem is, migrating these kind of (mostly unstructured) information is painful and could take weeks - provided the new mail system would even support such an abuse.. If there is no alternative in place, the next step would possibly be One Note, or worse Notepad.

I also think Microsoft missed a huge opportunity by not positioning Outlook as more than a e-mail tool but a shared information system. I even worked in a team for a few month, which developed a "Mail Publish" solution, where you've got a button in your Outlook which would upload your mail to a server and index it, so the whole team could get to the information..

(disclaimer: my startup depends on Outlook, but this is less relevant to this specific problem)

Thanks :) I'll see if the SSH solution is feasible.. The good thing is, that we have very little server code at the moment (as much is done on client-side), I hope we are not that bad at application code right now ;)

Thanks to all, I guess I'll stick to these basics first!