rlamacraft @rlamacraft@qoto.org

A worked-out example of how the ".zip" domain that Google has opened to registrants can be used in phishing attacks. The URL with the @ sign, and the characters that look like forward-slashes but aren't, looks like it goes to Github to download a zip file, but it actually goes to a server the phisher has registereed with the address "v1.27.1.zip".

The trick can also be pulled with other TLDs, but the .zip domain may make the URL look more like an expected file download.

https://medium.com/@bobbyrsec/the-dangers-of-googles-zip-tld-5e1e675e59a5

I have a new #Gemini project to announce!

💬 Bubble

It is a Gemini-based bulletin board system that combines elements from Station, Reddit, WordPress, and Git-adjacent issue trackers like on GitHub.

Check out the introduction and kick the tires over at: gemini://geminispace.org/u/skyjake/1

@raphael_fl @rodhilton

Right here.

#GoogleIO revealed the two weirdest features as a pair.

1. Give a short summary and Google will draft an e-mail for you based on it. You can even click "elaborate" and it will make the e-mail longer.

2. When opening an e-mail, Gmail can summarize the entire thing for you so you don't have to read all of it.

Does everyone realize how fucking bizarre this is?

Both people in the conversation want to work with directness and brevity, and Google is doing textual steganography in the middle.

Interviewer: Can you explain these gaps in your resume?

Me: Those are typographical indicators called spaces, and line breaks that separate words and paragraphs.

The amount of money CEOs are willing to invest in an AI that constantly screws up at its job with the promise it will get better is nowhere the amount of money they'd be willing to invest in an employee who constantly screws up while promising they'll get better.

#WeaversDeepThoughts #AI

@GeePawHill I’ve lately been thinking about starting a new project as planting a seed. Then I have to take care of it, tend to it, prune bad parts, and overall make it grow. Take some cuttings and plant them in a new area.

Let’s me think of myself as a software gardener: I grow software.

In the first 4 hours of any software project, we could, indeed, characterize what we do as "writing code". But that's the morning of the first day. After that, all we ever do with code on that project is change it.

Professional software developers *change* code.

"Develop" is a synonym for "change".

To learn how be a professional software developer, focus your learning around the topic of *changing* code.

accurate, af.

That people are taking ChatGPT seriously for coding tells you more about the state of software engineering as a discipline than it does about the state of machine learning as a technology.

In a world where developers can get a lot of help from Copilot, ChatGPT, StackOverflow, etc., there are still certain coding skills that characterize the best software developers. As just one example, real developers use data types in a way that makes their code cleaner and more reliable -- they define types like "heightInCm" or "widthInPixels" instead of floats and ints, and suddenly code is 10x easier to reason about.

In your opinion, what are some other hallmarks of top 1% developers?

Any experienced programmer worth their salt will tell you that •producing• code — learning syntax, finding examples, combining them, adding behaviors, adding complexity — is the •easy• part of programming.

The hard part: “How can it break? How will it surprise us? How will it change? Does it •really• accomplish our goal? What •is• our goal? Are we all even imagining the same goal? Do we understand each other? Will the next person to work on this understand it? Should we even build this?”