MagerValp

And it does. Copying any app bundle to an indexed disk, like your boot drive, will cause it to get indexed immediately.

There are the occasional bugs though, and there’s also aggressive caching.

A bug kept it from indexing the app when you first installed it. Forcing a re-index of /Applications would have fixed it, likewise duplicating the app and deleting the original.

When you registered the app I assume it modified itself, triggering a re-index.

While that sounds user friendly and genuinely useful, to me it's acceptable collateral damage in order to stop the rampant abuse by ad networks. As a user I'm also not sure it's a huge loss, since at least the browsers I use can auto-fill addresses and credit cards.

Sure, there are modems and serial ports, ranging from 300 to 115200 bps, but since 2002 there are 10 Mb Ethernet cards too. I wrote a TCP/IP stack for it: http://oliverschmidt.github.io/ip65/

NCSA httpd introduced the Common Gateway Interface which allows you to execute any binary, and whatever it puts on stdout is sent as the reply. Back then it was typically a Perl script or a compiled C binary.

https://en.m.wikipedia.org/wiki/Common_Gateway_Interface

They publish detailed data here: https://www.fastmailstatus.com/

And anecdotally it's been rock solid for me and my family, never slow.

It's only the 1Click bookmark feature that doesn't work, no apparent issues with the rest of the extension. Details here:

https://discussions.agilebits.com/discussion/67388/browser-e...

My experience is mainly from 8-bit CPUs, but unless you can afford one IRQ per bit, won't you just be busy waiting at 320 MHz instead? Performance tends to be less of a problem than the fact that you can't do anything else at the same time.

Project Binky is pretty much the opposite of what the GP asks for though, they're clearly experts and it's taken much more than 12 hours :) But Binky is hands down my favorite thing on YouTube, though Clickspring would have to come in second: https://www.youtube.com/channel/UCworsKCR-Sx6R6-BnIjS2MA/vid...

The good ones do! Try Micro64, its CRT simulation is completely configurable and you can set it up to match a high spec CRT: https://www.youtube.com/watch?v=d1qEP2vMe-I

Jeremy Reimer has a great article collecting sales numbers for personal computers: http://jeremyreimer.com/m-item.lsp?i=137

In 1981 the Apple II sold less than both the TRS-80 and the Atari 800. Also remember that the Apple II was almost exclusively sold in the US.

It's supposed to load to 100% (zing!)

Seriously though, works fine in FF here, and shows a beautifully rendered loop of the earth.

An official solution would be great, but in the meantime there was a thread last year with lots of options:

https://news.ycombinator.com/item?id=8706496

Well you'd have to start with an original floppy or cassette, wouldn't you? Some still enjoy cracking on the real hardware, but most make a low level floppy or tape image and work from that.

I've only cracked relatively simple stuff, but working in an emulator is a LOT easier than working on real hardware. In an emulator you can freeze the system and inspect both the computer and the disk drive, set breakpoints, modify memory, and so on, and it's totally undetectable to the protection code.

This is actually not a problem today, see e.g. the ipf image format and hardware such as KryoFlux:

http://info-coach.fr/atari/documents/_mydoc/IPF-Documentatio... http://www.archiveteam.org/index.php?title=Rescuing_Floppy_D...

I also switched from ABP to UBO, and I also feel that it does a better job out of the box and uses fewer resources, but it's a marked downturn in usability. Quickly blocking an element like an annoying gif is a breeze in ABP (with Element Hiding Helper), and also quickly seeing what's being blocked (CMD-Shift-V), or adding a custom rule. I have yet to figure out how to do any of those easily in UBO, and enabling advanced mode deliberately disables all mouseover help.

I'm close to switching back to ABP, but we'll see...

Isn't this what entitlements do? I honestly have no idea how they work - perhaps blog material? :)

It looks good, but the price is pretty baffling. I can run VLC and plex for free on my iOS devices, StreamToMe is $3, Air Video HD is $5. Is Beamer that much better?

Author of AutoDMG here, and since imaging is my day job I was happy to see that the article starts with a solid introduction to deploying OS X. However I'd do a few things differently:

* It's best to build the image using a full installer of the latest version of OS X downloaded from the App Store (currently 10.10.5 14F27). Do not build a 10.10 14A389 image and apply the combo update to it as updates are meant to be installed on live systems and occasionally causes headaches.

* Avoid including extra packages on the image, it'll only make it a pain to maintain and update. Also many packages are badly written and don't install correctly (see https://github.com/MagerValp/AutoDMG/wiki/Packages-Suitable-...).

* Rather than installing packages into the image you can include them but install them on first boot, e.g. with Outset: https://github.com/chilcote/outset

* Even better, it's easy to set up Munki for software management, this way you can keep your machines updated too: https://github.com/munki/munki

* If you build your image with AutoDMG a recovery partition should be included in the image and created automatically when you restore with asr. If for some reason it's missing you can create a package that will create it for you (again using the latest OS X installer): https://github.com/MagerValp/Create-Recovery-Partition-Insta...

Now on to reading the rest of the guide... :)

Edit: reworded

There are a few exceptions but generally you can stay one or two versions behind. While Apple annoyingly don't state how long they support OS releases, they currently ship security patches for 10.8 and 10.9. The last patch for Lion was just before the 10.10 release.

Don't be alarmist, worst case a cleaning tool would have to be run from recovery mode, but nuke and pave is usually the recommended cause of action if you get a infected with a rootkit.

SIP holes will be found, and Apple will patch them just like other security flaws.

I think you have that backwards. You, as the person with physical access, is in full control as SIP can be controlled from recovery mode. Processes running as root are no longer trusted to have full access to the system. This is definitely a step in the right direction.

It is here (Sweden), and I think the two most important factors are:

1. Paternity leave 2. Child care facilities

Paternity leave is important to break the stereotype that mothers are the ones who have to sacrifice their careers to stay at home and care for the family. Widely available child care allow both parents to work as much as they need.

Anecdotal evidence from the senior staff I know here at the University says that male professors don't have stay-at-home wives, and female professors have kids (with no noticeable difference compared to the rest of society).

If you prefer reading there are plenty of articles on this subject, for example this one from April: https://news.ycombinator.com/item?id=9454670

I liked David's video though, great production values and good pacing.

And as another long-time user of Firefox, I'm grateful that you keep adding useful things like Pocket. Any news on when the integration ships in non-US locales? That one had me stumped for a bit where I got Pocket on one box but not the other :)

You need a developer ID with kext signing ability, not a regular developer ID:

https://www.google.com/search?num=30&q=site%3Adeveloper.appl...

That restores some of my faith in humanity, thank you. We'll be looking at the kext today at work, but due to Apple's kext signing requirements I don't know how feasible it is to roll it out.

Thank you. Any particular reason you decided to lead with the exploit and not this patch?

There's writing a nicely worded letter, and sending it in a rose scented envelope. And then there's scribbling a note, tying it to a rock, and throwing it through the window.

Telling the world via a fully working exploit causes a ton of collateral damage, and the author made no effort at all to reduce the impact. Waiting for 10.10.5 and releasing it on a Saturday afternoon makes it seem like the point was to cause as big a mess as possible.

That article is two weeks old. 10.10.5 was released 3 days ago, and the fix is mentioned in the release notes (under dyld): https://support.apple.com/en-us/HT205031