view the rest of the comments
Mildly Infuriating
Home to all things "Mildly Infuriating" Not infuriating, not enraging. Mildly Infuriating. All posts should reflect that.
I want my day mildly ruined, not completely ruined. Please remember to refrain from reposting old content. If you post a post from reddit it is good practice to include a link and credit the OP. I'm not about stealing content!
It's just good to get something in this website for casual viewing whilst refreshing original content is added overtime.
Rules:
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means: -No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
7. Content should match the theme of this community.
-Content should be Mildly infuriating.
-At this time we permit content that is infuriating until an infuriating community is made available.
...
8. Reposting of Reddit content is permitted, try to credit the OC.
-Please consider crediting the OC when reposting content. A name of the user or a link to the original post is sufficient.
...
...
Also check out:
Partnered Communities:
Reach out to LillianVS for inclusion on the sidebar.
All communities included on the sidebar are to be made in compliance with the instance rules.
It's because they're using a chrome only API to interact with USB devices. This used to be a dedicated piece of software. I guess they don't even want to provide an electron app.
Honestly, I kinda hate the idea of a browser being able to access hardware devices.
That’s why no one outside Google wants it. Apple said no. Firefox said no. There’s a reason. WebRTC is shit. It leaks too much just for a small convenience.
And yeah, browsers don’t need my USB ports thanks.
This move was what hurt VIA as they moved to the API exclusively. So the only native apps are just electron wrappers 🤷♂️
Edit: Looks like Mozilla said yes after all heavy sigh: https://developer.mozilla.org/en-US/docs/Web/API/WebUSB_API
At the end we have Flash + ActiveX alltogether again.
WebRTC and WebUSB are different things. RTC doesn't provide direct port access, afaik.
I know. Both have the same fundamental premise: to leak data that shouldn’t be leaked.
“WebUSB provides a way for these non-standardized USB device services to be exposed to the web. This means that hardware manufacturers will be able to provide a way for their device to be accessed from the web, without having to provide their own API.”
That’s from Mozilla. And that’s a hard pass. Why anyone wants this is beyond me. Just so long as there’s a flag to turn it off.
Have you worked with either before? They're completely unrelated technologies, with similar names. They have nothing to do with one another. They're not even being developed by the same groups. They emphatically do not have the same fundamental premise. I've built apps in WebRTC before, and I can guarantee it has nothing to do with WebUSB, and in fact I just confirmed in the docs that it has nothing to do with any sort of device-level hardware control.
To reiterate: the only connection between WebUSB and WebRTC is the fact that they're named "Web" + three letter initialism.
Wikipedia is pretty aggressive with these bots
I have absolutely no idea what that's intended to mean.
Bots never do.
Oh cool, ad hominem. The clearest and most humble concession of defeat. Very well, I accept your capitulation.
Only losers claim victory in such ways
I have no need to claim it when you so freely offer it.
That's their web dev documentation. The official position is no: https://mozilla.github.io/standards-positions/#webusb
Is this an app for recording and editing podcasts? Why do they need usb access for that? On its website it doesn't says anything about usb.
Microphones, webcams, capture cards, etc
those do not require access to the underlying devices to get tho
What do they need that for? Every bowser has a file picker/dragndop.
I see it as them interacting directly with microphones, webcams, and other peripherals.
Every browser manages that too, though.