There are currently three forks of High-Fidelity which I'll be keeping my eye on. I believe two of them have former/current High-Fidelity staff working on them. An interesting blog post about Vircadia, a FOSS-focused fork. [1] The blog also covers the other two forks. [2][3]
"Some" people, arguably. Nothing beats email for an easily-referenceable, structured and local/distributed system of record. Slack requires an always-on connection. Catching up on conversations after a lengthy break is far, far easier using email.
Slack is also disruptive in a way that email isn't. Slack demands attention, which breaks concentration on other tasks. Email can be dealt with at the recipient's leisure.
Slack adds persistence, shared sessions across multiple PCs and phones, search, accounts with logins, messages to offline users, image and file hosting, and works even if you're heavily firewalled.
i.e. the stuff a veteran IRC user cobbles together from an always-on server running irssi+screen, nickserv, saved identify and ghost commands, a chatbot and some personal webspace.
Still, I agree Slack is far more the child of IRC than the child of Wave. IIRC Wave had full rich text, a threading-like mechanic, and you could edit other people's messages, and documents rather than channels.
So I want to be clear that it absolutely does not have feature parity with google wave but Asana encapsulates many of the collaborative features of wave in a way that I really enjoy and it is my next best replacement from the loss of google wave
each task has a thread attached to it... I would describe it as "real-time-ish" one of the things that I like about these threads is that you can unsubscribe from them so that you stop getting notifications.
There sure are a lot of developers only interested in developing for Apple platforms. But wouldn't it be beneficial for Apple to extend the framework outside their ecosystem? I doubt the reason they haven't is to limit expending resources.
The direct comparison one might make is to Microsoft, who recently opened up .NET to have official Linux and macOS compatibility. The result is that enterprise and small businesses can deploy Microsoft technology on their Linux servers, possibly moving towards deploying on Azure. The cloud is Microsoft's big money maker — providing cross-platform tooling is one way to support that business.
Apple makes their money from selling devices, not from offering a cloud infrastructure. Therefore, it makes no sense for Apple to offer their high-quality tooling and frameworks for other operating systems — the aim is to have developers selling their software for Apple platforms, eventually having people pay for services like iCloud storage, Apple Music, Apple TV — and then stay with using Apple's hardware. Maybe a person tries an iPad. Then they get an iPhone. Then they get a Mac.
Apple recognised this about two decades ago when they officially cancelled development on the Windows version of Yellow Box (later to be named Cocoa, the base frameworks for Mac and the ancestor to UIKit, the base frameworks for iOS). It has worked well for them.
Is it right or wrong? That depends on one's perspective about lock-in. However, I don't see a problem with it in the sense that nobody is being duped — unlike Microsoft in the 90s practically forcing Internet Explorer on practically every PC available, Apple doesn't have a market monopoly.
Apple's strategy has remained consistent since the early days of OS X: you don't trap users, you make simply make sure they never want to leave. That's the pitch they make to developers, too.
A few months ago they changed their app so that iOS users no longer had the "only while using" option for location access, and announced plans to stalk users even after their rides had ended.
We could try to build a network to deliver applications, which would stop when you close them. We only need a system to map names to ips and some standards for protocols. We could even run them in a sandbox for security. Would be awesome.
It's not necessary to uninstall the app after each use to prevent tracking - in Settings...Privacy...Location Services, you can disable location on a per-app basis.
(this is admittedly a pain, and Apple enforcing in-use-only option availability is a welcome change)
That's what the "Only While Using" option is all about. In iOS 10 (and earlier), apps could choose to request location tracking "Only While Using" or to request it "Always". Uber switched from the former to the latter. And the article you're commenting on is all about how iOS 11 will add "Only While Using" back as an option for all apps, so you can set it that way even though Uber doesn't want you to.
It is not allowed for apps to refuse to run without location permissions. If you do that the app will be rejected. So no, 'usually' apps do not do that. iOS is not Android.
I don't think we can make that distinction, even now. We might die every time we go to sleep, similar to how you would if you were to be teleported; destroyed at one end and recreated at the other.
I'm not worried in quite the same way as you are. I'm worried that once I've put on the wizard, I'll change, and I won't be who I once was. Maybe I'll lose my humanity. But maybe my humanity isn't doing me any good.
There are a lot of things I said I would never become when I was younger, which I have now become. Maybe this will be the same thing on a larger scale. I might change, a lot, but that's all. I don't see the change as good or bad.
Once I put on the wizard hat, I may miss what it was like without it, but I probably won't want to take it off again, similar to how I miss my childhood, but I'm not sure I actually want to regress back to it.
Edit: Even if you're right, and this is a bad idea, and it will change us for the worse, it still seems to be our best option. Either we pray that AI doesn't recklessly take off without us, possibly destroying us in the process, or we try integrating with it, with the chance that our humanity will be lifted up with it. At least making it so that we have the option is probably a good idea.
Can you prove you're really involved with Neuralink? I just wanted to add some of the stuff you said to Neuralink's Wikipedia page, but there's no real reason to believe anything written here is true.