- fewer people participating
- fewer people trying to karma farm
- less "news" on the weekends
- more "fun"/"interesting" on the weekends
4,221 karma · joined September 20, 2012
- fewer people participating
- fewer people trying to karma farm
- less "news" on the weekends
- more "fun"/"interesting" on the weekends
Features are not why people switch
If features were good enough, Google+ would have left Facebook in the dust
If features were good enough, Mastodon would have buried Twitter years ago
Adapting the adage "amateurs talk strategy, professionals talk logistics" - "amateurs talk features, professionals talk problem solving"
"Features" are how bad marketers promote their offerings
Problem solving is how good marketers promote their offerings
You need to solve a problem for me to consider you - a 'feature' has never solved a single problem
Identify problems (real or imagined) that I have that your XYZ solves for me (at all; in a better way than what I am using now; etc), and you have a chance to get me to switch
Try to pitch me on your "features", and I will keep on surfing by
It is not so much "capitalism" that demands domains and IP addresses be assigned/paid-for as it is without some kind of authoritative backing, you have a free-for-all
You wish your website was dotcoma.com? So do I!
So which one of us "actually" gets to have it? With static entries in a local "address book" (like /etc/hosts), we both can - but only we get to know we both have it
>There’s absolutely no reason why they couldn’t be a public good, paid for from the public purse.
This changes nothing from the current system - other than introducing additional bureaucratic inefficiencies: who gets to decide whom can have what domain(s)? How many can any given person/entity get? Why that number and not a different number? What about disputes?
Right now, there is no limit to the number of domains you can register - so long as you can pay for them all.
Converting to a taxpayer-funded government entity is going to put limits on who can register what, when, for how long, etc ... in a way that is (at the very least) no better than the current system, and (most likely) far worse than the current system
Add to this the beauty of capitalism: say I register dotcoma.com an you want it - we can come to a private agreement over how much it is worth to you vs to me, you give me a medium of exchange, and I give you rights to the domain.
Simple
Fast
And does not involve uninformed bureaucrats trying to nanny their way into determining who gets what
Deploying the app is not complicated - just a bunch of cloud instances and object storage.
What is complicated is interlinking regions/zones, understanding current other offerings (things like lambda, serverless offerings, strategies to simplify/reduce egress, etc)
I have a relatively string on-prem background (decades)
Most of my customers are moving off-prem to the cloud (or going for a hybridized approach)
That trend is not going away any time soon - which is part of why I am looking for a [somewhat] simplified approach to tackling major aspects of each of the providers
(I am already pretty adept at a couple small cloud providers from personal projects and a previous employer - it's getting up to speed with offerings past VPS instances and object storage I need now)
Gus Gorman is someone I would have expected would be identifiable from pop culture, based on the other descriptions I gave of him (collecting fractional cents lopped off transactions, being to flashy with buying a sports car, etc) - if not immediately by name, surely by description: Richard Pryor played him in Superman III
>Many systems use encryption in some way or another. However, when we talk about encryption in the context of modern private messaging services, the word typically has a very specific meaning: it refers to the use of default end-to-end encryption to protect users’ message content. When used in an industry-standard way, this feature ensures that every message will be encrypted using encryption keys that are only known to the communicating parties, and not to the service provider.
>From your perspective as a user, an “encrypted messenger” ensures that each time you start a conversation, your messages will only be readable by the folks you intend to speak with. If the operator of a messaging service tries to view the content of your messages, all they’ll see is useless encrypted junk. That same guarantee holds for anyone who might hack into the provider’s servers, and also, for better or for worse, to law enforcement agencies that serve providers with a subpoena.
>Telegram clearly fails to meet this stronger definition for a simple reason: it does not end-to-end encrypt conversations by default. If you want to use end-to-end encryption in Telegram, you must manually activate an optional end-to-end encryption feature called “Secret Chats” for every single private conversation you want to have. The feature is explicitly not turned on for the vast majority of conversations, and is only available for one-on-one conversations, and never for group chats with more than two people in them.
Regardless of whether you are Protestant or not (or religious or not) - understanding the theological philosophy of one of the great thinkers of the Protestant Reformation is a wonderful addition to your own mental maps fo the world at large
Or go with a provider aimed at individual developers and small-to-medium companies (like DO)
It really does not matter which one you pick ... other than realizing that whatever you build will need to be maintained by someone else when you get big enough to grow or sell :)
And where it needs to be located
If I have AWS devs available, probably gonna use AWS
Likewise with GCP or Azure or DO or any of the other platforms out there
They are all (more-or-less) "valid" to use
If I have to learn a platform, I am probably going to pick one of the Big Three (if it is either location independent, or needs to be in the US)
If it needs to be domiciled in a particular coutnry/region, that will change my decision, too
Oh! And it also depends on what I were trying to build
"bootstrap a service" is close to the most open-ended topic you might pick ;)
There are already a LOT of resources on it out there - so knowing what you are trying to accomplish will probably help you find "help" or some "coauthor[s]" :)
Who does center text with rough justification that is not a scammer?
If it is not a scam ... it has no way of knowing the "age" of most (if not all) email accounts out there (unless they have been breached somewhere and they snagged the list a la HaveIBeenPwned)
Propositional statements and key-value pairs are absolutely vital aspects of learning and understanding - but seeing how those ideas, facts, and statements will work themselves out in practical application is absolutely mandatory for proper understanding of the topic
If you never learn how you might use these facts, you are going to have an incredibly difficult time "learning" them
This is the fundamental problem of why "teaching to the test" (or, for that matter, relying too heavily on multiple-choice, true|false, matching, etc type "tests" to evaluate "learning" or "knowledge") is problematic: I can teach pretty much anyone how to pass a multiple-choice test with zero knowledge of the subject material (did it myself years ago when I passed the first-tier amateur radio licensing exam without ever looking at any study guide)
When you "teach to the test" (which is what, fundamentally, exclusive reliance on propositional statements (and drills over them) and key-value pairs are), you create people who may (or may not) end up being good at trivia challenges ... but have no mental framework for connecting all those dots into anything coherent - iow, you create human-based data lakes: it is all sitting there, but no connective lines have been drawn
To get someone to want to learn, you have to show they why it "matters" - you have to get them to develop intrinsic motivation to learn (vs the purely extrinsic "you have to to pass")
To develop that intrinsic motivation, you need to show the 'why' and the 'where' of the 'what'
And to do that you have to understand it yourself