2025-01-20T19:19:47.355Z
test
2025-01-20T19:40:21.357Z
https://forums.tomshardware.com/threads/android-not-connecting-via-usb-3-0-but-usb-2-working-fine.3155237/

"Iv got 2 LG devices the G5 and G6 both will not connect to my PC via USB 3.0 I plug them in and they just charge no option for USB on the phone and not showing up on my PC at all not even in device manager[.]
But if I plug the phones in to a USB 2 port it will work fine every time"

classic. niche issue thread that got closed as "solved" due to inactivity. this is an issue for me btw.
2025-01-22T23:50:40.726Z
gaming
2025-01-24T02:44:31.387Z
i think i have a good intuition for taking a close look at things, poking around and dissecting, then spotting things and saying "this looks important" or "this looks interesting"

my weakness is that i never have enough knowledge of the subject (like any specific assembly language, win32 APIs, C# in general, etc.) but my strength is in being able to loosely connect the dots despite that lack of knowledge
2025-01-28T20:50:00.024Z
random potential project idea of the day:
i wonder what sort of hacks it takes to get Steam fully (or almost fully) working on Windows 7 and Windows 8 these days.

i'm almost certain that you could get any installed game to run, without needing the main Steam program fully 100% working. maybe via certain trickery using an older version of Steam (or the Steam DLL in the game files). or maybe by using one of those Steam DLL emulators / replacements that people use to bypass Steam's regular DRM that a lot of games use.

(note: plenty of games don't use Steam's DRM at all. for example, the Steam releases of main-series touhou games, allegedly, last i heard. literally just run the EXE on any computer, no need to be logged-in to Steam.)

as much as i respect it, doing so for the purpose of bypassing DRM is a different question that i personally don't care about. i'd be more interested in getting the main Steam client application (and Steam DLL, if necessary) working as well as possible on Win 7 / 8 / 8.1. and reverse engineering the client, perhaps patching it to bring it up to date with the still-supported Windows 10/11 version, maybe patching it to use Supermium (https://github.com/win32ss/supermium) instead of Chromium, etc.

as always, a lot easier said than done. i might never decide to work on that, which is common. just a random spitball idea i could theoretically do.
2025-02-08T05:52:42.422Z
I plan on doing a little bit of datamining of Pokemon TCG Pocket
2025-02-08T05:58:33.200Z
(both the android and the iOS version)
2025-02-08T06:03:36.289Z
I'm not gonna do an exhaustive analysis, I'm mainly just interested in trying to dump some textures
2025-02-08T18:45:45.864Z

y'know, there's something to be said about the way Windows does so much baseless fearmongering that it actually backfires and trains its users to ignore *real* security concerns.
2025-02-08T18:53:46.486Z
*security concerns as well as other concerns. obviously that image isn't related to cybersecurity, it's a matter of potential data corruption, but it's the same principle. Every time I remove a USB drive without going into the badly designed UI to click "Eject", the "dirty" flag of the drive's filesystem is set, and Windows will display this notification when the drive is next plugged in. But 99.98% of the time, the data on the drive is literally completely fine (except perhaps if you were using ExFat, because that filesystem sucks balls and is super prone to mass data corruption...). So I completely ignore that notification every time it pops up, and sometimes I even make fun of it. 10 years of false flags of "WARNING!! WARNING!! DRIVE CORRUPTION!! CLICK HERE TO SCAN NOW!!" have trained me to completely ignore such warnings. This is an example of a broader issue with software (and UI) design.
2025-02-08T20:53:36.941Z
in the next hour i'll hopefully fuckin *finally* get around to dumping my friend's CD-ROM/DVD-ROM(?) copy of Microsoft Office FrontPage 2003 Academic Edition
2025-02-08T20:56:11.129Z
*it is in fact a CD-ROM
2025-04-15T00:50:01.849Z
had an issue with the Discord app on Linux, here's a text dump of my bug report:
2025-04-15T00:51:15.015Z
# Description

For the record, I've already figured out a workaround and the Discord app is now working again on my laptop. So I don't need help, I'm just reporting this bug.

(Read the Steps to Reproduce and Result sections...)

But that's just the way the issue *manifests*... That's probably because of a weird version number mismatch, where my version 0.0.90 Discord app wants me to update to a version that calls itself 0.0.89 but the .deb package installer GUI doesn't want to let the user downgrade a package.

The workaround I used is as follows:
1. The most recent update, I downloaded and renamed the file "discord-0.0.89 (2).deb" (because I still have the past few Discord app update .deb files on disk.)
2. In a terminal window, I ran ```sudo dpkg -i 'discord-0.0.89 (2).deb'``` and the package downgraded successfully. (See image attachment 3.)
3. I launch the Discord app, and it does the usual post-update process ("Downloading update 1 of 6" and "Installing update 1 of 6" etc.) and then seems to work perfectly without a hitch.

Additionally, refer to image attachment 4 to see the approximate release dates of the previous few Discord app versions (I use Discord on my laptop almost every day).

I don't regularly check my email, so I've uploaded a .tar.gz file containing the self-contained .deb packages of 0.0.88, 0.0.89. 0.0.90, and 0.0.89(2) on Google Drive. I've done this in advance in case anyone on the dev or support teams might find it useful. The files are available here: https://drive.google.com/file/d/1HDyjhXn8TEVx0XCP7UEg1OHXhMX0-K7V/view?usp=sharing

Pre-workaround Discord app 0.0.90 version info:
[unknown] (can't get into the Discord app proper to see it...)
Post-workaround Discord app 0.0.89 version info:
stable 389335 (8ebfee0) Host 0.0.89 x64 Build Override: N/A Linux 64-bit (6.8.0-57-generic)


# Steps to Reproduce

Using Linux Mint Xfce version 22(?) (based on Ubuntu)

Had previously installed the following updates as they released:
- discord-0.0.88.deb
- discord-0.0.89.deb
- discord-0.0.90.deb

Had version 0.0.90 installed at the time of the issue occuring.

Launch the Discord app, see the common "new update is available" message. (See image attachment 1.)

Click the button which sends me to https://discord.com/api/download/stable?platform=linux&format=deb as usual.

Using Firefox (or other web browser) save the file, then double-click it to open a .deb package installer GUI...


# Expected Result

Usually, the .deb package installer GUI shows a green button that says "Install Package", and I click that to install the update, input my laptop's root password, and everything goes smoothly as one would expect.


# Actual Result

Instead, in the .deb package installer GUI... That button which would usually be green is instead greyed-out and unclickable, and there's a red banner that reads "Error: A later version is already installed". (See image attachment 2.)


# Discord Client Info

[refer to the Description section]


# Attachments
...