The Rimfire Report: Why Your 10/22 Rifle is Inaccurate

https://www.thefirearmblog.com/blog/wp-content/uploads/2022/12/keyhole-targetfeat-180×180.png

The Rimfire Report: Why Your 10/22 Rifle is InaccurateHello everyone and welcome back to another edition of The Rimfire Report! This ongoing series is all about the rimfire firearm world and its various firearms, shooting sports, ammunition types, and history! Last week on The Rimfire Report we talked about the historical significance of what was collectively known as gallery guns – basically versions of rifles […]

Read More …

The post The Rimfire Report: Why Your 10/22 Rifle is Inaccurate appeared first on The Firearm Blog.

The Firearm Blog

Things That Don’t Suck: Faxon’s Ruger 10/22 Bolt Upgrade

https://cdn0.thetruthaboutguns.com/wp-content/uploads/2022/12/ruger-1022-bolt-6-scaled-e1670962187398.jpg

 

There are many parts that make up a 10/22 rifle, and each one of them plays an important role. However, the most critical component of the Ruger is the bolt. The trigger may be what initiates every shot, but it’s the bolt that’s responsible for shot-to-shot operation.

A high-quality bolt affects more than just reliability. The bolt face, its consistency, and how the firing pin strikes the bullet significantly contribute to the rifle’s accuracy.

Faxon Stainless Steel Bolt Assembly for 10/22

Faxon bolt sitting on it's butt against a white background

Whether you’re building up a new gun or keeping an old favorite running, the Faxon 10/22 Bolt Assembly is compatible with the OEM receiver, trigger group, charging handle, and bolt stop pin. The Faxon 10/22 bolt is fully assembled and ready to drop into your Ruger 10/22.

Specs

  • Material: 17-4 PH Stainless steel, H900
  • Hardness: HRC 40 – 47
  • Round Firing Pin
  • Sharp Extractor

Why Upgrade a 10/22 Bolt?

Upgrading the bolt improves reliability and accuracy on any 10/22 rifle. A high-quality bolt aftermarket bold like Faxon’s is properly radiused and polished to enhance the reliability of the cyclic action.

Additionally, Faxon’s 10/22 bolt has the proper head spacing in order to improve the reliability of the bullets feeding from the magazine into the chamber. Lastly, proper firing pin protrusion ensures optimal striking of the rimfire case.

All these small improvements add up to better overall reliability, consistent performance, and improved accuracy.

faxon bolt sitting against a white background

Does The Ruger 10/22 Have a Bolt Hold Open?

Out of the box in the stock configuration, the Ruger 10/22 doesn’t have a last-round bolt hold open feature. To add the bolt hold open feature, you need a third-party upgrade such as the CST Auto Bolt Stop.

What is a 10/22 Bolt Buffer?

A bolt buffer replaces/upgrades the bolt stop pin in your 10/22 receiver. The OEM bolt stop pin is made from steel, whereas the bolt buffer is made from a polymer material.

Over time the steel bolt stop pin can cause micro-cracks in the receiver due to repeated impacts of the bolt during shooting. The bolt buffer mitigates that and several other issues by being manufactured out of a polymer material.

top view of a ruger 10/22 bolt from faxon firearms

There are three main benefits of replacing the bolt stop pin with a bolt buffer.

  1. It reduces the sound when the bolt slams rearward during the cycling action during shooting. This is also a benefit when shooting suppressed as it greatly reduces the noise signature even more.
  2. The 10/22 blowback action is less shaky because of the dampening of the recoil and bolt cycling vibrations.
  3. It can prevent cracks in the 10/22 receiver resulting from prolonged usage, high round count shooting, or the added stress of high-velocity ammo.

top view of a faxon firearms bolt against a white backgound

The Ruger 10/22 bolt by Faxon includes a bolt buffer to replace the OEM bolt stop pin. If you’re interested in learning more, check out more on the Ruger 10/22 Bolt here.

 

This article originally appeared at Firearms Press and is reprinted here with permission. 

The Truth About Guns

First Human Trials Test Light and Sound Therapy For Alzheimer’s Disease

A new study published in the journal PLoS ONE has reported on the first human tests of an experimental therapy using sound and light to treat Alzheimer’s disease (AD). New Atlas reports: Over the last seven years, Li-Huei Tsai and colleagues at MIT’s Picower Institute for Learning and Memory have been investigating an unusual hypothesis. The researchers found toxic proteins associated with Alzheimer’s disease could be eliminated from mouse brains following exposure to flickering lights. Further research found the magic frequency was 40 Hz. When animals were exposed to both sound and light at that frequency, improvements in brain health were detected. Of course, these kinds of animal tests don’t mean much if they can’t be replicated in humans, so after further investigations revealed how this sensory therapy could be affecting a mouse brain, the researchers started preliminary human experiments. Working with colleagues at Massachusetts General Hospital, two clinical trials set out to test the therapy in humans.
The first Phase 1 study recruited 43 participants to test whether this kind of light and sound exposure was safe, and did anything to the human brain. Each subject was monitored using EEG measures while experiencing a short exposure to what has been dubbed by the researchers as GENUS (Gamma ENtrainment Using Sensory stimulation). This preliminary study comprised both healthy and cognitively impaired subjects, as well as participants with epilepsy in order to evaluate the seizure potential of the treatment. After a short exposure to the sensory stimulation, the researchers found a number of brain regions synchronize with the 40-Hz frequency.
The second trial recruited 15 participants with early-stage Alzheimer’s disease. Each participant was given a device to take home and use for around an hour a day. The device was essentially a small LED white board with an iPad in the middle and a soundbar underneath. While watching videos on the iPad, the LED light panel on the white board would flicker at a rate of 40 Hz and the soundbar would play a 40-Hz tone. Half the cohort was randomized to a sham control condition, exposed to a constant white light and white noise. Compliance was relatively high between both the GENUS and the sham groups, with participants completing the daily requirement of exposure around 90 percent of the time. After around three months of use the researchers could detect statistically significant differences between the two groups, both on brain imaging and memory tests. The researchers are cautious not to overstate their initial findings, the report says. "It’s early days for human studies […], larger cohorts of patients are needed to better understand the impacts of this sensory stimulation and longer trials will hopefully establish more prominent beneficial effects."


Read more of this story at Slashdot.

Slashdot

Setup your MacOS for Laravel Development

https://ahmadrosid.com/images/macos-for-laravel.png

Congratulations on your recent purchase of a MacBook! If you intend to use it for Laravel development, you have come to the right place. Allow me to guide you through the necessary steps for setting up your MacBook for a Laravel development environment.

Install PHP

To install PHP on macOS, you can use the package manager Homebrew. First, make sure you have Homebrew installed by running the following command in your terminal:

If you don’t have Homebrew installed, you can install it by running the following command:

Once you have Homebrew installed, you can install PHP by running the following command:

If you want to install specific php version you can search available php package in brew.

For example if you want to install php version 8 just.

Now export path for binary php, change ~/.zshrc to whatever shell you are using in this case I use zsh.

Install composer

To install Composer, you can follow the instructions on the Composer website: https://getcomposer.org/download. Here is a brief summary of the steps to install Composer on macOS:

Download the Composer installer by running the following command in your terminal:

Move the Composer binary to a directory that is included in your system path by running the following command:

Verify that Composer is installed by running the following command:

This should print the version of Composer that is installed on your machine

Install Laravel

This is optional. But if you want to create new project quickly you can use it directly from composer.

You also can create laravel project using the official cli. First install the cli.

Now export binary path.

And here’s how to create project from it.

Install MySQL

Most people use MySQL for Laravel projects. You might as well if you do. Please follow the instructions below for installation.

This will install the latest version of MySQL on your machine. You can verify that MySQL is installed by running the following command:

This should print the version of MySQL that is installed on your machine.

After installing MySQL, you will also need to start the MySQL server. You can do this by running the following command:

This will start the MySQL server in the background. To stop the MySQL server, you can run the following command:

To secure a MySQL installation, you can follow these steps:

Set a strong password for the MySQL root user: By default, the MySQL root user has no password, so you should set a strong password for the root user to prevent unauthorized access to your MySQL server. You can do this by running the following command:

Replace new_password with a strong password of your choice.

Reload the privilege tables: After making changes to the MySQL user accounts and permissions, you will need to reload the privilege tables to apply the changes. You can do this by running the following command:

I hope this helps! Let me know if you have any other questions.

Laravel News Links

Are You Nuts? Know your Fishing Knots! – Snell Knot

https://www.alloutdoor.com/wp-content/uploads/2022/12/20221212_165728-e1670885907355.jpg

This week we are going to show you how to tie a snell knot, also called snelling the hook. The smell knot is an older knot that was originally invented for tying hooks with no hook eyes. Instead, these hooks had a flattened wider portion of the shank that you would snell in front of. Nowadays though it is still widely used in many different techniques. In freshwater, bass anglers often snell hooks and use pegged bullet weights for punching matted vegetation. Fly anglers use the snell knot to keep a straight presentation for tube flies when fly fishing. In saltwater, it is popular for targeting big game, especially when pitching live bait or dragging baits on the bottom.

The snell knot is a very strong knot that when tied on a hook with an offset hook eye can keep the hook and line inline making it easier to get a good hook set. With the knot being behind the eye of the hook, this knot does not slip easily when under pressure. There is also plenty of meat to the knot so even if the hook eye isn’t closed completely there’s less risk of the knot failing due to a bad hook eye. The biggest downside to the snell knot is that the line can be easily abraded and cut if the fish you hook have sharp teeth, this is due to the line being on the hook shank itself.

Are You Nuts? Know your Fishing Knots! – Snell Knot

Step 1

First step as most knots is run the mainline through the eye of the hook, normally I use an offset hook but only have a straight shank hook for the demo.

Are You Nuts? Know your Fishing Knots! – Snell Knot

Step 2

Make a loop with the mainline and make sure to pinch the loop.

Are You Nuts? Know your Fishing Knots! – Snell Knot

Step 3

Using the pinched loop start wrapping the loop over the double line and shank of the hook, makes wraps towards the bend of the hook. Make sure to keep the loops from overlapping

Are You Nuts? Know your Fishing Knots! – Snell Knot

Step 4

Make about 6 to 8 wraps around the lines and shank of the hook, adjust for more loops for thinner lines, and then wet the knot. Then pull both ends of the line on the knot and snug the knot down. Trim the tag end and you’re ready to fish.

Are You Nuts? Know your Fishing Knots! – Snell Knot

The post Are You Nuts? Know your Fishing Knots! – Snell Knot appeared first on AllOutdoor.com.

AllOutdoor.com

Laravel Cookies Consent Plugin – Make your Laravel app compliant with the EU GDPR cookie law

https://opengraph.githubassets.com/3f36f64c581afab10d4862646cd54beff4f07535a273c187549b9c25e7469234/scify/laravel-cookies-consent

Laravel Cookies Consent Plugin – Make your Laravel app compliant with the EU GDPR cookie law

Latest Version on Packagist
GitHub Tests Action Status
GitHub Code Style Action Status
Total Downloads
GitHub Issues
GitHub Stars
GitHub forks
contributions welcome
License
Maintenance
Ask Me Anything !

About the plugin

According to the GDPR law, every platform is required to allow the users to decide which cookie
categories they will allow,
and, if a cookie category is not allowed, the application should not use the functionality tied to that cookie.

This plugin provides a simple cookie consent window through which the user can specify the cookies they would like to
allow.

After the user submission, the page reloads and the relevant cookies are set on the browser, and can then be used in the
front-end.

Features

  • Customizable cookie categories
  • Customizable pop-up view and style
  • Customizable show/hide "Read more" link
  • Customizable translations (6 languages already included)

Installation

You can install the package via composer:

composer require scify/laravel-cookies-consent

If on Laravel 9 or newer, the assets files (style.css) will automatically be published

If on Laravel 8 or older, make sure to manually publish the styles file, by running:

php artisan vendor:publish \
--provider="SciFY\LaravelCookiesConsent\LaravelCookiesConsentServiceProvider" \
--tag="laravel-assets"

In both cases, the assets files will be copied to public/vendor/cookies_consent.

You can then either decide to include the public/vendor/cookies_consent/style.css file to git (especially if you want
to edit it first), or add it to .gitignore, and make sure to also run this command on the staging/production server.

You can publish the config file with:

php artisan vendor:publish \
--provider="SciFY\LaravelCookiesConsent\LaravelCookiesConsentServiceProvider" \
--tag="cookies-consent-config"

The configuration file will be published to config/cookies_consent.php.

In the config file, you can change the cookie categories of your application, set the required and pre-selected
categories, as well as add new categories.

This is the contents of the published config file:

return [
    'cookie_prefix' => '',
    'cookies' => [
        'strictly_necessary', 
        'targeting', 
        'performance', 
        'functionality'
    ],
    'enabled' => [
        'strictly_necessary', 
        'targeting', 
        'performance', 
        'functionality'
    ],
    'required' => ['strictly_necessary'],
    'cookie_lifetime' => 365 * 10,
];

The cookie_prefix is optional and, if set, will be applied to every cookie.

If set, a good strategy is to also add a trailing underscore "_", that will be added between the field value, and each cookie.

For example, if cookie_prefix is set to my_app_, then the targeting cookie will have a value of my_app_cookies_consent_targeting.
You can add as many cookie categories as you like, simply by adding values to the cookies array.

If you want to remove a cookie category, simply remove it from the array.

You can use the enabled array to set the cookie categories that will be pre-selected,
and the required array to set the cookies that the user won’t be able to deselect.

If you want to change how long the cookies will be stored, edit the cookie_lifetime variable.

Usage

When the plugin is installed, a laravel-cookies-consent
custom Laravel View Component is automatically registered.

This will render the following cookies consent that, will look very much like this one.

dialog

You can then use this component in order to display the cookies consent window, wherever you’d like.

Typically, a good strategy is to put the component just before the closing <body> tag:

<body>
    ...
    ...
    ...
    <x-laravel-cookies-consent></x-laravel-cookies-consent>
</body>

After that, you can use the $_COOKIE global object, in order to check for the appropriate cookie.

Now you can use this object in your Blade files like this:

$_COOKIE[config('cookies_consent.cookie_prefix') . ]

For example, An application that wants to load the Google Analytics script only if the user has given their consent to
the targeting cookie category,
might do the following:

google-analytics.blade.php

<!-- Check the 'targeting' cookie: -->
@if(isset($_COOKIE[config('cookies_consent.cookie_prefix') 
. 'cookies_consent_targeting']) && config('app.google_analytics_id'))
    
    <!-- Google Analytics -->
    <script defer async>
        (function (i, s, o, g, r, a, m) {
            i['GoogleAnalyticsObject'] = r;
            i[r] = i[r] || function () {
                (i[r].q = i[r].q || []).push(arguments)
            }, i[r].l = 1 * new Date();
            a = s.createElement(o),
                m = s.getElementsByTagName(o)[0];
            a.async = 1;
            a.src = g;
            m.parentNode.insertBefore(a, m)
        })(window, document, 'script', 'https://www.google-analytics.com/analytics.js', 'ga');

        window.ga('create', '', 'auto');
        window.ga('set', 'anonymizeIp', true);
        window.ga('send', 'pageview');
    </script>
@endif

In this example, we checked whether
the $_COOKIE[config('cookies_consent.cookie_prefix') . 'cookies_consent_targeting'] key exists or not.

Customization

Customizing the component texts

If you want to modify the texts shown in the cookies dialog, you can publish the language resource files with this
command:

php artisan vendor:publish \
--provider="SciFY\LaravelCookiesConsent\LaravelCookiesConsentServiceProvider" \
--tag="cookies-consent-translations"

This will publish this file to resources/lang/vendor/cookies_consent//messages.php.

The plugin comes with 6 built-in languages. You can change the translations for a given language, or add additional
languages yourself.

Customizing the "Read more" link

In the cookies dialog, there is also an optional "Read more" link. This link is specified in the language translation
files, since it is common to have a different link for each language.

Example (file lang/vendor/cookies_consent/en/messages.php):

return [
    ...
    'read_more_link' => '',
    ...
];

If the link is left empty (default state), it won’t be shown.

Customizing the component contents

If you need full control over the contents of the cookies dialog, you can publish the views of the package:

php artisan vendor:publish \
--provider="SciFY\LaravelCookiesConsent\LaravelCookiesConsentServiceProvider" \
--tag="cookies-consent-components"

This will copy the resources/views/components/laravel-cookies-consent view file over
to resources/views/components/vendor/cookies_consent directory.

Testing

This project uses Pest for testing. To execute the test suite, run:

FAQ

Question: Is this plugin free to use?

Answer: Yes. This plugin is totally free and developed as
an Open-Source project.


Question: How long do the cookies last?

Answer: The duration is set in days, in config/cookies_consent.php file. In order to publish this file, run

php artisan vendor:publish \
--provider="SciFY\LaravelCookiesConsent\LaravelCookiesConsentServiceProvider" \
--tag="cookies-consent-config"

The configuration file will be published to config/cookies_consent.php.

Then, edit the cookie_lifetime field (in days).


Question: Will the cookie consent window show every time?

Answer: No. As soon as the user clicks one of the "Accept all", "Accept selection", or "Decline all", the selection
will be stored in another cookie, and the window won’t pop up again, until this cookie expires, or is deleted.


Question: In which languages is the plugin available?

Answer: The plugin has 6 built-in languages: English, Greek, Spanish, German, Italian, and Swedish. If you would
like to add a language, publish the translations by running:

php artisan vendor:publish \
--provider="SciFY\LaravelCookiesConsent\LaravelCookiesConsentServiceProvider" \
--tag="cookies-consent-translations"

And add/change your own translations. If you add a new language, consider also opening
a pull request, in order for this language to be included in
the plugin.


Question: Does this plugin work with all Laravel versions?

Answer: We have tested the plugin with Laravel 7, 8, and 9. The plugin’s simplicity allows it to work with any
Laravel version, but if you try it with a version other that the tested ones and it does not work, please open an issue
on GitHub.


Question: If I install later a new cookie category, how can I force the plugin to "reset" and show again?

Answer: The easiest way is to publish the configuration file, and change the cookie_prefix field. This will force
the plugin to show again.

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Credits

License

The Apache Licence. Please see the Licence File for more information.

Laravel News Links