Brian Daley

Teaching web design @UConnDMD and using web technology to help people. @uconndxgroup and @sourcery_app

[Brian Daley @UConnWebProf]

@JohnKrysinsky I also love that football players are assumed to be our best "athletes." (Whatever that term means.) It's an easy claim to make when nobody else plays your sport.

[Brian Daley @UConnWebProf]

@FOXSports @FOXSoccer @Jaboowins Please don't.

[Brian Daley @UConnWebProf]

Breeding is a terrorist.

[ArtButMakeItSports @ArtButSports]

Pentecost, by Friar Juan Bautista Maíno, 1615-20, 📸 via @MarchMadnessMBB

[UConn Men's Basketball @UConnMBB]

THE BRINGER OF RAIN 🌧️

[Brian Daley @UConnWebProf]

@JackMac The idea that our best "athletes" (however defined) are simply choosing a different sport to the detriment of US soccer is absurd. Anyone who has played or coached in our soccer hierarchy knows that it's a much more nuanced problem.

[Brian Daley @UConnWebProf]

@OfficialFPL That's Timber's goal. Redirection is clear as day.

[Captain-EO 👨🏾‍💻 @EOEboh]

Great question.
When you store passwords, you don't store them directly (that would be unsafe). Instead, you "hash" them. It is hashing that turns "password123" into something like "a7f8k2m9x4".

The problem is, if two people use "password123", they both get the same hash result. Hackers know this and have giant cheat sheets that say "if you see a7f8k2m9x4, the original password was password123."

The solution to this is "salting". Before hashing the password, you add some random junk to it.

So for User A, you might add "xyz" to their password, making it "password123xyz" before hashing.

For User B with the same password, you add different junk like "abc", making it "password123abc".

Now when hashed, they look completely different.

Benefits of salting is that even if a million people use "password123", every single one looks different in your database.

Hackers have to work much harder to crack each password individually

[Jay Rogers 👨‍💻 @jaydrogers]

It's finally here! serversideup/php v4 is now stable 🎉

😅 Over a year of work
🐘 FrankenPHP & Laravel Octane support
🤖 LLM integration on our docs
🤝 13 new contributors
❤️ All open source

Run PHP and Laravel anywhere you want.

Now go build awesome stuff, Internet. 🚀

[Povilas Korop | Laravel Courses Creator & Youtuber @PovilasKorop]

I think we, as Laravel/PHP community, have a problem.

I don't see many new/young devs starting with Laravel.

I also heard the same topic expressed by Taylor, Jeffrey, Nuno in podcasts.

Question: what can I/we do to promote PHP/Laravel to outsiders?

Let's brainstorm.

[Brian Daley @UConnWebProf]

Doing some decorating in i3 today.

[Tom Scheinfeldt @foundhistory]

Need a document scan from a repository in NYC or Boston? I know it’s hard to pull the trigger at $65 a pop. But you should know that your hard earned cash is landing in the pocket of some very talented and deserving grad students.

Also, 10% off with coupon code SOCIAL10 might ease the pain a bit.

#research #history #humanities #dh #genealogy #journalism #archives

[Tom Scheinfeldt @foundhistory]

Some great tips on remote archival research from @sourcery_app grad student, Mohammad Edalati

https://t.co/5U9fk22ggS

[Brian Daley @UConnWebProf]

@obsdmd Wow.

[ArtButMakeItSports @ArtButSports]

Tea Party, likely by Richard Collins, 1725-30, 📸 by @brilewerke

[Visual Studio Code @code]

Enhance your terminal experience in @code by enabling this one setting ⚙️

The terminal.integrated.suggest.enabled setting, currently in preview, surfaces rich completion support for your terminal.

[CBS Sports @CBSSports]

"There's honor in the way we went out."

An emotional Dan Hurley spoke with @tracywolfson after UConn's second round loss

[Brian Daley @UConnWebProf]

@paulg Florida, probably.

[Brian Daley @UConnWebProf]

The app is literally called "Teams" @Microsoft

[Brian Daley @UConnWebProf]

👇🏻

[Joel N @joelstarts]

I worked at BlackBerry (RIM at the time) in 2009.

The real reason for the downfall was the following.

Consumers wanted apps, but BlackBerry had two different customers: enterprise/gov and consumers.

Enterprise/gov customers cared a lot about security, of which BB was the best.

Consumers, aka end users, cared about apps.

BB was very cautious about the apps it brought onto the platform, among various other consumer-friendly products and features.

They should have separated into two subsidiaries, one phone focused on B2B and the other on the consumer experience.