Remote
Ian
@soviut@hachyderm.io
mastodon
4.6.6
Full stack developer with a passion for frontend.
he/him, Canadian
0
Followers
0
Following
50
Posts
Joined November 23, 2022
Zamtools:
CreatorGuard:
Posts
Replying to
@thomasfuchs@hachyderm.io
@thomasfuchs@hachyderm.io Not to mention it positions it self as a "privacy focused" browser and yet it was caught injecting affiliate links into URLs.
Their TOR implementation leaked DNS queries effectively making it pointless.
They collected cryptocurrency donations (BAT payments) using a system that looked like people were donating to youtube creators like Tom Scott.
And more...
https://www.reddit.com/r/browsers/comments/1j1pq7b/list_of_brave_browser_controversies/
Replying to
@pomegranate_stew@kind.social
@pomegranate_stew@kind.social @antipode77@mastodon.nl @ProPublica@newsie.social Your town got hosed. It had a direct rail line and still only has 5000 people in it? Sounds like it got gutted by the interstates. Remember that; cars ruin cities. Asphalt is expensive to maintain, has terrible drainage issues and is destroyed by heavy trucks that could have been delivered literally straight to your town via rail.
Replying to
@Linza@kamu.social
@Linza@kamu.social @pomegranate_stew@kind.social @antipode77@mastodon.nl @ProPublica@newsie.social You're right; put those on the roads instead.
Replying to
@pomegranate_stew@kind.social
@pomegranate_stew@kind.social @antipode77@mastodon.nl @ProPublica@newsie.social This is so car-pilled. There are solutions for getting past train tracks; don't build level crossings!
Replying to
@bagder@mastodon.social
@bagder@mastodon.social I feel like some of these figures can be gamed since you can vibe code a LOT of bugs/vulnerabilities into a project then turn around and claim you're fixing more bugs than ever.
Sorry to be cynical, but it's the first thing that came to mind these days when I saw this slide.
Replying to
@ProPublica@newsie.social
@ProPublica@newsie.social Sounds like he's suggesting we replace road-destroying trucks with trains.
Replying to
@SwiftOnSecurity@infosec.exchange
@SwiftOnSecurity@infosec.exchange If you just started with OnlyFans you'd be able to cut out a lot of unnecessary social media.
Replying to
@mitch@hachyderm.io
@mitch@hachyderm.io @pluralistic@mamot.fr it bodes well for transit and bike infrastructure as well.
Replying to
@codepo8@toot.cafe
@codepo8@toot.cafe @guardian@press.coop The term doesn't carry the same connotation here in Canada and the genres of music he plays would never call it a "violin". I could meet you halfway at "fiddle player" as being least ambiguous.
Replying to
@vga256@mastodon.tomodori.net
@vga256@mastodon.tomodori.net You should reach out to Nathan Baggs on YouTube to see if maybe he'd be able to crack it.
https://www.youtube.com/channel/UCQvW_89l7f-hCMP1pzGm4xw
Replying to
@kj6evv@mastodon.hams.social
@kj6evv@mastodon.hams.social @vga256@mastodon.tomodori.net Quark Express-ionism? CD ROM-antacism?
Replying to
@vga256@mastodon.tomodori.net
@vga256@mastodon.tomodori.net That box is some peak 90s desktop publishing.
White box? Got it.
You want skinny fonts? We got that.
Vertical text? No problem.
A gradient? Done!
Teal and purple? They won't even let us save the file without them.
A bunch of intertwined photographic elements? Sure thing; I threw in the background texture for free.
Replying to
@cwebber@social.coop
@cwebber This isn't so much a defense of it, but the built in budgets are a pretty nice safeguard for those of us tasked with building "chat bot for ___" demos that have to be deployed to semi-live staging environments so our clients can try them out.
Replying to
@pluralistic@mamot.fr
@pluralistic There's a certain irony to them looking upset that you're taking pictures of their faces.
Replying to
@rrustema020@mastodon.nl
@rrustema020 @notjustbikes Screw both of them; they're both car-pilled goofballs living in a hell hole built around needing a car to do anything.
@thomasfuchs@hachyderm.io So what you're saying is that, with enough vibe coding, we could destroy all social networks?
This sounds like pure upside.
Replying to
@carnage4life@mas.to
@carnage4life@mas.to or questioning whether your approach that it ignored is actually wrong.
"would it not be better to do X?" followed by a "you're absolutely right" response from the LLM.
Replying to
@beyondmachines1@infosec.exchange
@beyondmachines1@infosec.exchange Joke's on you LinkedIn, I never log in to the site.
The fact that some people use it as some weird business-centric social network makes me feel like perhaps they deserve it.
Replying to
@Migueldeicaza@mastodon.social
@Migueldeicaza Shows how dangerous they consider journalists to be.
Replying to
@adamshostack@infosec.exchange
@adamshostack No kidding, they're not even offering a simulation for us to live in while they do it.
Replying to
@nixCraft@mastodon.social
@nixCraft@mastodon.social Good to see Tesla and Meta not far behind.
Replying to
@ml@social.mitexleo.one
@ml Don't own a car and write to your local politicians to improve transit and bike infrastructure. You too can pay $0 on gas.
Replying to
@attoparsec@clacks.link
@attoparsec@clacks.link There needs to be one of these hanging in every pub in the US.
After all, if you let one ICE in, they'll bring their friends, and before you know it, you've got a bar full of nazis...er, ICE.
Replying to
@arstechnica__dup_1397@mastodon.social
@arstechnica I'm looking forward to the day when these towns start to actively sabotage these datacenters.
Replying to
@molly0xfff@hachyderm.io
@molly0xfff Think of all the AI token you'll be able to afford now!
Replying to
@emc2@indieweb.social
@emc2@indieweb.social @hacks4pancakes@infosec.exchange Indeed. The issue with all the so-called checks and balances is that it was assumed that rational, reasonable people would be there to enforce them.
Replying to
@librarysquirrel@sunny.garden
@librarysquirrel@sunny.garden @heliographe_studio@mastodon.social I'm just telling you what the science says; modern icons, developed with care, are more accessible.
Better contrast, faster identifiability, they survive on small and large display sizes at near and far distances. They survive poor lighting conditions. They survive colour blindness, partial sightedness, neuro optical disorders, etc.
Cute illustrations were so Steve Jobs could show off that OSX had 32 bit colour and could scale icons with the GPU.
Personal preference and aesthetics don't beat the science.
Replying to
@librarysquirrel@sunny.garden
@librarysquirrel@sunny.garden @heliographe_studio@mastodon.social It's more than that; there's visual rhythm, feature size, contrast, colour depth, etc.
The icons aren't the rectangles, the icons are the image inside the rectangles. The rectangles are usually an indicator that something is clickable, like a button. Icons on their own don't necessarily convey click-ability. An example would be the battery indicator on your phone.
A lot of effort goes into designing icons that are legible, identifiable, and most importantly accessible. They serve a functional purpose that goes far beyond their aesthetics and cater to a much wider audience than just you.
Replying to
@Irenetherogue@beige.party
@Irenetherogue@beige.party @aj@gts.sadauskas.id.au @drdrowland@fediscience.org @SeanCasten@mastodon.social yeah. I'm sarcastically throwing the right's "they're coming to take our guns" rhetoric back at them.
Replying to
@aj@gts.sadauskas.id.au
@aj@gts.sadauskas.id.au @drdrowland@fediscience.org @SeanCasten@mastodon.social so ice was "trying to take their gun"?
Replying to
@mattblaze@federate.social
@mattblaze@federate.social After your second civil war they'll hopefully put them back up.
Replying to
@librarysquirrel@sunny.garden
@librarysquirrel@sunny.garden @heliographe_studio@mastodon.social Silhouettes mostly. There's a reason you could recognize every pokémon when they did the "who's that pokémon" bit in the show; their silhouettes are intentionally designed to be very unique. The character design in Team Fortress 2 is similar; you can identify what class a player is at a glance even in dimly lit areas of the map.
The same goes for icons; they should be highly recognizable under any viewing conditions. We don't all run our phones at full brightness, we're glancing at them when we get a notification that disappears quickly, etc.
Replying to
@librarysquirrel@sunny.garden
@librarysquirrel@sunny.garden @heliographe_studio@mastodon.social Regardless, they're icons, not illustrations. They're meant to be understood at a glance and in concert with other icons around it. They often have to survive across multiple types of displays and lighting conditions as well. Illustration and skeuomorphism don't usually lend themselves well to this.
Replying to
@loke@functional.cafe
@loke@functional.cafe @glent@aus.social @heliographe_studio@mastodon.social In both cases those are very iconographic. Silhouettes with clear poses, details like faces and skin tones are removed, etc.
The only difference is that the sign is clarified to indicate that they're guarding, while the old one look like they're in active combat.
Replying to
@glent@aus.social
@glent@aus.social @heliographe_studio@mastodon.social That isn't a cultural thing; plenty of standardized iconography exists in Japan for warnings, traffic signals and signs, etc. In this case you'd be hard pressed to find clear icons for those four specific dangers.
Japan is well known for its iconography. It's flag is literally iconic of the rising sun. Emoji originated in Japan which is pretty much an iconographic alphabet.
Replying to
@JoeBeam@mastodon.social
@JoeBeam@mastodon.social @heliographe_studio@mastodon.social This is neither iconography, nor illustration; it's type setting. hehe
Replying to
@heliographe_studio@mastodon.social
@heliographe_studio@mastodon.social More like really good at illustration, not good at icon design. Icons are intentionally simple for legibility.
There's a reason danger signs are iconographic and not illustrative; wood chipper and acid warnings would be too horrific to look at.
Replying to
@ut3usw@mastodon.radio
@ut3usw@mastodon.radio This runs smoother than it did on my neighbour's 486
Replying to
@jon@henshaw.social
@jon@henshaw.social A lenticular display channeling its inner zoetrope in cup form.
Replying to
@gedeonm@mastodon.social
@gedeonm I feel like that's a trap intelligent people set for themselves; You're too competent to believe anyone could be that incompetent.
It's kind of like a conspiracy theory for sane people who are really hoping someone's in control.
Replying to
@slightlyoff@toot.cafe
@slightlyoff @sil I don't believe that at all. Unskilled developers in the frontend are significantly less dangerous than when they're granted access to the backend.
Just look at all the accidental leaks that have happened in Next when those same devs have direct access to the database and secret keys with server actions and such.
That doesn't mean solutions like SSR aren't viable. You get much better time to first contentful paint, avoid loading spinners and don't have to heavily modify your frontend app to accommodate it.
Point being, yes, you can optimize at the server, but it comes with risks that pure frontends don't.
Replying to
@slightlyoff@toot.cafe
@slightlyoff @sil What I'm saying is the stakes are even higher in the backend. Those same inexperienced developers who made a bulky frontend are now able to create real security vulnerabilities.
This isn't me speculating, I've encountered it several times. I had to pause a project because I discovered over 5000 SQL injection vulnerabilities in their API. The only reason they hadn't been utterly pwned is because their host had some rudimentary injection prevention middleware.
Had they used a framework, they wouldn't have been able to produce those vulnerabilities (at least not as easily as they did raw dawging it).
To summarize, servers are a luxury and should be treated as such. If your team is struggling to ride a bicycle, don't give them a motorcycle.
Replying to
@slightlyoff@toot.cafe
@slightlyoff @sil Less catastrophic? Every major data breach for nearly a decade was Wordpress sites getting hacked. Even popular open source maintainers couldn't secure their PHP.
All I'm saying is, call out the actual culprits; in this case, React. Vue and Svelte are both are more efficient and better citizens in the space.
Replying to
@slightlyoff@toot.cafe
@slightlyoff @sil If closer to the metal limited factors, then PHP sites would be a lot less prone to issues. Instead, it took a framework like Laravel to remove a lot of the PHP "foot guns".
I'm not disputing that showing a loading spinner on a benefits site is ridiculous. If you need one before you can even interact then you've already failed.
Building performant frontends isn't a hard thing to do, just something you have to be aware of. In my experience, this mostly boils down to saying no to "grid" components and no to charts libraries, haha.
Replying to
@slightlyoff@toot.cafe
@slightlyoff @sil Not only have I seen way worse structural MPAs, but I've seen ones that are terrifyingly insecure as well.
The blast radius of a mistake in server side is so much worse. You see it now as server components and mixed client/server state accidentally leak because a convention got messed up.
These teams will exist no matter what and their impact will be worse the closer to the metal you put them.