As an owner of an Advantage 2, I wholeheartedly agree. I was worried that I'd lose my ability to type on a normal keyboard after I became accustomed to the ortholinear layout of the Kinesis (as some posts online suggested), but I'm typing this message on my MacBook Pro's keyboard.
That said, there's nothing more comfortable and pleasant to type on for the whole day than my Kinesis keyboard. Well worth the $350 price tag and the learning curve.
I also have the 2019 MacBook Pro and it's been a dumpster fire. I'm running 3x 4K monitors and it's completely unusable with the dedicated GPU (the 5500M).
I spent months trying everything I could think of: downgrading to Catalina, turning off transparency/shadows, running as few background services as possible, and not using scaling at all (which was the most effective solution). And this was only with 2x 4K monitors; I added a 3rd more recently.
Nothing worked. Thermal throttling and insufficient sustained power were two problems I was able to identify (the 96W adapter is not sufficient for the system's peak power load, so it uses the battery to get over 96W of draw).
Eventually, I broke down and bought an eGPU (Blackmagic eGPU) which solved the problem. For about ~$700, I'm now able to use my machine without a hiccup. Not a great or affordable solution, but it has made my $3,100 machine usable again.
This is true, although it's important to differentiate active and passive adapters.
Ubiquiti sells some devices that are 24V passive PoE. These devices include their UISP products (such as devices like the AirMax). Passive injectors are dangerous because they always supply 24V to the port; this could damage a non-24V PoE device.
There's also the 802.3a* standards family, such as the 802.3at (what Ubiquiti calls PoE+). Each of the standards (e.g. 802.3at, 802.3af, etc.) support different amounts of current, but they're all 48V active adapters. Active PoE is safer because the device "requests" the power it wants; the switch does not always supply 48V power over the port, so devices that don't require PoE won't be receiving power.
Ubiquiti sells a few switches that support both 24V passive PoE and 48V active PoE. You can change this in the switch's web interface, through the port settings. You may also want to consider just using a 24V passive injector, especially if your switch cannot be configured to supply 24V power.
I might be in the minority here, but wired headphones have always been a disaster for me.
I only buy wireless ones now, even though they're fraught with their own issues. It seems like there's always a tradeoff to be made, specifically regarding quality.
My biggest complaint has been the damage that I've always seem to have done to the headphone jacks of devices that I use. I'm not harsh on my devices, but I do tend to put my phone in my pocket and walk around with headphones on. And if it's not the headphone jack that gets destroyed, it's the cable; I went through ~5 different cables/earbuds when I was using the Shure SE215s.
Bluetooth headphones aren't great either. I have not lost a pair of headphones in years, but I've gone no more than 12 months without purchasing a new pair. This gets expensive when I also want my headphones to have active noise cancelling and sound reasonably good (I don't care about audiophile cans, because I wear my headphones primarily when I'm active). And don't even get me started on a pair that has a good (not even great) mic... I'd love to be able to have a phone conversation when walking through midtown Manhattan.
So don’t allow GET with query params. You want the static moniker? It has to be static. No server interaction after load, and no sending any data during load.
How about after load, that tab automatically goes completely offline.
Users can manually do this in Chrome on a tab by tab basis by using developer console and setting Throttling to "Offline"
That sounds more promising. The site might be able to store data and then send it the next time the page is loaded. I think at the end of the day, a malicious dev could probably find a workaround to most implementations. Might just be better to vet out sites and use reputation to state they are truly offline.
I’m very interested in seeing how Dokkument turns out. There are too many documentation tools that:
1) have horrible navigation
2) lack a good editing experience / CMS, especially when working with a lot of images & videos. Markdown is actually distracting in this case because I have to break my workflow to upload these assets to my CDN.
3) are not designed to meet the needs of product marketing - they can’t have analytics added or they can’t be branded to match the rest of the marketing website.
That's an interesting question. You need to differentiate two types of tools.
1. Internal knowledge bases.
2. Customer help centers.
1. are internal only and usually a tool like Confluence, Notion, or Sharepoint is used. Except from Sharepoint their designs are not very customizable. Because that's not the main use case of these tools
2. are customer facing and is usually easier to customize. There are plenty of tools but they mostly follow the initial "intercom" [1] help center design. A few categories with a bunch of articles and folders inside. They are usually not really great tools. On the navigation part there are still a lot of innovation to be done because we still don't know how to orient people who are novice
Thanks for clarifying. That’s exactly the problem that I’m facing. There really needs to be a third option that doesn’t follow the Intercom style of docs that is also suitable for marketing use.
In an ideal world, navigation would be chapter-style, similar to Stripe’s docs.
I’m currently using Docusaurus as my public docs site, but it isn’t ideal because 1) it’s cumbersome to manage a lot of uploaded content and 2) it is not particularly easy to manage the navigation.
I’m thinking of rolling my own within my marketing site (that’s built in Gatsby) and using a suitable CMS but I’d certainly like to avoid the time investment.
This is not a safe method for protecting against this type of cache vulnerability. IP addresses are regularly shared by multiple users, especially when behind NAT (even mobile ISPs are doing carrier grade NAT these days).
