secure_rails VS FriendlyId

See also: https://github.com/ankane/secure_rails/blob/master/README.md

See also: ankane/secure_rails Rails security Best Practices

update with rails production best practices, security best practices and rails-security-checklist

On a side note, "Sqids ... is an open-source library that lets you generate YouTube-looking IDs from numbers.", "The main use of Sqids is purely visual."

If the purpose of it is to give a friendlier url / id, who not use something like friendly_id instead? (http://norman.github.io/friendly_id).

The url is readable and searchable through the history.

I would much rather prefer people using "www.website.com/channel/video/a-dog-walking" instead of "www.website.com/channel/video/3cXv8c".

Take a look at https://github.com/norman/friendly_id for a good gem to implement them.

Check out the friendly_id gem! I remember watching a GoRails video about it and thinking it looked super easy to implement.

SEO tools - meta-tags, sitemap_generator and friendly_id

friendly_id - We will use the friendly_id gem, which created slugs that we can map to a predetermined route. This is a method you can use throughout an application, not just with the User models.

FriendlyId is the “Swiss Army bulldozer” of slugging and permalink plugins for ActiveRecord. It allows you to create pretty URL’s and work with human-friendly strings as if they were numeric ids for ActiveRecord models. 5,500 stars by now