Twitter should really allow advertising to your existing following.
I have an account for one of my projects that I use to announce new releases and updates. This happens once every few weeks, so I would pay for an option to stick my tweet at the top of my followers' feeds for, say, a week. If Twitter would then also allow people to unstick a tweet after reading it (or opt out of sticked tweets altogether), I think it'd be a great and welcome feature to have for everyone involved - TWTR gets paid, I get more eyes on my tweet and others won't miss my updates, which is what they followed me for to begin with.
This could really work! I think Twitter is much more about building an public identity than let's say Facebook. If they would allow their user to run minimal budget campaigns this could become much more successful/relevant than the typical Twitter ads.
They know when it's displayed to you. Let's say that Bob follows Sally (and a bunch of other people)
* Sally makes a tweet at 8AM
* Bob doesn't check Twitter until noon
* Bob doesn't scroll down, the tweet at the bottom of the screen is timestamped 11:30AM
In this scenario Twitter never displays Sally's tweet in Bob's timeline. It is thus not an impression. If Bob had scrolled down to see tweets going back to 8AM Twitter would display Sally's tweet in Bob's timeline, this would count as an impression.
If you're asking if they know that you actually read, parsed, comprehended, or contemplated the text of the tweet then no of course not. Likewise somebody clicking on a link doesn't mean they actually read, parsed, comprehended, or contemplated that content.
Of course, and that's how ad impressions are counted. But that doesn't help me as a user, and advertisers pay much less for "impressions" than for an ad that is interacted with in some way. So that's worse for everyone than an ad that you click to dismiss.
It's C++ on top of raw Win32 API with very light use of actual ++ features and no external dependencies except for Windows SDK. About 75KLoC in libraries (UI, RPC, event loop, tasklets, etc) and 90KLoC in the app itself. The IDE font is one and only Dina - https://www.donationcoder.com/Software/Jibz/Dina/.
Ahh yes Dina! I tried it out long ago but have been using Consolas since its release. Just installed Dina and I have to say it looks rather lovely at 8pt on a dark theme! Is that a custom theme you have in VS or something from vsstyles?
The animations in Bvackup are very OS X like. They are beautiful. It has been a very long time since I clicked a button in a Windows app and went "ohh that is sexy!" haha. Also your /wip is very interesting. The level of detail is impressive. I ended up spending about half an hour reading every entry.
Are all the animations completely home baked then?
It's not a theme, just some basic color palette with green for preprocessor, yellow for keywords, cyan for string and numbers and white for the rest. Dark gray for the comments.
Re: animations - yeah, they are all custom, but there's not really much to them. The hardest part was to do flickerless fade-ins and -outs, the code for that just ain't pretty. Window transformations are just DeferWindowPos with the right combination of flags and a bit of painting cooperation from custom controls. Still though... the amount of work required to get these animations working was ungodly compared to $('div').animate({ ... }); :)
Yeah I can imagine. Win32 was never designed for animations like that :) You appear to have done a pretty remarkable job though as they are some of the best I have seen in Windows outside of things such as WPF. Well done!
Do you blog at all? I imagine you have some very interesting things you could talk about in regards to Win32 programming. Understandably there are fewer and fewer pure Win32 developers these days and even fewer who take the time to really make a Win32 application look good.
Purely for personal curiosity I have decided to learn C (and most likely C++ as well) as I have no real experience with native development and it is something that has always bugged me. Would it be incredibly rude of me to maybe shoot you an email for a little chat one to one? I totally understand if you are unable too. Thanks!
It's been too long since I've actually worked with it, but it is how Win8 does file history and wbackup uses it to make its differential backups, of all files, not just log like files.
It's former. It splits files into blocks (defaulting to 32KB, but that's configurable), computes hashes (two separate hashes per block) and stores them in a file in the backup config directory. These are used to detect modified blocks. It also computes a hash of an entire file and stores it in the same hash file. This is used to hedge against false negatives with modified block detection. The original version (from '09) didn't use the full-file hash, so it resorted to re-copying files in full after several incremental updates.
Is the full-file hash actually faster than re-copying the whole file?
Re-calculating a full-file hash will require reading the whole file anyway. Which will take around the same amount of time as re-copying the whole file, since the sequential write speeds of most HDDs and non-entry-level SSDs are similar to their sequential read speeds. The only benefit would seem to be that your SSD might last a bit longer... but how many consumers use SSDs to store their backups?
It's a file-level replicator, it is just not meant for system/image backups, because those need to be aware of MBRs, partition tables and other non-FS elements.
Yes, that's what I feared.
I might start using it at work, in association with CloneZilla, the latter for deployment, and yours for user's data safety.
If you are referring to the "last beta", then it's just what it says on the tin - it's the last of beta releases, meaning that it's unsupported and it's the end of the line, feature-frozen since mid May, no updates. The exact list of differences is over at [1]. The reason the last beta exists is that the beta period was quite long and there were people who got used to using the app for free, so that version is for them (though all beta users got 50% the production version).
From what I've read persistent volume snapshots has been removed from W8 and replaced with File History. You can still use VSS to make temporary snapshots though (and that's what allows backup apps to process locked files).
The filesystem and API support is still there, and System Restore still uses them. vssadmin doesn't offer to let you create shadows, but you can still make them via PowerShell:
