Cheering on Facebook is cheering against your own interests.
Companies need to learn that they play in and extract resources from our sandbox.
If they want to continue to play in our sandbox, they need to play by our rules. They need to act in a socially responsible way. There are even laws about corporate governance pertaining to this.
You don't have to agree with Canada's laws (I don't), but you do need to recognise that they are their laws. Being hostile like this is a good way to make enemies.
This is verifiably incorrect. Members of the Canadian House of Commons swear their allegiance to the monarch. They make no such oath to the People nor the Constitution in Canada.
"I, [name], do swear that I will be faithful and bear true allegiance to Her Majesty Queen Elizabeth the Second, Queen of Canada, Her Heirs and Successors. So help me God."
I’m curious about what’s the best way to go about gathering user feedback and feature requests. You can’t develop a product for people to use behind closed doors, because you run the risk of building the wrong product. Conversely, if it’s too out in the open then anyone and their parents might have suggestions to improve which will drag you away from the core thesis of your product/PMF.
I guess another way to ask my question is - is the aforementioned sequence of steps (please add X, string of +1s, PRs welcome, etc) a bad thing?
> I’m curious about what’s the best way to go about gathering user feedback and feature requests.
IMO, building in the open is still the best way. But to ensure that you don't end up with a mongrel of a thing that tries to do every single thing requested by everybody, It does help to have a rigid set of goals about what we want to build. And the courage to say NO to feature requests that stray too far from the original design goals.
I believe the latest Rich Hickey talk ‘Design in Practice’ might answers your questions in detail - I haven’t seen it recently, but it says something along the lines of don’t build features because they were requested, but instead ask why were said features requested, what’s the reason behind that and solve that problem.
As every Hickey talk, I can only recommend watching the whole thing, it is not clojure-specific at all if that were off putting for you.
Uni for international students in the US is extremely expensive unless you're pursuing a PhD, in which case you're usually fully covered by your PI. Although I don't really see how that's costing the taxpayer much unless that number is somehow accounting for the lost value of what someone who stays in the US after finishing their PhD would contribute to the economy.
Universities take most of the money from the student's funding source such that the student is only left enough to take care of their basic necessities, so it definitely isn't costing much in terms of stipends,
I have a feeling this is temporary to do a server upgrade on the VPS which might run other stuff too. Doesn't make sense to go through all that effort to hide your IP and keep port 80 on pfsense blocked just to open it all up anyway.
> So I added a second A record in CloudFlare for the blog to my home address, and again utilized the CloudFlare Proxy Services.
Is cloudflare detecting downtime via their proxy or something? I don't understand how you can pull the plug and have your VPS route not eventually fall over once cf's cache invalidates. Do browsers try both if one server fails?
Honestly I'm not 100% sure. Full A record failover is a paid feature which I don't pay for, but it seems like adding 2 A records does more than just round robin the DNS
If from a test machine I am loading the site via the VPS and I power it down, as soon as I refresh the page it ends up pointing home with zero downtime
There's massive differences of using this compared to throwing some keys on a server and opening 22. These systems use the cloud provider's proxying and authz/authn to dynamically grant access.
One could have a box with no public IP and no open ports and still use this to connect.
No, through their in-house proxy tools such as Session Manager or Identity Aware Proxy or whatever Azure has.
> With an SSH key?
Not at the edge, and not an SSH key you manage. A dynamically generated one managed by the cloud provider which exists just for that session. So, not really, not like you're thinking.
Pretty hard. There is no centralized book registry.
All you need to publish a book is a valid ISBN10/EAN13. You can buy those online in bulk. And technically you don't need one, but generally if you want to sell it enmasse you want one.
Given its owned by Amazon you'd think they'd limit it to known ASINs but then I guess they can't account for rare or old books that predate the isbn system.
Not long ago, I was in charge of a lending library at church. A very small lending library, like we started with one bookcase and grew to two.
At first, the most important task was sorting the donations, and determining which books were good for our shelves, and which to discard/recycle. So I was studying a lot of publication houses and authors and reputations. And at that time, I was sorting the books more or less by size and shape, or randomly.
So I had no catalog of books; each had a little library-style pocket with a library-style checkout card, and on the honor system, the parishioners would choose a book, remove the card, and keep the book for a few weeks. But we didn't know what was on the shelves in the first place.
So I decided I would find a book cataloging app for Android. You know, something that a small-time librarian could use. Ahahaha! That was a pointless exercise at the Play Store! Perhaps I gave up far too early. I also looked for a barcode scanning app, so that I could just zap each book and immediately know its ISBN and other details. At that point, I started noticing whether a book had a barcode or ISBN, and guess what, a lot of them had neither. More ISBNs than barcodes, that's for sure. What did I expect? These books were donated from parishioners who passed away, and represented 50 years or more of collecting tomes.
Eventually I just started taking photos of the bookshelves after I was done organizing them all. Oh, and there was at least one unknown person whose mission in life was to purposely mess up all the organized books, and put them in weird arrangements. Far more than someone who's innocently browsing the shelves, this was some kind of deliberate messing with my mind. It came to a point where I had to decide whether I would spend volunteer hours re-re-re-arranging and organizing, or just do a 10-minute tidy on it and stop worrying about this living Catholic troll.
Why not give Authors/Publishers control on adding books and flipping the "book is released" switch?
If Amazon just put a little bit of effort, they could make this into a "goodreads premium" thing and earn money to boot.
Imagine selling input codes for ARC reviewers to be able to input reviews before the book is released for the public; publishers would gladly pay for the privilege, so that when the book is actually available, the top reviews are those of ARC reviewers.
There could be other things Amazon could do, this is just something I thought could earn them money and thus align their incentives with readers. They just need to "care"
Outside of a few niche scenarios with large authors, I don’t see the upside. And those authors have to care in the first place to keep Goodreads updated else Goodreads has a new problem of being stale since now it’s relying on author activity.
I don’t think this is as trivial as you suggest. Training users to not take “reviews” too seriously seems like a sensible trade off.
