Showing posts with label unfair competition. Show all posts
Showing posts with label unfair competition. Show all posts

Monday, February 12, 2024

Hertz/Thrifty takes reservations for cars it doesn't have, stranding customers; worse, that's the business model

I've been locked in pre-litigation combat with Hertz Corp. for almost a year, and I'm tapping out.

The problem is simple: The Thrifty Car Rental (Thrifty is a Hertz company) at Memphis Airport (MEM) has been renting cars that it doesn't have. Customers get stranded for hours, until a car comes in, rolling the problem forward. And Hertz is OK with it.

Frustrated Thrifty customers wait hours for cars in Memphis (Mar. 2023).
There's not even seating.
RJ Peltz-Steele CC BY-NC-SA 4.0

Here's a rough timeline.

March 2023: I show up for a car rental in Memphis with a time-sensitive work schedule. They're "out of cars." Lots of people are milling about in the same predicament.  Hours later, I get a car, not before my work plans are screwed up. A check of online reviews reveals that this is business as usual for Thrifty MEM.

Later March 2023: I complain to Thrifty and the Tennessee AG and ask for just one day's refund and that the deceptive practice be abated.

May-June 2023: Hertz Executive Customer Service reaches out to offer $50 off a future rental and pledges that what I experienced is not Hertz/Thrifty's normal mode of business. In exchange for the coupon and assurance, I drop the matter with the Tennessee AG.

October 2023: I discover that the $50-off coupon is a sham.  The coupon can only be redeemed at the rental counter.  Premium for paying at the rental counter: $50.  I ask the Tennessee AG to reopen the matter. 

Also October 2023: I investigate online reviews of Thrifty MEM and discover that they still are renting cars they don't have, leaving customers stranded for hours or longer. I report my finding to the Tennessee AG. The Tennessee AG suggests I also report the matter to Hertz's home jurisdiction, Florida. So I forward the report to the Florida AG.

November 2023: In response to my reopening of the settlement with the Tennessee AG, Hertz says take a hike. The Tennessee AG closes the matter, because, you know, what can you do.

December 2023: I send Hertz a demand letter, alerting the company that sending a sham coupon to a Rhode Island resident and knowingly doubling down on the sham renders the company liable for treble statutory damages of $1,500 under R.I. consumer protection law.

January 2024: Hertz gives me 1,900 "Gold Plus Rewards" points for one day's car rental, in place of the $50 coupon.  I find out the points are just as useless when I need a rental from IAD to BWI; points can't be used on one-way rentals.  Meanwhile, Hertz replies angrily to my report to the Florida AG, accusing me of seeking unjust enrichment by complaining in multiple states. Oh, and Hertz tells me again to go take a hike.

That brings us to today.


Feb. 12, 2024

Hertz Corp. d/b/a Thrifty Rental Car
Attn.: General Counsel
8501 Williams Rd.
Estero, Fla. 33928

Open Letter

Dear sir or madam:

I write in regard to the matter originating in a car rental reservation with Thrifty at the Memphis International Airport on March 28, 2023; your subsequent proffer of a sham coupon for a subsequent Thrifty rental; my demand of Dec. 17, 2023, for compensation accordingly under Rhode Island consumer protection law; and your subsequent award of 1,900 “Gold Plus Rewards” points.

I accept your award of the points in abeyance of my demand.  I have grave doubts that the points are of any use to me.  I already have discovered that I could not use them for a one-way rental from IAD to BWI; they cannot be redeemed on one-way rentals.  And I don’t foresee a need in the future for a one-day car rental anywhere, certainly not before the points expire.  Nevertheless, I choose to see the award as a gesture of good faith.

In return, I ask just one more thing of you:  Hear me out on the following points.

(1) I never wanted from you money, coupons, or points.  I demanded the sum of only one day’s rental cost as nominal and symbolic. What I really wanted was simply that you stop your Memphis MEM Thrifty provider from accepting car reservations for cars they do not have, leaving customers stranded.  Ms. Walsh of Hertz Executive Customer Service wrote that that was not the business practice of Hertz and Thrifty (nor, one presumes, Dollar). That assurance was false. My investigation of online reviews revealed that the deceptive practice continued unabated at MEM. I subsequently rented from another company at MEM and saw the usual crowd of distressed travelers camped out at the Thrifty counter. Shame on you.

(2) A “$50 off”-at-the-counter coupon when you charge $50 more for transactions at the counter is a sham, plain and simple.  I reiterate, I didn’t want your coupon.  I would’ve dropped the matter if you simply abated the deceptive practice.  I decided to redeem the coupon only when it became clear that you were determined to continue to allow deception in your business at MEM.  Even to buy me off, you could not even make an honest offer. Shame on you.

(3) I informed the Tennessee and Florida AGs of the ongoing deceptive business practice at MEM.  Authorities should be informed, even if, as usual, they do nothing.  I forwarded the notice to the Florida AG only because the Tennessee AG bid me do so.  I did not ask for anything in Florida; I did not want dispute resolution in Florida.  The Florida AG, whether for incompetence or willful indifference, entered the notice into a private-dispute resolution system. Ms. Walsh responded in Florida with something like outrage that I had dared to complain about you in another jurisdiction. Let’s be clear: Your MEM provider was engaged in a deceptive business practice.  I notified civil enforcement authorities in that jurisdiction.  They urged me to notify civil enforcement authorities in Hertz’s home jurisdiction. So I did. I asked for nothing from or in Florida. Don’t accuse me of some kind of profiteering off of your poor choices.

You know as well as I do that you can get away with deception at MEM, and anywhere else you want to, and with your profound commitment to stick your head in the sand about it only because antitrust and consumer protection enforcement in your industry is a joke.  I wish I could say I’ll never rent again from Hertz companies. But of course I will. I won’t have a choice.

I understand how you get away with deception and subterfuge, but what I cannot understand is why.  It would be so easy simply to run an honest business.  Don’t accept reservations for cars you don’t have.  Don’t tell customers you’re doing one thing and do another.  If you give someone $50 off, give someone $50 off.  I’m sure Hertz is big and successful enough to stay in business without relying on deception.

Is it really so hard just to be honest?

Sincerely,

/s/ Rick J. Peltz-Steele

Cc: [Ms. Walsh]; [Tenn. AG]; [R.I. AG]; [Fla. AG]

Saturday, September 3, 2022

FTC finally notices abuse of customers, shady business practices by car rental industry

In an omnibus resolution late last week, the Federal Trade Commission (FTC) green-lighted investigation of the car rental industry.

Earlier this year, I wrote about the "new lows" of our car rental oligopoly in the United States, including my own experiences with the misleading Hertz "loyalty" program and the manipulation of pickup and drop-off times to draw overage fees.

The resolution broadly compels investigation "[t]o determine whether any persons, partnerships, corporations, or others have engaged or are engaging in deceptive or unfair acts or practices in or affecting commerce in the advertising, marketing, promotion, sale, tracking, or distribution of rental cars."

For context, Frankfurt Kurnit's Jeff Greenbaum wrote in Advertising Law Updates that commissioners ordered similar investigations in July 2021 into "areas such as COVID-19, healthcare, and technology platforms," and in September 2021 into services targeting veterans and children, "algorithmic and biometric bias, deceptive and manipulative conduct online, repair restrictions, and abuse of intellectual property."

The FTC didn't detail the buzz in its bonnet, but they likely heard lawmakers in the spring frowning on Hertz's misreporting of stolen cars. Senator Richard Blumenthal (D-Conn.) wrote Hertz a nasty-gram in March. Forty-seven customers filed suit for false arrest in July, CNN reported (via ABC 7 L.A.), and they're not the only ones.

I documented my rental return this summer in Thunder Bay, Ontario.
(RJ Peltz-Steele CC BY-NC-SA 4.0)

I've started taking the advice of The Points Guy's Summer Hull to take pictures and videos of my rental cars when I pick them up and when I return them. One Mile at a Time advises the same

But I'm doubting the utility of it. I'm not sure you can see scratches or dents in the images, especially in dark garages. And, as Hull herself reported, she was called out for alleged damage to the roof, which she had not climbed up to photograph. I wonder whether I should crawl under the car to photograph the undercarriage.

Lately rental companies have presented me with an up-sell option for tire and window insurance, threatening that they're not covered even if a buy the CDW. And don't get me started on involuntary "upgrades" to fuel-inefficient trucks. Even the sedan pictured here, which I rented this summer in Thunder Bay, Ontario, was what I got when I reserved an SUV to tackle unpaved roads.

Meanwhile, my budding occupation as car portraitist is eating into my travel time and my hard drive space.

It seems to me that when customers start having systematically to video-record their interactions with industry to protect themselves against fraud, the problem might be with the industry and not with the customer.

Oh, FTC ... 🤙

Saturday, July 9, 2022

Tort-contract distinction cannot block damage multiplier, Mass. high court holds in lease dispute

Photo by Yonkers Honda CC BY-SA 2.0 via Flickr
A landlord may not rely on a limitation-of-liability provision in a commercial lease to evade a damage multiplier under Massachusetts consumer protection law, the Supreme Judicial Court ruled in January, regardless of whether the case is characterized as tort or contract.

The dispute arose between plaintiff-tenant Majestic Honda and its LLC landlord, owned by Alfredo Dos Anjos. Majestic accused the defendant of bad-faith lease termination, and the trial court agreed.

Massachusetts General Laws chapter 93A, under which Majestic brought its case, is a famously potent statutory remedy. Ostensibly its section 11 is a consumer protection law like any of the unfair trade practices prohibitions found throughout the states. But the statute has been read broadly in Massachusetts to operate at or beyond the margins of what lawyers usually regard as "consumer protection."

Moreover, section 11 authorizes double and treble damage awards upon "willful or knowing" misconduct. Massachusetts does not recognize punitive damages at common law, only by statute. Chapter 93A also has a four-year statute of limitations, sometimes an advantage to plaintiffs over the usual Massachusetts limitations period of three years for most tort actions.

Thus, as a result of permissive construction and powerful incentives for plaintiffs, chapter 93A is invoked frequently in what would be merely common law tort cases in other states, even to the exclusion of the common law claim in Massachusetts. Chapter 93A also is used in public enforcement, as in the Attorney General's present litigation to hold Big Oil accountable for climate change.

Tort and contract claims can be subsumed into the same 93A framework, blurring the classical distinction. The distinction is especially weak in product liability cases, in which Massachusetts plaintiffs almost always rely on 93A, in part because the commonwealth has recognized strict product liability as an extension of quasi-contractual warranty rather than as an evolution of common law negligence.

I am not a Massachusetts lawyer, and I am careful to disclaim to my 1L torts students that I am not well versed in 93A practice. It is its own field and cannot be folded into tort fundamentals. But, I admonish, they should endeavor to learn more if they intend to practice tort litigation in Massachusetts. My supremely talented colleague Professor Jim Freely once regularly taught a 93A course, but I don't think it's been offered since he was drafted (no pun intended) into the legal skills program.

Insofar as section 93A's damage multiplier is punitive in nature, it should not be disclaimable by a tort defendant, else the legislature's intended deterrent effect would be rendered moot. Upon this logic, the Massachusetts Appeals Court looked in past cases to discern whether the plaintiff's claim analogized more closely to tort or contract, to determine whether a limitation-of-liability provision should be allowed to nullify extraordinary statutory damages.

In fairness to the Appeals Court, the Supreme Judicial Court did roughly the same thing in 2018 when it applied a statute of repose for tort claims arising from real property to a 93A action, even though 93A itself has no repose period; three justices dissented from that ruling.

Here, the analogical approach is wrong, the Supreme Judicial Court decided unanimously. The court wrote, per Justice Scott Kafker, "Because G. L. c. 93A establishes causes of action that blur the distinction between tort and contract claims, incorporating elements of both, we do not adopt this formulation." The court further explained,

Our cases have also pointed out that a c. 93A claim is difficult to pigeonhole into discrete tort or contract categories, as c. 93A violations tend to involve elements of both tort and breach of contract, blurring the lines between the two. As we explained in [prior cases], "[t]he relief available under c. 93A is 'sui generis,'" being "neither wholly tortious nor wholly contractual in nature." Hence, a "cause of action under c. 93A is 'not dependent on traditional tort or contract law concepts for its definition.'"

After all, the court reasoned, the legislative intention to deter willful or knowing misconduct is not a function of whether the wrong is a tort or a breach of contract.

At a theoretical level, the vast gray area of 93A in Massachusetts law might have broader implications for the classical distinction between tort and contract, namely, whether the distinction will or should persist at all in contemporary common law. Massachusetts 93A practice might prove instructive as courts in many common law jurisdictions, such as Canada, reconsider the vitality of the so-called "economic loss rule," a historic marker of the tort-contract distinction that forbade tort actions in the absence of physical injury or damage.

The case is H1 Lincoln, Inc. v. South Washington Street, LLC, No. SJC-13088 (Mass. Jan. 24, 2022).

Wednesday, May 31, 2017

Anti-SLAPP gone wild: Massachusetts tightens the reins



The anti-SLAPP cases kept coming from the Massachusetts appeals courts in May.  I posted previously on anti-SLAPP in the Massachusetts Supreme Judicial Court in February.  This posting describes three recent holdings, the middle of which substantially revised—and tightened—the anti-SLAPP qualification analysis.  The next two paragraphs recap some background on anti-SLAPP; skip right down to the cases if you like.  The Massachusetts anti-SLAPP statute is Mass. Gen. L. ch. 231, § 59H.

For a quick recap, “anti-SLAPP” refers to state statutes designed to forestall tort claims in “strategic lawsuits against public participation” (SLAPPs).  The prototypical SLAPP might be a land developer’s suit against environmental protestors for interference with the developer’s prospective economic relations.  The protestors are motivated by First Amendment right to speak and petition and are not acting wrongfully.  So, the logic goes, they should not be tied up in pricey and complex litigation having to assert the First Amendment as an affirmative defense.  Rather, they are entitled to a speedy dismissal.  In various forms and fashion across the states, anti-SLAPP statutes allow expedited process before the trial courts to dispense summarily with cases that ultimately would or should come out in defendants’ favor.

Furthermore for quick recap, I despise anti-SLAPP statutes.  They are yet another crutch for defense lawyers—complementing a broad array of defense privileges in common law and constitutional law—to cloak the perpetrators of defamation, privacy invasion, interference, and other torts in the false light (if you will) of constitutional holy writ.  Through unduly expedited process, anti-SLAPP deprives plaintiffs out of the gate of a fair chance to discover the damning evidence of defendants’ wrongful conduct—evidence often required by the aforementioned broad array of defenses, thus compounding the already ratcheted-up hurdles a plaintiff with meritorious cause must clear.

At ABA meetings, I have heard the defense lawyers of transnational mass media conglomerates speak of anti-SLAPP bills in the same tender timbre one employs to share photos of a newborn.  They are especially fond of anti-SLAPP laws that award attorneys’ fees to the prevailing defendant; imagine that Goliath bill arriving in David’s mailbox.  Such cooing should be evidence enough that the playing field has been unleveled.  And I was a defense lawyer, so I know of whom I speak.

That said, I would be foolish to assert that anti-SLAPP motions don’t often reach just results.  An unlevel playing field does not mean that the winning team is not the better.  I contend instead that anti-SLAPP gives a trial judge too much power to ballpark “right” and “wrong” in the absence of the fair evidentiary confrontation that our adversarial system requires.  These cases illustrate how the Massachusetts appellate courts are struggling to implement the state anti-SLAPP law fairly.

(1) The Case of the Ex-Spouse Who Won’t Let It Go

After what must have been an ugly divorce in the 1990s, Ms. St. Germain was left with a permanent protective order of no contact against her former husband, Mr. O’Gara.  In 2014, after receiving contact via post, St. Germain complained to police that O’Gara had violated the protective order.  Police arrested, charged, and then dismissed charges against O’Gara, who in turn sued St. Germain on various civil theories—breach of contract, abuse of process, malicious prosecution, tortious interference, and intentional infliction of emotional distress—for the police report that had precipitated his arrest.

Holding O’Gara’s civil suit “based entirely on [St. Germain’s] petitioning activity,” the court dismissed the civil suit upon St. Germain’s anti-SLAPP special motion, reversing the superior court.  The court reiterated that petitioning activity under the Massachusetts statute is to be construed broadly, “‘similar in purpose to the protections afforded public officials by the doctrine of governmental immunity’” (quoting precedent).  “Furthermore, § 59H covers petitioning activity regardless of whether it concerns a public or purely private matter.”

The statute first burdened defendant St. Germain, as special movant, with proving by preponderance that O’Gara’s lawsuit was based solely on her police report as petitioning activity, without other substantial basis.  Second, under the burden-shifting procedure of the statute, O’Gara would be compelled to prove by preponderance that St. Germain’s petition “‘(1) … was devoid of any reasonable factual support or any arguable basis in law and (2) … caused actual injury.’”

The trial judge had erred by skipping the first step of the inquiry and justifying discovery upon a “credible claim of injury caused by [St. Germain].”  Rather, first, St. Germain was correct in asserting that O’Gara’s suit concerned her police report solely as petitioning.  O’Gara had asserted that St. Germain was motivated by hostility, besides petitioning.  But the court concluded that whether or not she bore such motive was immaterial to the purely petitioning nature of the report.  Second, St. Germain was reasonable in believing her police report legally founded, despite the later dismissal of charges.  I.e., the police report was not a sham.

The case is O’Gara v. St. Germain, No. 15-P-1711 (Mass. App. Ct. May 11, 2017) (Justia).


Four incidents of alleged abuse or neglect of patients in a unit of the Steward Carney Hospital in Boston resulted in a mass dismissal of unit staff, including nurses.  Discussing the employment shake-up publicly in email to hospital staff and in statements to The Boston Globe, with a state investigation still underway, hospital administrators were vague on particulars.  The state later blamed three incidents on only one mental health counselor, and the fourth incident on staff, the latter conclusion the subject of ongoing legal contest.  Plaintiff nurses sued the hospital for defamation, and the hospital responded with an anti-SLAPP special motion. 

The Supreme Judicial Court, per Justice Barbara Lenk on May 23, reached a mixed result and remanded, furthermore finding occasion to tighten the requirements for an anti-SLAPP motion to succeed. 

Again illustrating the broad construction of petitioning activity, on the first step of the anti-SLAPP test, the hospital successfully asserted that the nurses’ lawsuit concerned statements to the press solely as protected petitioning, because the statements were “‘made to influence, inform, or at the very least, reach governmental bodies—either directly or indirectly’” (quoting precedent).  “The key requirement of this definition of petitioning is the establishment of a plausible nexus between the statement and the governmental proceeding.”  The Court held that statements to the Globe passed muster as indirectly aimed at state investigators  However, email to hospital staff, intended only for internal circulation, did not pass the test.

Here the Court steered off the road.  Initially the Court was flummoxed: what to do with a split outcome between allegedly defamatory statements?  Recall that the defendant must show that plaintiff’s suit concerned “solely” defendant’s petitioning activity.  What happens when some statements are petitioning and some are not?  Perhaps the anti-SLAPP motion must fail, because the defendants’ activity was not, then, purely petitioning.  Or perhaps the petitioning activity alone, here the Globe statements, advance to the second step of the test, burden shifting for the plaintiff to prove sham.  If plaintiff cannot prove sham petitioning, defamation might be dismissed in part.  The design of the complaint cannot be dispositive, for plaintiffs could evade anti-SLAPP by parsing counts.

That issue, however, proved to be only the crest of a hill concealing the drop off of a cliff.  For then the Court plunged into angst over the very enterprise of the anti-SLAPP analysis.  If a defendant cannot prove that the lawsuit is about solely petitioning activity, can the lawsuit not be a SLAPP?  Inversely, if a defendant proves that the lawsuit is about solely petitioning activity, and the petitioning was not a sham, does it follow necessarily that the lawsuit should be dismissed as a SLAPP?

Suppose, the Court proffered (quoting Illinois precedent), that defendant “‘spread malicious lies about an individual while in the course of genuinely petitioning the government for a favorable result.’”  The defendant passes muster under step one (if the statements are not parsed).  And the plaintiff cannot show sham under step two.  Case dismissed.  Yet “[i]f a plaintiff's complaint genuinely seeks redress for damages from defamation or other intentional torts and, thus, does not constitute a SLAPP, it is irrelevant whether the defendant[’s] actions were genuinely aimed at procuring favorable government action, result, or outcome.”

Thus the Court exposed a basic constitutional dilemma in anti-SLAPP: The plaintiff has a right to petition, too; plaintiff’s lawsuit is a constitutionally protected petition to the judiciary.  I would add, ignorance of this fact is why anti-SLAPP statutes, if not properly reined in by the courts, unfairly overcorrect in defendants’ favor.  One can argue that this operation of anti-SLAPP is a prophylactic protection for the petitioning rights of the defendant, thereby demanding that we tolerate dismissal of some meritorious causes of action—like the problematic “actual malice” rule of public-figure defamation.  But that argument fails to explain why the defendant’s petition right is superior to the plaintiff’s.

To solve this problem and mitigate its constitutional dilemma, the Supreme Judicial Court added a second way for the plaintiff to prove its way out of anti-SLAPP dismissal in step two of the test.  Recall that plaintiff bore the burden of prove sham petitioning by the defendant (and actual injury).  Well now the plaintiff may prove sham petitioning or plaintiff’s “suit was not ‘brought primarily to chill’ the [defendant]’s legitimate exercise of its right to petition.”  Thus, recalling the “malicious lies” example above, suppose furthermore that the plaintiff cared not one way or the other about the matter of defendant’s petition to the government.  Plaintiff rather was concerned with the malicious lies, however the matter was decided.  “A necessary but not sufficient factor in this analysis will be whether the [plaintiff]’s claim at issue is ‘colorable or … worthy of being presented to and considered by the court,’ … i.e., whether it ‘offers some reasonable possibility’ of a decision in the party’s favor.” 

On remand, then, the nurses would be able to avoid anti-SLAPP dismissal on the Globe statements, as well as the email, by showing the Globe statements a sham petition—unlikely—or by showing “that their defamation claim, viewed as a whole, is nonetheless not a ‘SLAPP’ suit.”  If they cannot meet their burden either way, then the hospital will be entitled to dismissal as to the Globe statements, the case over the email persisting.

The change is a dramatic one.  So modifying the plaintiff’s burden on step two of the test forces the trial court to confront head on the undisguised, central question of the anti-SLAPP inquiry.  Notwithstanding precedents that eschew focus on a plaintiff’s motives, the analysis inevitably steers the court back to ask whether the plaintiff is aggrieved by the hurtfulness of what the defendant did, or by the defendant’s aim to influence government.  For my money, one might as well ask that question at the start and be done with it.

The case is Blanchard v. Steward Carney Hospital, No. SJC-12141 (Mass. May 23, 2017) (Justia).


Justice Lenk issued a second opinion on anti-SLAPP for the Supreme Judicial Court the same day, May 23.  The case better fits the prototype anti-SLAPP mold in being a dispute over property development.  The Court remanded for application of its new Blanchard standard (case (2), immediately above).

In 2011, the plaintiff purchased a five-story brick building, 477 Harrison Avenue, Boston, to redevelop it for residential use.  Defendant JACE Boston owned neighboring 1234 Washington Street, which shared a wall with the Harrison property.  Defendant intended at some point to redevelop its property, too, and a competition ensued.  The parties disputed redevelopment plans in years of administrative process and litigation.  Finally in 2014, plaintiff sued defendant in superior court for abuse of process and for violation of Mass. Gen. L. ch. 93A, § 11, a broad state prohibition on unfair competition.

Upon defendant’s anti-SLAPP motion, the trial court determined that the defendant could not meet its step-one burden to show that the lawsuit was about solely petitioning activity, without other substantial basis.  The Court rather found that the abuse of process claim passed muster under step one, concerning solely defendant’s petitioning.  On step two, the plaintiff could not show that defendant’s petitioning, with respect to the abuse of process claim, was entirely a sham, that is devoid of factual and legal basis.  Nevertheless, under the newly announced Blanchard standard, the plaintiff on remand must be afforded the opportunity to resist dismissal by proving that its lawsuit is not a SLAPP—that is, “the motion judge may conclude with fair assurance,” “‘that [plaintiff’s] primary motivating goal in bringing its claim, viewed in its entirety, was “not to interfere with and burden defendants” … petition rights, but to seek damages for the personal harm to [the plaintiff] from [the] defendant[’s] alleged … [legally transgressive] acts.’”

Faced with “the novel issue as to whether all or only some of a [defendant’s] petitioning activities must be shown to be illegitimate in order to defeat a special motion to dismiss,” the Court decided that the plaintiff must “show that the entirety of its abuse of process claim is not a ‘SLAPP’ suit” to resist dismissal in full.  Otherwise, dismissal (and fees) are granted only for the “portion of the abuse of process claim arising out of the defendant[’s] protected petitioning activities.” 

The case is 477 Harrison Avenue v. JACE Boston, LLC, No. SJC-12150 (Mass. May 23, 2017) (Justia).

[UPDATE, Nov. 11, 2019: The SJC today issued another installment in 477 Harrison saga.  Remanding, the Court determined that abutters' counterclaims were retaliatory, not substantive, so should not be sustained against the developer.  I'll say again, anti-SLAPP was not designed to protect developers in land feuds, much less to generate multiple interlocutory dispositions, and this case speaks directly to the pathology of anti-SLAPP.]