> > #1 is doable but would destroy our ability to combat fraud. "Here's how not to get banned next time" is not an email anyone in this space would consider sending.
> Just imagine laws would work that way.
This is how "tipping off" law often works in practice.
As a support agent you often lack full visibility into the treatment or history of the person on the other end of the phone, especially if they're a bad actor. You can't tell them what is or isn't fraudulent behaviour, or what might be construed as such.
But the quote "Here's how not to get banned next time" is rather factitious. It's in fact "we will not even tell you why you got banned".
I don't know what you mean by "tipping off" laws mean, but certainly if you get given a penalty in law (e.g. you get judged in court), you will be told what you have done wrong, and shown proof of it.
But most people also aren't draining their battery every day.
I live in Toronto, own a Kona EV, and am lucky enough to have a garage. I've literally never needed anything more than 120V except when going on >300km car trips. Any daily commute that wouldn't be handled by an overnight charge at 120V probably isn't a commute I'd put up with even with an ICE vehicle.
Or decline in product offering relative to the competition.
In Canada at least Netflix's library seems to have been gutted with a ton of their non-original content moving to Prime, Disney+, etc. And even a bunch of their own formerly-exclusive content is now available for free on services like Tubi.
> If you are worried about safety, ride your e-bike/bike in the middle of the lane.
I'm the sort of person who "takes the lane" when necessary but it doesn't work great in practice: Many drivers will aggressively tailgate and I've even been "bonked" by one who thought it was a totally normal and acceptable thing to do.
I even live in an area where cyclists are recommended (by the police) to ride ~3 feet from the curb and we require drivers (by law) to give cyclists ~3 feet of clearance. If cyclists were to follow those rules they'd be taking the full lane almost everywhere. But likely due to a combination of it not being common in practice and motorists being generally impatient it ends up being a dangerous set of guidelines to follow.
In the greater context of this and the NYT article: The answer is probably better bike infrastructure.
Part of the complexity of moderating on Reddit vs. moderating on Facebook is Reddit's open-by-default nature and limited control provided to moderators.
For example: Optionally requiring a questionnaire before being able to post to a Facebook group significantly cuts down on spam. Reddit doesn't really have an equivalent. If a Reddit mod wants to implement similar? They could use the API to write something that blackholes new members' comments until they respond to an automated message. Not a great user experience and what happens if Reddit pricing changes now make that integration prohibitively expensive?
Some mods certainly power-trip but ultimately the role isn't a glamorous one: You're a volunteer customer success agent. Most of the work isn't hard or controversial, but at the scale of Reddit there's a _lot_ of it. The hardest part of recruiting new moderators is finding people who'll remain even minimally engaged. Replacing them certainly isn't impossible but the process of replacing proven-engaged moderators with newcomers that need to be vetted can be a ton of work in itself.
There are a few bank-to-bank mechanisms (ACH, wire transfers) but they're slow (often multiple business days) and often have fees associated with them ($20+ for wires).
The lack of good transfer mechanisms is what has led to a proliferation of alternatives (e.g. Venmo, Cash App). Zelle has emerged as a bank-approved mechanism for "instant" funds transfer.
It might be worth giving the Apple Store or online support another shot.
I was in basically the exact same position a month ago (pros bought launch week, very out of warranty, known crackling issue) and they replaced the ear pieces (but not the case) without question or hesitation.
I feel like my experiences are in sharp contrast to many others here.
I love Elixir the language but find myself still having to throughly review new libraries to avoid footguns. In particular with "connectors" -- DB drivers, API clients, basic protocol implementations, etc. And resolving those issues normally means fixing them ourselves, often with a significant refactor to someone else's library. And in turn that's meant some of us having to become fairly proficient with Erlang.
So while I'm optimistic about the future of Elixir there are still some pain points that I think relate directly to the immaturity of the community.
Are many of these issues related more to older Erlang libraries? Most all of the Elixir libraries that aren’t a WIP have been pretty good for me. Just curious which sort of protocols too. Not always, but I do find older Erlang libraries often lack unit testing and consistent doc tooling, likely due to lack of tooling in earlier days.
Probably 50/50 old (but popular) Erlang libraries and newer Elixir libraries.
For protocols, we have a not-uncommon use case for which there’s no mature HTTP client. Mint might be an option but it’s new enough that I haven’t evaluated yet.
A&W was our go-to fast food hamburger place even before beyond meat burgers as their veggie deluxe burger was already fairly good, though I'd still order a meat burger.
Now we both get the beyond meat burger and I honestly can't tell the difference between them and their standard meat patties. Granted, that's a lower bar than fresh ground beef coming off a barbecue, but still impressive.
One service-to-service case where I've found GraphQL extremely useful is report generation.
For example, in one case we had around a dozen services with fairly typical REST APIs, a few of which we wanted to pull large inter-related sets of information from. Using GraphQL allowed us to:
- Have a single large-but-human-readable query to retrieve all report data.
- Analyze deep nesting up front to determine opportunities for caching and eager loading.
- Abstract details regarding what data was coming from what service, plus handle any quirks (e.g. inconsistent auth strategies) at the GraphQL layer.
Without having to make many modifications to the underlying services. We also saw a two-order-of-magnitude performance improvement that would otherwise have required building out a lot of service-specific awareness into our reporting service.
Granted reporting is a unique case, but the simplified gateway layer and potential for query analysis are also major advantages as the number of API consumers grows.
> Just imagine laws would work that way.
This is how "tipping off" law often works in practice.
As a support agent you often lack full visibility into the treatment or history of the person on the other end of the phone, especially if they're a bad actor. You can't tell them what is or isn't fraudulent behaviour, or what might be construed as such.