AusatKeyboardPremi

joined 1 year ago
[–] AusatKeyboardPremi@lemmy.world 3 points 3 days ago (1 children)

“… as of August 2024” is literally front and centre in the image.

[–] AusatKeyboardPremi@lemmy.world 20 points 6 days ago* (last edited 6 days ago) (7 children)

I completed a marathon of all AC games last year, from the very first title, all the way up to Valhalla.

The games serves as a good reflection of Ubisoft over the years. The issues in the series and Ubisoft’s approach are amplified when one plays the games back to back.

The first title from 2007, albeit with clunky movements, had a promising story which was only elevated by its sequels.

The titles post-Revelations experimented a lot but the series settled at Origins, which was the last playable game, all aspects considered.

Valhalla is the worst of the series. It offers nothing new in terms of gameplay or story. It is just more of the same. Mundane and boring. It kept painfully reminding me that I am playing a video game.

Yet, I firmly believe that Shadows will be a lot worse with its live service mechanics.

A sidebar on AC 2007I would be remiss if I did not mention that nostalgia might be compensating for some of the game’s flaws. I still remember reading the full/multi page spreads about the game in the local computer magazines.

[–] AusatKeyboardPremi@lemmy.world 2 points 2 weeks ago* (last edited 2 weeks ago)

Thank you for introducing me to KOReader and Kindle jailbreaking.

Fortunately, the Kindle Paperwhite I use is no longer supported, and is compatible with few of the jailbreaks out there.

A good rabbit hole to dive into over the weekend.

I have experienced this myself.

My main machine at home - a M2 Pro MacBook with 32GB RAM - effortlessly runs whatever I throw at it. It completes heavy tasks in reasonable time such as Xcode builds and running local LLMs.

Work issued machine - an Intel MacBook Pro with 16GB RAM - struggles with Firefox and Slack. However, development takes place on a remote server via terminal, so I do not notice anything beyond the input latency.

A secondary machine at home - an HP 15 laptop from 2013 with an A8 APU and 8GB RAM (4GB OOTB) - feels sluggish at times with Linux Mint, but suffices for the occasional task of checking emails and web browsing by family.

A journaling and writing machine - a ThinkPad T43 from 2005 maxed out with 2GB RAM and Pentium M - runs Emacs snappily on FreeBSD.

There are a few older machines with acceptable usability that don't get taken out much, except for the infrequent bout of vintage gaming

[–] AusatKeyboardPremi@lemmy.world 1 points 2 weeks ago* (last edited 2 weeks ago) (1 children)
[–] AusatKeyboardPremi@lemmy.world 21 points 3 weeks ago (4 children)

He uses a version of Emacs called MicroEmacs.

I recall seeing his MicroEmacs configuration a while back when I was exploring options to start using Emacs.

Something does seem fishy: the total number of votes this post has received (~450 at the time of writing this comment) is only about a third of the number of comments (~1.2k).

I guess people were really pent up about their pedantic tendencies.

 

cross-posted from: https://lemmy.world/post/18205906

I have an old ThinkPad T42 coming my way. I plan to use it alongside my daily driver mainly for reading, emacs, and retro gaming. I will be dual booting a lightweight flavour of Linux (TBD) and Windows 98 on it.

However, I am a bit concerned about its ability to handle today's internet, with all of its heavy websites.

I would love to hear from those of you who are still using old ThinkPads (or other vintage laptops) in 2024. How do you make it work? Do you use lightweight browsers, specific configurations, or lightweight websites to get around the limitations of older hardware?

Are there any specific tips or tricks you can share for getting the most out of an old ThinkPad on the modern web?

Looking forward to hearing about your experiences!

[–] AusatKeyboardPremi@lemmy.world 3 points 4 months ago (1 children)

Pardon me if I sounded dismissive. 1Blocker is good, and so is AdGuard.

I remember those being one of the first ones to do the job well, back when Apple launched content blockers. Wipr came much later, and I only recently switched to it (around late 2022).

[–] AusatKeyboardPremi@lemmy.world 3 points 4 months ago (1 children)

Joplin’s storage model made me stop using it.

Managing plain text notes should not be this convoluted.

[–] AusatKeyboardPremi@lemmy.world 1 points 4 months ago* (last edited 4 months ago)
  • Windows 95, 98, 2000, XP, 7 spanning a decade and a half.
  • Ubuntu 10.04 going up to the release where Unity became the default DE (11.04, I think). Came back to 10.04, as it was an LTS release.
  • Linux Mint Maya because of Cinnamon, and it was terrible.
  • Fedora 16 to 25 or 26.
  • Linux Mint 19

Been with Linux Mint ever since. It just works. LM19 was also around the time when I stepped into Apple’s walled garden with iOS and macOS.

[–] AusatKeyboardPremi@lemmy.world 3 points 4 months ago* (last edited 4 months ago) (3 children)

On Safari for iOS and macOS, I prefer Wipr instead of 1Blocker.

It’s lighter, easier to use, cheaper, scores more on d3ward’s ad-block test (but that may fluctuate).

E: added specific browser.

 

cross-posted from: https://lemmy.zip/post/14145658

[512Pixels] Logitech’s Mouse Software Now Includes ChatGPT Support, Adds Janky ‘ai_overlay_tmp’ Directory to Users’ Home Folders

 

cross-posted from: https://lemmy.world/post/15358589

Bloomberg - Apple Says No Major App Developers Accept New Outside Payments

According to Apple, only 38 developers have applied to add such links — out of roughly 65,000 that could.

 

According to Apple, only 38 developers have applied to add such links — out of roughly 65,000 that could.

 

HMD is betting that consumers are moving to more environmentally-conscious products and are placing an emphasis on repairability. HMD says the Pulse range is built to “Gen 1 repairability” and that users can pick up self-repair kits from iFixit. Repairs include changing the battery, but also swapping the screen.

 

After using Apple’s products exclusively for close to a decade, I have seen a pattern emerge with their software updates where every new update introduces a set of trivial regressions in the UX.

  1. Swipe to seek a video in iOS’ native player has stopped working since I updated to iOS 17. In fact, this paper cut is what prompted me to write this post. I believe it didn’t work on iOS 15 either but worked flawlessly on iOS 16.
  2. Across all of iOS 16 versions installed on my phone, long-pressing an item on screen (links, app icons, files, etc.) to show the contact menu and selecting an entry in the menu without listing the finger didn’t work. It did until iOS 15 and it does now in iOS 17.
  3. Spotlight in iOS 14 (and back in iOS 10 or 11, I don’t remember well) took slightly longer to load (and even stutter on iPadOS). I don’t find this issue anymore on the same devices that had this earlier.
  4. The magnifying bubble that popped up while moving the caret in a text field stopped working around iOS 14/15. It was reintroduced back in iOS 16.

Now, I understand that these regressions are unintentional unlike the botched System Preferences on macOS or the poor handling of Safari UI across iOS 15 and macOS 12.

I also understand that such regressions are bound to happen as no software is 100% QC-able, but it doesn’t mean one has to wait for an entire year to see these get fixed as is the case with the examples I have mentioned.

It could also be the case that these issues are localised to my devices, and that the yearly updates perhaps cleans the slate (the good ol’ reboot-machine-to-rid-error fix). Regardless, I have raised bug reports for all these and more, along with feature requests.

I would like to hear your experiences across major/minor software updates on Apple devices or services.

Also, let this serve as a PSA to file bug reports if you have the time and effort to spare, it helps the developers a lot (Apple or otherwise). Here is a comprehensive guide to report bugs for a variety of Apple’s offerings:

Bug Reporting: How and Why?

E: Through one of the deleted comments made on this post, I learned that the removal of the magnifying bubble while typing in iOS 13 was intentional.

view more: next ›