this post was submitted on 01 Jun 2023
7 points (100.0% liked)

Technology

37747 readers
39 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

The Web Applications Working Group has published Web Share API as a W3C Recommendation. This specification defines an API for sharing text, links and other content to an arbitrary destination of the user’s choice. The available share targets are not specified here; they are provided by the user agent. They could, for example, be apps, websites or contacts.

top 5 comments
sorted by: hot top controversial new old
[–] schizanon 3 points 2 years ago (1 children)

I'm super stoked to see this API finally hitting recommendation. Next up Web Share Target API! #webDev #web #api #programming #javaScript #webPlatform #frontend

[–] schizanon@mas.to 2 points 2 years ago (1 children)

@schizanon@beehaw.org weird how hashtags created in #lemmy posts aren't linked ^

[–] ollien 2 points 2 years ago

Interestingly, for me they link to Mastodon. Heh.

[–] ollien 2 points 2 years ago (1 children)

While I haven't read through the spec to see how they deal with this, my immediate thought upon seeing the JS snippets is how spam sites might use it. Similar to a MFA fatigue attack, it seems plausible to me you may use this API to get your spam shared by shoving the share menu on people's faces repeatedly.

[–] schizanon 2 points 2 years ago

Nah, the share api just pops up the OS share dialog, if the user didn't want that they can just close it, if they click a share target then when the share target usually asks for another confirmation click. It's not likely the user will click three times accidentally.