Notifications can be useful for web apps. A good rule of thumb is to only ask for permission when the user interacts with your app. For example, I ask for permission when the user clicks a button with the text "Enable Push Notifications" on the user settings screen. Then I let the user choose what kind of notifications they'd like to receive - typically CRUD actions for entities that the user cares about.
> A good rule of thumb is to only ask for permission when the user interacts with your app. For example, I ask for permission when the user clicks a button with the text "Enable Push Notifications" on the user settings screen.
This is absolutely the right way to do it. A little unobtrusive in-page suggestion to enable notifications is not a problem; I've enabled them for Slack via such a notification, for instance. But I'm never going to grant a site notification permission if it pops up the browser permission dialog without interaction.
Curious as to how PasswordMaker either uses weak crypto or "suffers from critical flaws". Master Password seems to be more flexible with features like password counter and a customizable password policy (this is especially cool if it is customizable per domain). Unfortunately for me iOS-only is a deal breaker. PasswordMaker has clients that run on everything. The two I use most are the "PasswordMaker Pro" Chrome extension and the PasswordMaker X Android app.
Hey, thanks for linking to my PasswordMaker app! :) I saw this linked on /r/programming earlier and mentioned it there.
I'm not sure how the password counter and "customizable password policy" (I'm assuming this refers to the password templating feature?) make Master Password more flexible, though. PasswordMaker offers plenty of configuration options you can tweak when you want to change the password for a site; I've begun creating multiple profiles as sites varying in their password requirements. I use the Chrome extension you linked to, as well, which auto-selects the profile based on the URL I'm browsing.
If you can, go with ASP.NET MVC or MonoRail - "regular" ASP.NET will be probably be frustrating given your background. ASP.NET makes it difficult to control the generated html and js, and likes to pretend the web is stateless (viewstate).
I've noticed an increase in heavy server side and client side jobs, oh and can you do some Flash stuff too? Maybe there are some folks that are really strong on the server and know Flash but I haven't met any.
FDC Servers (fdcservers.net) is another good option for high bandwidth sites. 100 meg unmetered line (you can push 15 - 20 TB/mo) - good colo and dedicated server pricing.
1. digg. I still visit digg once in a while but for tech news HN is a better fit. HN has great comments while it seems that a lot of commenters on digg are trying to make puns.
