I had done a fair bit of reverse-engineering-jar-files in the pre-LLM era for various reasons. The biggest problem with decompiled java files was naming. The original variable names, class names etc were not retained and the decompiler would use some alphanumeric series. That'd make reading code very hard. Curious how the current LLMs are able to address this. Maybe it's able to figure out how the class, variable etc is used and name it accordingly. (All this is assuming the original code itself was readable because there are enough bad programmers)
I expect Java would be easy-mode for the AI, they already do quite well reconstructing C++ from ghidra output in my experience from when I wanted to know what damage formula some game was using.
As a reminder; your account has been shadow-banned, it looks like you got a little unlucky in 2016.
That makes sense. Java leaves metadata in compiled code to reconstruct better.
> your account has been shadow-banned, it looks like you got a little unlucky in 2016
I see. I wasn't aware. Thanks. I thought the two comments per day limit is for users with low karma. Anyway, I'm using that limit to push myself in being picky about posts to comment on and to improve the quality of comments.
Shadowbans are actually a bit more than that - your comments are invisible unless someone with a high karma threshold puts a little effort in to mark them as reasonable. People can't actually see most of your comments.
I'd recommend creating a new account. Or you could email the mods (I forget the email but it is publicly available somewhere) if the user name has sentimental value. In your case it is clear that a shadowban is inappropriate.
It amuses me how the low limit nature of Excel has affected the ecosystem around it. Apache POI, which is a popular library to operate on Excel files, has a weird 4GB limit [1] on uncompressed file size.
throw new IllegalArgumentException("Max entry size is bounded [0-4GB], but had " + maxEntrySize);
What makes you think this limitation is related to Excel? 4GiB is a very common limit due to it being the max size you can fit on a 32bit integer. It's the max file size on FAT32 as well for instance.
> Yandex officials also said they re-secured the compromised accounts and blocked what appeared to be unauthorized logins. They are now asking impacted account owners to change their passwords.
I’m curious how access was provided to these sold accounts. The password change implies the passwords were shared and that means plan text password were available to admins!?
I'm not sure why you were downvoted - I vouched for your comment to bring it back (in fact, looking at your comment history it looks like almost all of your comments are dead).
I think you're right though--it does seem like they must have sold the passwords themselves. It's interesting to think about how you would sell access to an account if you wanted to.
Depending on your level of access, I can think of many ways.
You can do a "takeout" of all data in the account and sell that. Or it can be anything that is requested, like a dump of all the private messages.
You can change the password of the account, possibly at a time like 3am at the user's local time so they're less likely to be using the account, then change it back at say 5am. This requires DB access.
You can find the user's session token/id if they're logged in somewhere and sell that.
All 3 ways make sense. The dump and session token ways look cleaner from Yandex employees’ perspective. Although, none of the three should require a password change for the compromised user account. At no point, users password or hash of the password gets shared.
> This increased transmission could be due to chance or founder effects—meaning one variant just happened to get somewhere before the other variants and then got “lucky”; it was early, rather than more transmissible. It could be due to changed behavior among people—quarantine fatigue, less masking—leading to more rapid spread. However, given the current evidence, along with the specifics of the mutation, it’s getting harder to assume that those other explanations are more likely than the simple proposition that this is truly a more transmissible variant.
There is a chance that the hyper growth of the mutated virus is not scalable.
I have seen this behaviour repeatedly. Having to many “task windows” makes it difficult to focus. Similar to having to many tasks in Asana or emails in my Inbox. Prioritisation is the only option to come out of this. Unfortunately, I haven’t found a way to tag priority with the “task windows”. And that’s the reason I daily browse through all windows and close the ones that are not urgent.
Hm, I haven't found this to be the case. This is probably in part because of my WM/OS setup; I use a tiling window manager and different workspaces for different contexts, so my fan-out factor is never that high in cases where it matters.
Branching is more of an art. With the kind of flexibility git provides, one can get lost in the convention to follow. I have found this useful For a small team working on app development -
Working on your intrinsic motivation needs - relatedness, autonomy, and competence - has always helped me when it comes to burnout, failures, and, in general, feeling of things not going your way. AFAIU, you probably have a good autonomy in terms of "how" you do the tech stuff as long as it works. Embrace your autonomy and have a plan for the other two.
