[-] Penguincoder@beehaw.org 5 points 4 days ago

That must be a huge battery killer.

21
submitted 1 week ago by Penguincoder@beehaw.org to c/chat@beehaw.org
1
submitted 1 month ago by Penguincoder@beehaw.org to c/lua@sopuli.xyz

A highly evasive, custom malware loader that had completely bypassed the modern AV/EDR ecosystem. Its use of a legitimate signed binary, a Lua‑based orchestrator, and advanced anti‑detection techniques

3
submitted 1 month ago by Penguincoder@beehaw.org to c/lua@sopuli.xyz

This paper presents an empirical study of Lua's runtime performance and energy efficiency across 25 official interpreter versions and just-in-time (JIT) compilers. Using a comprehensive benchmark suite, we measure execution time and energy consumption to analyze Lua's evolution, the impact of JIT compilation, and comparisons with other languages. Results show that all LuaJIT compilers significantly outperform standard Lua interpreters.

3
submitted 1 month ago by Penguincoder@beehaw.org to c/music@beehaw.org
19
submitted 2 months ago by Penguincoder@beehaw.org to c/chat@beehaw.org
1
New Lua-based malware “LucidRook” (blog.talosintelligence.com)
submitted 3 months ago by Penguincoder@beehaw.org to c/lua@sopuli.xyz
4
submitted 4 months ago by Penguincoder@beehaw.org to c/music@beehaw.org
19
submitted 5 months ago by Penguincoder@beehaw.org to c/chat@beehaw.org

Let's hear your wins and whines!

19
submitted 5 months ago* (last edited 5 months ago) by Penguincoder@beehaw.org to c/chat@beehaw.org

Pinch-hitting for Alyaza; no book club this week but how about a selection of music?

Amaranth

4
submitted 5 months ago by Penguincoder@beehaw.org to c/music@beehaw.org
15

A full-featured web browser for the terminal using Chromium (CEF) and libsixel for graphics rendering.

4
Lua 5.5 Released (www.lua.org)
submitted 6 months ago by Penguincoder@beehaw.org to c/lua@sopuli.xyz

Newest release! So many programs are on 5.1 still, but 5.5 brings some awesome changes.

[-] Penguincoder@beehaw.org 74 points 2 years ago

Go-dAmn Sachs is wrong often, but in this I think they're on point. Learned from the Crypto insanity.

[-] Penguincoder@beehaw.org 75 points 2 years ago* (last edited 2 years ago)

And so enshrined is that final nail in the enshitiffication coffin that was Reddit. I give it 3mo before Spez leaves Reddit to focus on [whatever].

[-] Penguincoder@beehaw.org 75 points 2 years ago

Well that's certainly a war crime. Wonder if the rest of the world will look the other way on this too.

[-] Penguincoder@beehaw.org 62 points 2 years ago

I think that question is definitely a worthy cause, but entirely misplaced. As others said, they donated to Beehaw not to some other foundation or charity. Rainy day fund is better than an oh shit, we're broke moment. I am extremely grateful to those who have and continue to donate towards Beehaw's Cause. We need to make sure that money is used, when needed, as expected.

Let it ride.

[-] Penguincoder@beehaw.org 50 points 2 years ago

Good to see them working on the important issues affecting Android auto.

[-] Penguincoder@beehaw.org 235 points 2 years ago

Hey man why you talking bout me....

J/K. Thank you for the kind words. I really am happy to be able to help out here for a lot of reasons. I understand the risk, heavily, but I appreciate the trust you and the other admins have placed in me. I hoped I have shown it to be a correct decision. I want to do my best for Beehaw and what is the best. I won't say everything I do is right or the correct thing, but I normally have a reason for it.

Thank you kindly; genuinely happy to help and want to keep doing so.

[-] Penguincoder@beehaw.org 48 points 3 years ago

We were not hacked. The site was taken down preemptively for security measures. Are we ok? Yet to be determined fully.

Incident response on the available systems and data, show attempted XSS comments sourced from federated instances; none on Beehaw itself. Those were deleted from our Beehaw database. Additional security measures put in place to try and mitigate XSS and other Web based exploits. Changed the Content-Security-Policy to be more strict (might break some apps). Secrets for tokens and salting passwords were changed on the backend. You shouldn't need to change your password, but it can't hurt at this point.

If you're unable to login on Firefox:

* Open Beehaw website, tools -> more tools -> web developer tools

* Delete EVERYTHING for cache, cookies, indexed db, local storage, session storage

* Ctrl+F5 the page and try to login again.
[-] Penguincoder@beehaw.org 59 points 3 years ago

Absolutely will cause a lot more spam to go through. But why is that the custom written moderators tool/bot fault? Why isn't Reddit the company doing more to stop or combat spam/bots? Why keep doing their job for them, for free?? If it's so damn useful (and BotDefense is), then Reddit should be doing it, or I don't know pay for that service?!

[-] Penguincoder@beehaw.org 82 points 3 years ago* (last edited 3 years ago)

WOW.

I can't speak for the other admins; but this part:

Beehaw admins look out for us by cutting off instances

Isn't really a matter of us looking out for anyone else, except Beehaw really. It's us not wanting to deal with that crap and what it involves, either. Literally be nice. They weren't being nice, they don't fit the ethos here.

view more: next ›

Penguincoder

0 post score
0 comment score
joined 4 years ago
MODERATOR OF