2,202 karma · joined August 2, 2012
MCP Lead Maintainer
Writer at: https://den.dev
Host of The Work Item: https://theworkitem.com
Send me a note: hi@den.dev
In all seriousness, I am a big advocate for hosting your own infrastructure as much as you can, but that requires you to be REALLY into doing it. Otherwise, it's just a completely unnecessary chore.
reg add "HKCR\Applications\photoviewer.dll" /f
reg add "HKCR\Applications\photoviewer.dll\shell" /f
reg add "HKCR\Applications\photoviewer.dll\shell\open" /f /v MuiVerb /t REG_SZ /d "@photoviewer.dll,-3043"
reg add "HKCR\Applications\photoviewer.dll\shell\open\command" /f /ve /t REG_EXPAND_SZ /d "%SystemRoot%\System32\rundll32.exe \"%ProgramFiles%\Windows Photo Viewer\PhotoViewer.dll\", ImageView_Fullscreen %1"
reg add "HKCR\Applications\photoviewer.dll\shell\open\DropTarget" /f /v Clsid /t REG_SZ /d "{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}"
reg add "HKCR\Applications\photoviewer.dll\shell\print" /f
reg add "HKCR\Applications\photoviewer.dll\shell\print\command" /f /ve /t REG_EXPAND_SZ /d "%SystemRoot%\System32\rundll32.exe \"%ProgramFiles%\Windows Photo Viewer\PhotoViewer.dll\", ImageView_Fullscreen %1"
reg add "HKCR\Applications\photoviewer.dll\shell\print\DropTarget" /f /v Clsid /t REG_SZ /d "{FFE2A43C-56B9-4bf5-9A79-CC6D4285608A}"
For HEIC photos, you might still want to use the new viewer.
The buttons are entirely virtual and the onboard controller ensures they are properly positioned, so you don't have to have each button carry it's own screen.
Appreciate the shout-out!
Entirely static site built with Hugo. Blogging for a bit more than a decade now.
Apollo's leverage was "We help keep power users on your platform, and keep them happy." And, as it turns out, while their numbers are not necessarily large, they are also some of the loudest and with most influence (see how many subreddits joined the blackout). What the outcome of this will be is to be seen, but it's a very shortsighted take from Reddit, in my own humble opinion.
1. Got my break in the tech industry thanks to a blog post on some reverse engineering tinkering I've been doing.
2. On multiple occasions, I ended up searching online for a problem only to land on a blog post I wrote years ago, so I use it as my own reference every once in a while.
3. Connected to a network of folks in the companies I've worked at (and continue to work in) thanks to blog posts where I tinker with APIs and all sorts of random stuff ("Oh yeah - I've seen that blog post before.") that I wouldn't run into otherwise.
4. Got way better at writing and expressing my thoughts clearly, especially when it comes to more technical topics, thanks to having a public forcing function.
In light of this, it's easier to outsource the network and data infrastructure to a provider that actually does it day in and day out and put the limited engineering resources to something that is more impactful.
Just reaffirms that quite a few companies do not want to run their own servers unless they absolutely have to.
I stand by the statement that Twitter moving into publishing long-form content puts it on the same pedestal with Medium and defeats the purpose of the platform. Which is OK - strategy evolves, and someone did the math that this is going to be more beneficial.
My other comments reflect my stance on their decision, but I am neither a product manager at Twitter, nor do I have any knowledge of the "whys" so take this with a boulder of salt.
It's a trade-off that folks are willing to make, and for the "average user" (definition can vary depending on service/area) that is a very straightforward choice. I just hope that more folks understand what rights they give up by becoming attached to one platform as their publishing medium.
My guess is that this is an attempt to replace long threads (1/n), but those have their own place and mechanics and I don't see how getting people to write Twitter Notes is in any way a 1:1 replacement or improvement for that.
Time will tell.
> By submitting, posting or displaying Content on or through the Services, you grant us a worldwide, non-exclusive, royalty-free license (with the right to sublicense) to use, copy, reproduce, process, adapt, modify, publish, transmit, display and distribute such Content in any and all media or distribution methods now known or later developed (for clarity, these rights include, for example, curating, transforming, and translating).