mihaip

The CPU emulator tries to be pretty accurate about timing, but the I/O is not throttled, so that might be unrealistically fast (depending on your Internet connection).

The Developer CD for the 3.3 release is in the CD-ROM drawer, you should be able to mount it and install IB and PB.

You can reduce the mouse speed a bit using Preferences.app.

The fundamental issue is that there’s two acceleration curves being applied (the guest OS’s and NeXTStep’s). I experimented with the unadjustedMovement option (https://developer.mozilla.org/en-US/docs/Web/API/Element/req...) but it didn’t seem to help (and if anything, made things feel even harder to control)

Author of the post/creator of the site here. To save everyone the click, NeXTStep 3.3 is probably the best release to try out: https://infinitemac.org/1994/NeXTSTEP%203.3 (it was the last release that ran well on the original NeXT hardware, OPENSTEP 4.0 and later were mostly focused on Intel support).

If you'd like to play the NeXT version of DOOM and explore a few other apps, they're in the "Infinite HD" drive (you can get to different drives by clicking on the computer icon in the Workspace file viewer).

Also possible on iOS starting in 1.38.1: https://tailscale.com/changelog/#2023-03-14-client

https://www.pcjs.org/ is a similar project on the PC side.

The Internet Archive also has some collections: https://archive.org/details/classicpcgames and https://archive.org/details/softwarelibrary_msdos_games

One change that went into 1.36 is that you can no longer use an exit node while advertising one (https://github.com/tailscale/tailscale/issues/3569). The Mac UI was not updated for that in time, but the next release the menu items should be disabled correctly.

Can you sent a message to support@tailscale.com about this and include a bug report ID (option click on the Tailscale menu icon and choose Debug -> Bug Report…)?

The main binary also contains Tailscale’s GUI (onboarding, auth, menu, notifications, etc) so it does a little more than that.

What would you recommend? dlopen is only used when running in CLI mode (which is not super performance sensitive), but not making it slower than it needs to be would be good too.

upx is not used in the macOS build (we only mention it as a possibility in https://tailscale.com/kb/1207/small-tailscale/, which is for embedded systems), so I have no done any benchmarking with it.

There is a way to build an even smaller version of Tailscale for embedded systems, though there are some trade offs with regards to ease of use and security. https://tailscale.com/kb/1207/small-tailscale/ has more details.

(I’m the author of the post)

The solution we ended up with was partially a matter of the minimum change to fix the issue, and partly because we have a lot of platforms to cover with a small team, so the fewer platform-specific concepts we have (frameworks in this case), the easier it is to maintain.

macintosh.js (https://github.com/felixrieseberg/macintosh.js/) is an Electron packaged version of an earlier iteration of the BasiliskII Emscripten port.

I'm the creator of the site, thanks for the submission.

This is an in-progress port of the SheepShaver emulator to WebAssembly/Emscripten, https://github.com/mihaip/infinite-mac/issues/34 is tracking the remaining work.

If you're interested in running older Mac software in the browser, the BasiliskII-based sites at https://system7.app/ and https://macos8.app/ may be better bets. They will boot faster and have fewer compatibility issues (especially System 7).

The main thing that Mac OS 9/SheepShaver brings is PowerPC support. There is also a variant of System 7 for PowerPC with more esoteric mid-90s Apple projects like OpenDoc and QuickDraw GX installed available at https://system7.app/?domain=system7-ppc.app.

No native client is running. The browser makes a WebSocket connection to our relay server, and we run the WireGuard tunnel over that.

Tailscale SSH's check mode (https://tailscale.com/kb/1193/tailscale-ssh/#configure-tails...) is meant to address the issue of "rogue process starts an SSH connection". For truly sensitive applications, you can set the check period to be "1s" to always require it.

This seems to work OK for me. Any chance a modifier is stuck down (try pressing command, option and shift to reset their state). If this still happens, can you file a bug at https://github.com/mihaip/infinite-mac/issues/new?

I haven't tried this myself, but you should be able to download and install it from https://macintoshgarden.org/apps/aldus-pagemaker-50 (drag the .sit on the emulator, and it'll be copied to the "Downloads" folder). You can then use StuffIt Expander to unstuff the .sit and Disk Copy to mount the install images (both are in the "Utilities" folder)

Lunatic Fringe was part of After Dark, which is in the Control Panels & Extensions folder. If you drag that to the "Control Panels" folder in the System Folder and restart, it'll be enabled, and you can choose it.

https://oldweb.today/ gives you that experience, using some of the same building blocks.

Creator of the site here. There's a blog post with the technical details if you're curious about how it works and whose work it builds on: https://blog.persistent.info/2022/03/blog-post.html

There are also a couple of variants that boot either System 7.5.3 or KanjiTalk 7.5.3 (the Japanese version of MacOS): https://system7.app/ and https://kanjitalk7.app/

This particular issue has been reported as https://github.com/mihaip/infinite-mac/issues/20

Usually nothing to worry about, see https://github.com/mihaip/readerisdead/commit/19d3159c985b6e...

I wrote most of Reader's JSON API in 2006-2007 :)

The tool uses the "high-fidelity" Atom output mode for getting at item bodies. That preserves namespaced XML elements and other extra data from the feed. It uses JSON for everything else, and will fall back to regular Atom output if the high fidelity mode is not well-formed (it was added in late 2010, as things were winding down, and thus never got a lot of testing).

The tool caches the API responses (in the _raw_data directory), so if you're re-running it, most of the initial requests will be served from the cache.

If the XML parse errors are listing any item IDs, feel free to email them to me (mihai at persistent dot info) and I'll see if there's any workaround from my side.

Edit: If it's "XML parse error when fetching items, retrying with high-fidelity turned off" messages that you're seeing, then those are harmless (assuming no follow-up exceptions). The retry must have succeeded.

I tried that too (https://github.com/mihaip/web-experiments/blob/master/tempor...). It still flickers, I'm guessing because the frame delay interval is specified as an integer, and both 16 and 17ms don't quite line up with 60Hz (or whatever the screen's refresh rate is).

I tried this with a canvas (putImageData with alternatively the positive and negative frame) and it wasn't any faster on desktop Chrome (and slower on iOS devices).

As background, I (the author of the post) was a founding engineer on the Reader team and the frontend tech lead from 2006 to 2010.

http://crbug.com/45510, http://crrev.com/50386, http://crrev.com/51486, http://crrev.com/51594 and http://crrev.com/54934 seem to be appropriate links.