> Fair use is the same doctrine that allows a school to play a movie for educational purposes without acquiring a license for the public performance of that movie.
This is a pretty bad example, since fair use has been ruled to NOT allow this.
273 karma · joined May 28, 2017
But it’s $24/month, isn’t it? Double that if they invited the kids, in-laws, or neighbors but they don’t use it regularly because those people don’t use Slack for business — which is the whole point of the loss-leader approach: get people used to using slack, get them in the app, and then get them to bring it into larger environments where corporate rates make sense.
This new policy degrades the value of slack significantly for a bunch of long-term, low-volume users. It will cause a few people to move to a paid plan, maybe, and it will certainly cause many to leave slack. The last part will make slack less sticky, less familiar, less generally used, and will save them some amount on storage, maybe? Have you priced out storage recently? I’d bet the cost difference for storage of short text snippets between 90-day rolling and 10k messages is: - Smaller than the variance of MTBF of different batches of disks - Smaller than the variance on overhead in block/page size for their underlying storage system - Smaller than the variance of employee number for their 90th percentile large customers In other words, they’re adding annoyance and losing users for peanuts.
To whomever posted it: thank you for reminding me of an old friend.
When 17 year olds can “own Twitter” and Facebook just budgets 9 figures for data collection compliance fines, are you sure there’s a bright line distinction in the world that’s not “let’s all agree we’re not the terrible/hated/untrustworthy other”? Is the problem that another sovereign country could coerce a company to provide a service that Facebook provides for money?
If you hear a loud banging noise, don’t buy?
The theoretical model here is using people’s fast, stable (-ish) broadband connections to relay the connection. Even then, it’s only for the initial setup steps; once you get to the actual streaming data, nobody in this model wants to ferry those packets around.
It’s likely that those headers don’t all get added all the time, for all the Akamai traffic, but instead are added selectively for key parts of the mapping process.
(Disclosure: I worked for Akamai Way Back When, but left the company many years ago.)
While some of those leaps of logic are plausible, it’s a lot of guessing.
One old example: I have an old friend who used to do sysadmin work in the Windows 2k days, and he would often get gigs by speeding up services by 5-15% within a day. His go-to trick was to log into the headless win2k server and disable the screensaver process, then wait.
It’s definitely a feel argument, and thus highly subjective.
DOS and such were designed around everything on the device being shared, with conflicts resolved at the application layer. Windows was built to maintain some (even ideological) compatibility with that world, while adding some of the benefits of separation and sharing (for example, moving away from the world where every piece of a job could crash/co-opt/exfiltrate the entire device).
Unix (Multics, CTSS, ITSS, etc) was built to enable a world where multiple jobs (not processes; even then lots of jobs were multi-process) and multiple people could share the device. Threads, jails, cgroups, etc were added to move to a world where sharing wasn’t entirely cooperative and trusting. VMs, containers, and hypervisors are on the recent end of that same movement, along with wasm and JS sandboxing.
In the end, it’s a balancing act between performance (speed, power, cost) versus safety, often starting from different points. Exo-, uni-, and library-kernels are similar efforts that haven’t (yet?) caught on, but there’s a pretty clear direction of movement towards the strongest isolation that our (currently quite flawed) hardware can afford.
It’s true that after some number of years, you switch the hardware to a different OS, including a 3rd party supported ChromeOS system or a variety of Linux distributions.
I’m not saying it’s for everyone, but I will say that it’s at least in the same class of consideration as “you could buy an old Thinkpad, and replace at least the hard drive, keyboard, display, and battery to get something similarly usable”.
Eventually I pulled the trigger on a “big” chromebook, the Lenovo Yoga C630, with an i5-U processor and 8Gb of ram, as a trial period device (I had toyed around with a couple sub-$300 chromebooks before), and then the mbp died (pink screen, boot-loops), and I’ve been using the chromebook ever since. It’s pretty good, and steadily improving - at this point, it runs ChromeOS, android apps, and containerized linux simultaneously. My only regret about the thing is that I accidentally got the model without the backlit keyboard.
As a device, it’s a little larger than I would like, but it pays for that with a quite nice screen (I have the FHD version; the 4K display model gives up too much battery life for my taste). I still occasionally look at the Dell XPS13 or the Thinkpad X1 in stores, but it’s hard for me to justify spending 4* what the C630 cost me for either of those devices, especially since the XPS13 seems to have some hardware quality problems and the Thinkpad loses the portability that I would like from the XPS13.
I had hopes for the Pixelbook Go, but they were quickly dashed by the leaks then killed by the launch - it’s expensive and underpowered for a chromebook — costs more for less oomph than the chromebook I already have. I also had hopes for a new mbp with a new (old, really) keyboard, but that just doesn’t seem likely, so I’m not holding my breath.