In addition, zero-rated traffic types.
I'd love to see this for small business Internet Access services. Availability of static v4/v6 assignments, etc.
Batman emoji is the one I'd use the most. Surprised it wasn't isn't the original set.
A $10k Apple Watch is going to attract thieves. Unlike a phone, which for some is a fashion accessory while out, but usually stays in the pocket/purse, this thing will be on your wrist continuously. It doesn't need to work to be valuable to someone just wanting to be seen with it. For someone with a stolen Apple Watch, saying it is out of batteries will be enough to explain away questions about why it isn't working.
Has anybody patented delivering boxes on a truck yet? Better jump on that one.
Using the Epic browser, slashdot is exactly as you say. Under chrome, I'm seeing ads from Doubleclick and Tribalfusion.
Guess I'll have to dig deeper to figure out where the ads are coming from. If my box or browser is compromised, I owe you one.
Over the last few years, I have worked with a service provider on what to an outsider would sound very similar. The organization's processes, applications, and information had been distributed throughout the company on an ad hoc and project basis, resulting in an irrational de facto architecture that contributed inefficiency to practically every activity. For any organization, addressing these systemic issues will always be a work in progress. Although my case differs in scale by more than a factor of 100, I think the lessons I've taken may apply for you as well.
1 - Dysfunction is not a product of the technical situation. It is a product of management. Thus, it can only be addressed by management. For you, this means you have the opportunity to lead the organization to the right outcome, and you will have to get management support to get folks to change their processes. It looks like this: a) Identify the outcomes the org is looking for. Not "FAQs on the same server," but "Knowledge Management - Processes and technology to get and KEEP key company information accessible when necessary and secure." b) Obtain management support on the outcome. c) Explain the steps and costs needed - technical and non-technical. Management must ensure that new knowledge lands in the right place and people to go to the right place for the info. d) Implement - the technology and the culture changes e) Evaluate.
2 - What you are doing is not unique to your organization. Practically every firm has this problem in varying degrees. Go scan through the book "Faster Cheaper Better" by Michael Hammer to see an articulation of the issue at a very high level - not specific to knowledge management.
3 - There are frameworks that help guide the architecture process. Have a look at TOGAF. These are model driven, and frankly, they are very hard to consume and live by. Nevertheless, the point of these is roughly the same. When the problem is too large, divide and conquer. Model the organization and subject matter by dividing it into its parts. Prioritize, strategize, etc. Having the model enables you to ensure that solutions at the micro level are in harmony with those at the macro, etc. TM Forum does this for telecoms.
4 - Since the most important part of the job is getting buy in from management and those having to live through the culture change, your soft skills are more important than the tech skills.
All this might look like killing an ant with a sledgehammer. I suggest that you take a little time glance through material on how this is done at large scale and apply whatever seems pertinent.
This thread already has great posts in it. I'm an amateur who has recently done a good bit of research and made some purchases.
Prior to this 2011, I usually kept a small point-and-shoot around for a few years at a time. Each one took some great photos, and plenty of throw aways. That was until I had a chance to use a friend's Nikon D40, an older 6MP DSLR. I discovered with it that I had far more control, especially over focus and depth of field. All of the sudden, I could put the subject into focus quickly, and I found I was getting better results. From this experience, I went on a research binge and ended up making two purchases soon after. I bought a Canon ELPH SD4000 IS, a Point-and-Shoot that works well in low light, for my girlfriend. I got a Nikon D3100, an entry level DSLR. Here is a quick list of what I learned.
1 - The world is full of great cameras. A good photographer can make great work with most or all of them, and the best camera can't make up for a poor photographer.
2 - The DSLR world is as much about lenses as camera bodies. Canon and Nikon seem to be the two that most folks are religious about, and both have their mutually-incompatible lens styles. Every dollar toward one lens style gets you further invested in that family of lenses. It's not a bad thing, but you'll want to school up if you go the DSLR route. Have a sense for how the UIs work, the lens options (including compatibility with cameras), the relative prices, etc.
3 - Despite my Nikon D3100 having 14MP and all around "better specs" in most regards, I have little practical benefit to having my DSLR vs. the one borrowed. I get the joy of having more control with both, and I know I can shoot photos that could be printed to be somewhat larger. Scaling images down, my photos might be slightly more forgiving than those of the D40. In truth, if I were taking the same photos with either, I would have the same keepers.
4 - DSLRs carry a stigma in crowds. Carrying a point-and-shoot, you can take your pictures and put them away. Pulling out a DSLR means everyone around knows they're on camera.
5 - The Canon SD4000 IS does the best of job of no-flash low-light shots of any point and shoot I have seen. It does better than my DSLR with stock lens due to having a lower aperture. If your shots are mainly of people indoors at their homes, in restaurants, at clubs, or in other night settings, pulling out a DSLR will not only inspire poses or turned backs, but will probably require more tuning. I am not endorsing this camera as the best at this, but only that I was satisfied that I matched the camera to the kinds of shots that would be taken. I would have been less happy with a general purpose point and shoot.
6 - I have no experience with the "DSLR-like" cameras in the mid range, except that very good photographers I know downsize to these to have a camera that they can take with them anywhere.
7 - Borrow a camera if you can. I was very happy that I did.
Once you know what you'll use it for and what it is that encourages you, you'll be in a better position to figure out what camera will fit you.
A follow up to some comments on this approach.
On zeroing out your drive or partition:
If you zero out a drive, whatever you use to get bootstrapping started (traditionally MBR), describing the extents of your volumes (partition table), and your filesystems themselves will not write over most of those zeros. So whether you do it to the whole drive (say..
On the use of DD at the drive or volume level:
- You can back up whole drives, but you must restore to something at least the size of the original drive. Plus, you will lose any additional space when you restore to a larger drive. You may be able to add additional volumes with your partition tool or resize what you have, but you begin to erode the value of this approach.
- You can image the volumes/partitions, but you'll have to ensure that the partition table describing the extent of the partition does so the same way, with the same size.
- The most important thing about either approach is that you have a strong understanding of what is and isn't getting imaged when you use the DD tool.
The craziest thing I have done with this method:
(Circa 2003, I think)
I had 3 PATA drives set up as a Linux RAID 5. Two of the drives relied on the same cable and drive controller.. some of you already know what will go wrong here.. The cable or controller failed, and I had a failed RAID 5 volume that would be risky to rebuild. And it had important files.
The three RAIDed drives were
Using a 250G drive, I created 3 partitions
A couple of lessons -
1 - There is no difference between the block device identified as the drive and those identified as partitions on the drive. They are differentiated based on their use by the OS.
2 - Don't be dumb like me. Follow best practices with RAIDs, backups, and protecting your data.
dd is your primary tool.
zero out your drive so that when you compress it, you get a very small image.
dd if=/dev/zero of=[drive]
Install and configure your OS onto [drive]
dd if=/dev/[drive] | gzip -c > zipped_drive_image.bin.gz
gzcat zipped_drive_image.bin.gz | dd of=[drive]
I may be a bit rusty, so the commands may need slight work. I've definitely used this method though, and it has worked well.
The lesson I take from this is that the local retail is doomed unless we figure out how to address the online tax advantage.
Borders is a high profile example of a brick and morter shop that can't compete in an environment where its primary competition has an unnatural advantage. Amazon doesn't pay sales tax. Sure, it had some missteps along the way, like having Amazon run its web sites. But if Borders can't compete, do you think Mom and Pop retailers will? This impacts not or future local retailing environment, but local employment, too. Sure, online stores can be more efficient, but even a local preference for local retail won't compensate for a 5-10% price penalty.
No skis take rocks like rental skis!