chameleon avatar

chameleon

@chameleon@kbin.social

i'm lizard 🦎

AnonTwo,

Audio size is based on the quality of the recording, not what the recording is.

If the white noise is for some reason recorded in high quality, it's going to use as much data as music.

IHeartBadCode,
IHeartBadCode avatar

WEI is not designed to single out browsers or extensions

Let's take a look at exactly the things from Wiser that he indicates was inspiration for WEI.

App Attest and Play integrity API. Both of these APIs are used to ensure that the hardware is in a particular configuration. Namely to ensure that you aren't using a device with an unlocked bootloader. Now Google and Apple will say, "THEY are NOT the ones enforcing it, they're just telling on you but it's ultimately up to the remote if they wish to accept your unlocked bootloader or not."

That's the thing. WEI would be roughly the same thing. Chrome wouldn't "prevent" you from having an ad-blocker, it's just that if you had one, they would absolutely be telling on you to the website. It's completely up to the website if they want to show you a site with your ad-blocker.

The details are nebulous, but the goal seems to be to prevent 'fake' interactions with websites of all kinds. While this seems like a noble motivation, and the use cases listed seem very reasonable, the solution proposed is absolutely terrible and has already been equated with DRM for websites, with all that it implies.

— Julien Picalausa, a software developer for Vivaldi

And I agree with Julien. This has to be the dumbest way to do what the stated goals are. Because what if I have a browser on a custom compiled Linux kernel? What if I've turned off SecureBoot? How will the attest software KNOW for SURE, I'm not messing with it? And the only way, that can happen, is the exact same way that SafetyNet gave way to Android Play Integrity. Only particular models are allowed. It's why some APKs won't load on a custom Android. Your frankentablet just isn't part of the established crew, you don't get that app.

The fact that Wiser completely ignores the history that lead to the two APIs that they cite is so gross, there's no way Wiser just "forgot" to mention how all that played out. There's no way that this Google Engineer was that stupid to not see where this was going.

It is clear based on the feedback we’ve received that a bigger discussion needs to take place

Bullshit! You got called! That's what happened. You are not dumb, you knew exactly what this API was pitching. You even cited two APIs that went the exact way that you claim this wouldn't happen for WEI. BULLSHIT!!

No one should be using Google Chrome at this point because they are absolutely going to try this shit. They don't have any compunction for the ramifications of what WEI will do. No. They're just tail between legs right now because someone found out about their bullshit and sounded the alarm. The second everyone goes radio silence on the matter, it'll be back to bat for this shit.

Google is shit and they prance around like they are some sort of liberator. They talk mad about ASOP, that's Android's Open Source side of things. But ASOP is useless. There's no hardware today that you can compile ASOP for, and run native. You have to have closed binary blobs to compile into ASOP just to run on literally anything. And even when you do have ASOP, none of the apps use the native services any longer. It's all in Google Play Services now. Like you can tap on your GPS hardware directly, but your OS will report it GPS and not eGPS, why? Because eGPS only comes with a special stamp, and that stamp only comes with Google Play Services. And the hardware API, none of that is solid ground. Google modifies that shit in ASOP all the time, they just tell you that if you want a stable API, hit up the Google Play Services. Hell LineageOS, probably the best known custom ROM, even covers the blobs here. But most people just download an image and not actually build their own custom ROM. The fact that these binary blobs that we don't know what's going on inside of them are the goto way to make custom ROMS is likely the only reason Gapps (all the Google apps) still run on custom ROM. The attesting software sees enough of the closed off blob to assume some ability to secure the environment.

There's nothing open source about Android. Yes, they put out ASOP so that they meet the minimum GPL agreement. But you cannot run ASOP without making it closed. And this fucker indicated that "Yeah, this sounds like a wonderful way to solve a problem in web browsers." There's no way this Wiser person just oops missed all that history. Just absolutely NO WAY. They got caught and they're trying to walk it back to save some face.

Google is working on essentially putting DRM on the web (github.com)

The much maligned “Trusted Computing” idea requires that the party you are supposed to trust deserves to be trusted, and Google is DEFINITELY NOT worthy of being trusted, this is a naked power grab to destroy the open web for Google’s ad profits no matter the consequences, this would put heavy surveillance in Google’s...

tojikomori,
tojikomori avatar

"Good vibes only" seems to be embedded in the culture of web development today. Influential devs' Twitter accounts have strong Instagram vibes: constantly promoting and congratulating each other, never sharing substantive criticisms. Hustle hustle.

People with deep, valid criticisms of popular frameworks like React seem to be ostracized as cranks.

It's all very vapid and depressing.

EnglishMobster, (edited )
EnglishMobster avatar

tl;dr: It's Mastodon. You can use Mastodon from Kbin.


The Microblog tab shows posts from Kbin + Mastodon, just like how the Threads tab shows posts from Kbin + Lemmy. So if you have people you like on Mastodon, search for them using the little magnifying glass and then follow them from Kbin. Their posts will appear in the Microblog tab.

Additionally, if people on Mastodon use a for something, it'll automatically be sorted in magazines that care about that hashtag. This means if you follow someone and that person uses a hashtag, their post will be placed in the "Microblog" tab of whatever magazine relates to that hashtag. This allows other people to discover the person you're following through shared interests.

For example, the Internet Archive has a Mastodon account - @internetarchive. The Internet Archive used their Mastodon account to make a toot on Mastodon: https://mastodon.archive.org/@internetarchive/110611348840969515

Because people are following the @internetarchive account from Kbin (which you can do by going here or by searching Kbin for their username, @internetarchive@mastodon.archive.org), that post was federated here to Kbin. Once it showed up, it appeared in the "Microblog" tab and got automatically organized into Kbin's @Futurology magazine because it used the hashtag : https://kbin.social/m/Futurology/p/565801/Exciting-news-Introducing-ARCH-Archives-Research-Compute-Hub-a

Magazine moderators determine what hashtags they want included in their magazine - so @Futurology has said "We would like all posts with to show up in our microblog section". (You can go to @Futurology directly to see what hashtags the mod team thinks are relevant.)

If no hashtags are used on a post (or none of them match any magazines), then it goes to the magazine @random.


Wanna write a tweet/toot from right here on Kbin? Put it in a microblog. Use to organize it into a magazine, or use the dropdown on Kbin to pick a magazine manually.

People can follow your Kbin profile from Mastodon. They'll see microblogs as a Mastodon toot, and "boosts" as basically Mastodon's version of retweets. People on Lemmy don't see boosts, but will see microblogs as a "normal" Lemmy post (since Lemmy doesn't have a "microblog" tab).

For example. I made this post to the Microblog here on Kbin: https://kbin.social/m/Disneyland/p/510705

I made it from the main "microblogs" tab, but it used the hashtag . @Disneyland listens to that hashtag, so Kbin automatically put it there: https://kbin.social/m/Disneyland/p/510705/Went-to-Disneyland-over-the-weekend-and-went-on-RunawayRailway

If you go to Mastodon, you'll see it as a normal toot: https://sunny.garden/@EnglishMobster@kbin.social/110587107756032019

If you go to Lemmy, you'll see that microblog as a Reddit-like post: https://lemmy.world/post/418494?scrollToComments=true

(Note that it seems things which come from Mastodon don't get automatically sent to Lemmy - just microblogs from Kbin itself. That Internet Archive post I mentioned above doesn't seem to exist on Lemmy.world.)


This behavior is one of the main reasons why I chose Kbin over Lemmy; I love that I can post once and have my stuff federated everywhere else super cleanly and easily. Lemmy is a bit more messy when it comes to Lemmy -> Mastodon and the devs aren't interested in changing how it works (I asked before I came over here).

Ernest seems really invested in playing to the strengths of the fediverse, and the Kbin roadmap has him planning to integrate more fediverse services in the future. For example, Mobilizon support is planned, which is like a group calendar on the fediverse.

If @Starwars wanted to have a watch party for a new episode of The Mandalorian, they could (theoretically) schedule an event on Mobilizon and have it federate to their magazine as a normal thread. Then they could (theoretically) pin the Mobilizon thread and use the comment section of the event as a Kbin megathread when the episode airs. See https://demo.mobilizon.org/ and imagine it being part of Kbin, just as Lemmy and Mastodon are "part of Kbin."

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • kavyap
  • DreamBathrooms
  • Durango
  • osvaldo12
  • everett
  • magazineikmin
  • Youngstown
  • thenastyranch
  • rosin
  • slotface
  • cisconetworking
  • mdbf
  • ngwrru68w68
  • modclub
  • khanakhh
  • InstantRegret
  • tacticalgear
  • ethstaker
  • normalnudes
  • tester
  • anitta
  • Leos
  • cubers
  • GTA5RPClips
  • megavids
  • provamag3
  • lostlight
  • All magazines