Salubrious Ruby: Don’t mutate what you don’t own, by Tim Riley
> When we’re writing a method in Ruby and receiving objects as arguments, a helpful principle to follow is “don’t mutate what you don’t own.”
Tim is 100% correct - IMHO
P.S.A - RubyonRails have a new security release fixing two XSS vulnerabilities for all supported versions, pushing the current stables to these:
Una de las ventajas de los modos de publicación es que tus toots pueden ser enviados con varios tipos de alcance:
- public: default y bastante obvio
Por ejemplo este toot no va a ser visto en el timeline público, pero como te menciono tu puedes ser notificado y todos los demás no tienen que _joderse_, @porras
You probably didn't notice but one of the cornerstones of the ruby development has been changing for good: mail gem
A few days ago this PR by Deivid Rodriguez was accepted by the maintainers and it's all good news 🎉
Basically the mail gem moved their minimal ruby version to 2.5 from a very old ruby 1.8.
I get the idea of supporting more systems, but supporting a 20 year-old ruby version has been dragging the project for a while - IMO.
Welcome to the new & returning ruby.social users. Hope we can engage better this time.
Please try to follow up other peers, create your #introduction and pin your toot.
Remember this is not a "new twitter" the idea is kind of different. You can check @feditips to get more insights about how the federation works and how to have a better integrated environments.
P.S. there's no edit feature, but you can delete & redraft as I did with this toot.
New people, welcome to Mastodon and the Fediverse!
Here's how to get started:
2. Find out your Mastodon/Fediverse address so you can share it with friends (https://mstdn.social/@feditips/107248252715651564)
3. Invite people to join you on here by telling them to go to https://joinmastodon.org and click on "Get Started". It doesn't matter if they join a different server because the servers talk to each other (here's a bit more of an explanation https://mstdn.social/@feditips/107021461185874594)
4. Find out what the Fediverse is (https://mstdn.social/@feditips/107044096139091624)
5. Find out why Mastodon being on so many different servers/instances is a really good thing (https://mstdn.social/@feditips/107083735491993183)
6. If you see anything nasty, you can report it to your friendly server admin (https://mstdn.social/@feditips/106540152842368591)
7. You can (sort of) verify your account if you own a website (https://mstdn.social/@feditips/106274105538953001)
If you have any questions, @ me or DM me!
Ruby on Rails has released v. 7.0!!
This time I had the honor & privilege to contribute with 8 commits.
I'm so grateful for maintainers and contributors who #keepRailsRelevant
There's an interesting bug happening on Ruby's standard library where this code triggers an exception (and it shouldn't, IMO):
and here's my attempt to fix it:
Got a lot of fun recalling the networking algebra just for the sake of having tests to support the patch - there were no test for `to_range'
AppSignal: To concern or not concern
After 6 years of using Rails I'm still not sold of use concerns to simplify mixins.
Surely has their use cases but there's definitely better ways: containers, dependency injection, abstractions, or even plain modules.
"It's a concern when you start using Rails' concerns"
You may not be aware of this, but there's a lot of coordinated efforts to a better documentation of Ruby core classes & the standard library.
People like Burdette Lamar, Eric Holden (drbrain) and others has been nailing it going method by method doing a better docs.
Today Jeremy Evans proposed a "Method Documentation Guide" for this:
It's really nice to see this happening, if you are privilege enough to help, please do. The ruby ecosystem need your help.
Next time you think your data is not valuable remember these images.
This is what I can track in my local network. Nice graphs and metadata I got without any fancy nor expensive technology: around $0 since it's produced by my EdgeRoute X & PiHole.
Imagine this kind of data aggregated by your ISP or "no logger ever" VPN provider.
Not sure how developers can sleep having code like this:
return input.scan(/^\d*/) && $&.to_s
So, the reader/maintainers should read it says:
> Return the prefix of the string consistent of only numbers, otherwise an empty string. Note: no empty spaces allowed at the beginning of the input.
Yes, I do #hateRegex
A Mastodon instance for Rubyists & friends