ForgottenFlux@lemmy.world to Technology@lemmy.worldEnglish · 13 days agoUS sues Adobe for ‘deceiving’ subscriptions that are too hard to cancel | The Justice Department alleges that Adobe hid early cancellation fees and trapped consumers in pricey subscriptionswww.theverge.comexternal-linkmessage-square81fedilinkarrow-up11arrow-down10 cross-posted to: technology@lemmy.worldtechnology@lemmy.worldtechnology@beehaw.org
arrow-up11arrow-down1external-linkUS sues Adobe for ‘deceiving’ subscriptions that are too hard to cancel | The Justice Department alleges that Adobe hid early cancellation fees and trapped consumers in pricey subscriptionswww.theverge.comForgottenFlux@lemmy.world to Technology@lemmy.worldEnglish · 13 days agomessage-square81fedilink cross-posted to: technology@lemmy.worldtechnology@lemmy.worldtechnology@beehaw.org
minus-squareSeptimaeus@infosec.publinkfedilinkEnglisharrow-up0·12 days agoI’m curious about this. If demonstrable, many could sue for damages. For these government websites, what is the typical user workflow? An embedded Adobe applet (e.g. fill, sign, and submit on the government website) Token-based API (e.g. redirect or spawn child window/tab, user fills and signs on adobe site, user returned to government site). Something else, such as a document upload button with server-side validation for digital signing?
/cdn.vox-cdn.com/uploads/chorus_asset/file/23624358/acastro_STK124_04.jpg)
I’m curious about this. If demonstrable, many could sue for damages.
For these government websites, what is the typical user workflow?