1,968 karma · joined April 30, 2012
Some feed readers have "scraping" support where they request each article's URL internally and figure out how (or can be configured with CSS selectors) to extract the article's text content and display it in the reader, though it can be pretty hit or miss whether that can work for a given site.
As for formatting, there are a couple possible explanations--the reader could be ignoring or mangling HTML tags in the content when it's displaying it, or the site itself may be generating its RSS feeds with mangled or missing formatting elements. In my experience both possibilities are equally likely.
I can't imagine this working. The plain text section would probably something like "Upgrade your email client to view this message" 90% of the time and be completely pointless.
Maybe it's an unpopular opinion but if I were rebooting email I'd forego HTML entirely and either say it's strictly plain-text, or use some Markdown-like formatting spec that looks fine even when viewed as plain text (email clients could provide WYSIWYG editors for less technically-inclined email authors). The evils of HTML in email (phishing, impersonating companies, and other scams) far outweigh the benefits (none, as far as I'm concerned).
Turns out he actually was from the bank and he did cancel the loan application.
I've got a couple Vizios right now that are basically just glorified monitors because they stay offline, and they work just fine for me.
My main gripe was that I like to listen to music and podcasts while I walk, and the LP2's apps for that are rather lackluster (nearly to the point of unusability for me). It drove me back to my smartphone a few times (a OnePlus something-or-other), which would usually last a few weeks before I'd go back to the LP2 again because the smartphone was too distracting (like I'd pop open a web browser to look up an actor while watching a movie, then getting sucked down a rabbit hole and missing the whole movie before I realized it was happening).
I'm trying a new experiment now--I've got a smartphone again but it's a super tiny one (a Jelly Star which has a 3 inch screen). It's very annoying to actually use for typing or reading because it's so small. It's only been a month or so, but so far I'm finding it's a very nice compromise. I can listen to all my podcasts and music using my normal Android apps, and I can fire up a web browser in a pinch, but it doesn't suck up my attention because it's so uncomfortable to use for any period of time.
The way I set everything up, there's one schema containing just the bare tables and data, and then everything else (stuff that PostGraphile generates and all of our stored procedures with business logic) are in a separate schema. That way the migration process is a shell script that essentially 1. drops the entire non-table schema, 2. runs through all of the SQL files that define the application (there's some custom logic to control dependencies by looking for a `-- PRIORITY N` comment on the first line of the source files), 3. attach all the triggers to the tables (since they live in the schema that was dropped). It means we didn't have to worry about figuring out what all needs to be dropped to make a change because literally everything is dropped and recreated from scratch each time we deploy a new version.
I'm speaking in present tense because this application still exists, we've just (more or less) frozen the code base and are slowly migrating all its functionality piecemeal into a ASP.NET Core WebAPI project.
That being said, I do fully agree that things like Redis, ElasticSearch, RabbitMQ, and Kafka are probably unnecessary in a large number of projects that decide to add them to the stack if those projects are also already using PostgreSQL as a database.
Being familiar with vi keybindings can be useful if you ever find yourself on a minimal system with no other editors available, but the subset of knowledge you need in that situation would be much smaller than if you wanted to use Neovim as your primary development environment. I think Emacs/Vim/Neovim and the like are better suited to users who actually enjoy the process of configuring stuff like LSPs and code completions in a way that's fine-tuned to their personal preferences and works the same across all programming languages.
- Total number of /64 subnets available: 2^64
- Total number of humans in this future: Let's say 16 billion (roughly twice what we're at now)
To get the total number of months before we'd run out of /64 subnets, assuming each human is absorbing one every month, we divide the number of /64 subnets by the number of humans:
2^64 / 16 billion =~ 1,152,921,505
Divide by 12 to get the total number of years:
1,152,921,505 / 12 =~ 96,076,792
So by my math, assuming the human population stayed steady at 16 billion (which seems just as absurd as the initial premise) we'd have about 100 million years to figure out how to start reusing some of those old subnets before we started running into trouble.
As an author, if you notice that your style choices are generating more interest and discussion than the actual content of your writing, it's probably worth considering whether the reasons that led you to those choices are really worth taking away from the messages you're trying to convey. Seeing as how the author of this post chimed in here to call their use of lowercase an "asshole filter," I suppose it's clear where they stand on that question.
I can see a future where we'll have browser extensions that use generative AI to "correct" style and grammar of articles to match the preferences of the reader, at which point stylistic choices may cease to matter as much.
You could also connect them to a PC wirelessly and play any PC VR games that your computer is capable of running. It used to be a little more cumbersome to set up, but Valve recently released a native SteamLink app on the Quest store that vastly simplifies the whole PC VR experience.
I'd venture that this 23andMe situation is one of the scenarios where password expiration could have significantly improved the outcome, but I concede that it was a poor example for me to use.
So while I agree with you that those users are not responsible for the accounts that were actually compromised, they were fully responsible for sharing their data on that service without fully thinking the implications through. 23andMe is not blameless--it's their poor security controls that allowed it to happen in the first place--but I strongly feel people do not take security and privacy as seriously as they should and as a result do share at least some of the blame.
This may be a regional thing, because my kids have to lug heavier loads back and forth to school every day than I ever had to when I was a kid, and that's on top of their Chromebooks and sometimes an instrument for band. They also don't get lockers big enough to store anything substantial so they've got to carry everything all the time. We pretty much go through a new backpack each year for each kid because they get so worn down from having their capacity continuously stretched to the limit.
The note I link above discusses its replacement and how to upgrade.
For a while I wore a solar-powered Casio that self-adjusted every morning using the NIST atomic clock radio signals, and the peace of mind knowing that my watch was always accurate was such a pleasure in comparison. It was kind of cheap build quality and eventually fell apart, but I don't think I'll ever go back to a mechanical watch again after that.
I think multiple monitors is the solution for people who would rather solve the problem by spending their money instead of the effort it takes to configure and become accustomed to switching between virtual desktops. Given that it is a strict biological limitation that the human brain can only focus attention on one thing at a time, I don't believe there is any valid argument for why moving your eyeballs between physical monitors is any better than hitting a key combo to switch between virtual desktops on a single monitor once those key combos have become muscle memory. Additionally, the number of physical monitors you have is limited by how much money you have to burn and how much physical space you have to place them, whereas virtual desktops are theoretically unlimited.