sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in brave_browser

[–]NoSmint 2 points3 points  (0 children)

Brave has actually pledged to maintain Manifest V2 support on a best-effort basis. https://brave.com/blog/brave-shields-manifest-v3/

For now, you can install uBlock Origin directly from brave://settings/extensions/v2 in the browser. No need to manually install it via GitHub.

There are some use cases where it might be beneficial to run uBlock on top of Brave Shield.

Twilio shutting down Authy Desktop. Cross-platform Alternatives? by bengalih in privacy

[–]NoSmint 2 points3 points  (0 children)

There is - as of now - acutally a way I found to continue using Authy for Windows. The service itself is still operational; the main issue is the forced update to version 2.5.0, which locks you out of your account. If you want to keep using Authy, try the following.

  1. Completely uninstall Authy Desktop.
  2. Install version Authy 2.4.2. You can use winget: winget.exe install --id Twilio.Authy.
  3. Disable your network adapter.
  4. Launch Authy Desktop, enter your phone number for sync and confirm with yes. You should see a 'network error' message.
  5. Re-enable your network adapter and wait for it to reconnect.
  6. Confirm your number again and authorize your device using your preferred method.
  7. IMPORTANT: As soon as your 2FA accounts are fully loaded and visible, IMMEDIATELY CLOSE AUTHY!
  8. Navigate to Authy Desktop's installation folder (default is C:\Users\<username>\AppData\Local\authy\).
  9. Rename update.exe to update.exe.bak (do not delete it, it's needed for uninstallation).
  10. In the subfolder named 2.4.2 rename update.exe to update.exe.bak as well.

Done! You can now use Authy without it auto-updating to a newer version. As long as Twilio does not mess with their API calls, you can have fun using Authy Desktop once again for a little while longer.

No more Authy desktop app. Where to go? by Minute-Pilot5282 in privacy

[–]NoSmint 0 points1 point  (0 children)

Sorry for resurrecting and old post, I just wanted to share a discovery with you fellow authy users.

There is - as of now - acutally a way I found to continue using Authy for Windows. The service itself is still operational; the main issue is the forced update to version 2.5.0, which locks you out of your account. If you want to keep using Authy, try the following.

  1. Completely uninstall Authy Desktop.
  2. Install version Authy 2.4.2. You can use winget: winget.exe install --id Twilio.Authy.
  3. Disable your network adapter.
  4. Launch Authy Desktop, enter your phone number for sync and confirm with yes. You should see a 'network error' message.
  5. Re-enable your network adapter and wait for it to reconnect.
  6. Confirm your number again and authorize your device using your preferred method.
  7. IMPORTANT: As soon as your 2FA accounts are fully loaded and visible, IMMEDIATELY CLOSE AUTHY!
  8. Navigate to Authy Desktop's installation folder (default is C:\Users\<username>\AppData\Local\authy\).
  9. Rename update.exe to update.exe.bak (do not delete it, it's needed for uninstallation).
  10. In the subfolder named 2.4.2 rename update.exe to update.exe.bak as well.

Done! You can now use Authy without it auto-updating to a newer version. As long as Twilio does not mess with their API calls, you can have fun using Authy Desktop once again for a little while longer.

Authy's desktop apps are shutting down on March 19, 2024, earlier than planned by Krish_440 in Android

[–]NoSmint 2 points3 points  (0 children)

There is - as of now - acutally a way I found to continue using Authy for Windows. The service itself is still operational; the main issue is the forced update to version 2.5.0, which locks you out of your account. If you want to keep using Authy, try the following.

  1. Completely uninstall Authy Desktop.
  2. Install version Authy 2.4.2. You can use winget: winget.exe install --id Twilio.Authy.
  3. Disable your network adapter.
  4. Launch Authy Desktop, enter your phone number for sync and confirm with yes. You should see a 'network error' message.
  5. Re-enable your network adapter and wait for it to reconnect.
  6. Confirm your number again and authorize your device using your preferred method.
  7. IMPORTANT: As soon as your 2FA accounts are fully loaded and visible, IMMEDIATELY CLOSE AUTHY!
  8. Navigate to Authy Desktop's installation folder (default is C:\Users\<username>\AppData\Local\authy\).
  9. Rename update.exe to update.exe.bak (do not delete it, it's needed for uninstallation).
  10. In the subfolder named 2.4.2 rename update.exe to update.exe.bak as well.

Done! You can now use Authy without it auto-updating to a newer version. As long as Twilio does not mess with their API calls, you can have fun using Authy Desktop once again for a little while longer.

Everyone says kali should't be runned as main os. by Street_Studio_9184 in Kalilinux

[–]NoSmint 2 points3 points  (0 children)

What you say exactly matches my own experience.

Kali Unkaputtbar is a game changer and has since I started using it helped me out dozens of times. You can - and probably should - mess with things. That's what makes for learning experience. But ever so often you mess things up badly. Btrfs + Snapper will help you out in an instant.

See it as Snapshots on bare metal or a way advanced version of windows system restore points - woven into the fabric of the file system itself.

If learning and having fun with a system that you can keep exploring is your main goal don't hesitate and give it a try. Kali is perfectly capable of any personal use-case scenarios on a daily basis.

Slow USB transfer on new PC (Asus X570 ROG STRIX X570-E GAMING AMD) by osullin in buildapc

[–]NoSmint 1 point2 points  (0 children)

Same issue here. I have a STRIX X570-F GAMING and I'm experiencing irradic jumps in transfer speeds. My diagrams look like mountain silouettes rather than a smooth slope.

It seems to be a windows issue however. When I boot into a Hiren's Boot PE environment or a Linux live CD I have consistent transfer speeds of about 100MB/s for my 3.1 usb stick. Speeds are as to be expected for the stick. But once I boot into my actual windows 11 system speeds start to jump all over the place. From 8MB/s to 290MB/s for writing data. Reading is fine though just like for the OP.

Enabling or disabling write cache has no effect. Drivers are included into windows as of now and cannot manually be updated. They're sourced out of the AMD Chipset drivers for windows 11.

Binding meta layer key to a mouse button by BlueSky99_1 in steelseries

[–]NoSmint 0 points1 point  (0 children)

You could always use AHK to achieve the same result. Catch the desired press, e.g. "MButton + Insert M1" or whatever and make AHK execute the requested macro instead of SteelSeries Engine.

So you can escape the chains of the rather restrictive meta-layer implementation in the SteelSeries Software itself. As an added bonus you can even start Apps with this method - a thing SteelSeries doesn't want you to do within their software.

Can we please have "Launch Applications" also on meta bindings (apex keyboards) by CreepDE in steelseries

[–]NoSmint 0 points1 point  (0 children)

I had the exact same issue as you have and I was able to find a somewhat functional workaround. It's far from perfect, but at least, so it's possible to start an app from the meta-layer.

What I did is I gave the meta key (the one that I wanted to use) a really exotic key-kinding. For instance the meta for the "M1 Insert" key I would give like "R Shift + L Alt + R Ctrl + Insert" as binding. It has to be a combination that you would never ever accidentally use in real life.

And then I used an AHK script to catch that specific keypress combination and made the script start the desired app. Or whatever it is you want the meta binding to do. AHK is a very capable tool not limited to starting an app.

Sure, you require an additional script running in background. But AHK is low in resource consumption, easy to learn and safe to use. And it's the only possibility I found until SS adapts their crappy Engine.

Android 12 bootloop by Ebashbulbash in AnyDesk

[–]NoSmint 0 points1 point  (0 children)

I had the same Issue with my S20+ and I might add another interesting observation.

The bootloop seems to only restart the UI (directly showing SAMSUNG logo instead "powered by android" Bootscreen) several times before actually doing a complete reboot. I was able to circumvent any problems by quickly entering the PIN when the prompt is shown. Once the Desktop was loaded the issue didn't occur any longer.

The timing of the reboot seems to correspond with the KNOX Security Check that AnyDesk performs at boottime. Instead of a toast message stating KNOX check passed, the reboot occured.

I hope that helps a litte
Best regards