PenguinCoder @ Penguincoder @beehaw.org

Bit-breaker working in cybersecurity/IT. Only languages I know are English

---

Read more

Posts

81

Comments

503

Joined

3 yr. ago

Moderating

---

Serious question; would it help if some of us left beehaw?

No. As noted in the post, the largest aspect of issues are other users and content federating to Beehaw. Less users on Beehaw won't address that.

If there are moderation issues, wouldn’t it be easier to recruit more moderators?

No. The tools needed for successfully moderating Lemmy federated items, is severely lacking. The primary devs do not seem interested in making this area a priority either from their own efforts, or others submitting PRs for such. More moderators won't help when the ability to moderate isn't there.

The issue here isn't the front-end and can't be fixed with a new coat of wax.

You know what the various logs are, that's good to help out. So you have any crash dumps enabled? I think on Debian (what promox is based on), you have to install kdump tools and reboot. Then it should cause a the kernel to log a dump file you can read with crash if it's a kernel crash and not something else.

This is what I have in my . tmux.conf for SSH you can adapt

bind-key S command-prompt -p "ssh to:","port:" "new-window -n %1 'ssh %1 -p %2'"

That means when I press C-b, SHIFT S it asks what IP to connect to (type it in when it asks on the status bar of TMUX), press enter, the it asks the port to use.

What?

TMUX is life. Before, I was fighting screen to do what I needed. TMUX just does it and the customisation puts it way above. I can't imagine working on the command line without TMUX.

That's like; my life philosophy man.

Nah, I don't have patience or desire to.

Reductionist, Sunk Cost Fallacy, Choice-support bias, list goes on.

Most things it does are IO bound [...] so you’re really not benefiting from anything specific to Rust,

Preach.

I had a bunch of stuff typed here (probably too much), clicked a damn icon on this UI and POOF when my entire comment....

These are my opinions, probably not shared with others and surely not the end all be all to 'why not Rust?'

Rust is hard. Rust is slow to iterate with and compile. Here's a highlevel overview of the things you'd need to learn to effectively understand Rust code; not even speaking to learning enough of that to write it. Rust gets touted as secure, and it is more secure than other low level languages like C/C++. That does not make it invulnerable to exploits. It gives a false sense of security to developers who think My app can't be hacked, it's written in Rust!!. While Rust is better at memory management and protecting against run time errors related to memory issues, that doesn't make it 100% safe. That removes almost one class of potential exploits, not all of them, and can't protect the developer against other developer created issues. Rust code is still written by people. People still write insecure code even in Rust. Computers are dumb as hell; but fast. People are smart as hell, but SLOW. Combine the two and you get stupid things faster; not smarter things better.

• Rust development is hard, hard to learn, very hard to do right
• Rust is not suited for a web application. Would you tell someone to go write the web application and web page in C/C++? Nope. There's a reason for that. Not suited to it. Square peg, round hole
• There's always exploits being discovered. Rust handles some things better, but uhhh.. Go look at some Lemmy Rust code. Definitely still has vulnerabilities; Rust won't save you from yourself.

Something like Golang is much better choice for development of a web service that has sane API handling. By the time to add in more error handling, more type checking, more passing around of this function or that data, and more checking it on the sender and receiver side...etc. By the time you're writing Rust safely and correctly; it is much slower than what you may be lead to believe.

Go is primarily designed for speed of development (including compilation times), rather than speed of execution. Go programmers tend to value clear code over fast code. Why does a microsecond longer matter for a website? Maybe in some backend PLC land there's a damn good use for that performance. For a networked web application; it's a pointless metric. That is not going to be your bottleneck.

Rust is hard to understand just reading it let alone determine why it's doing something.

Rust

    
fn does_what(n: u64) -> bool {
    match n {
        0...1 => false,
        _ => !(2..n).any(|d| n % d == 0),
    }
}

  

Golang

    
func doesWhat(value int) bool {
    for i := 2; i <= int(math.Floor(float64(value)/2)); i++ {
        if value %i == 0 {
            return false
        }
    }
    return value > 1
}

  

Not talking about the functionality merits of the two, but in comparing the _code itself. One of those is much easier to determine what's going on and what it should be doing versus the other. I don't feel like fighting my code. Programming is a tool to help. If it takes more work to use the tool to achieve your goal, it's the wrong tool. Rust is the wrong tool for web development.

The problem with forking Lemmy is in starting from all the bad that is inherently there, and trying to make it better. That is way more work than starting fresh with more developers. IE, not using Rust for a web app and UI, better database queries from the start, better logging/functions from the start; not adding on bandaids.

A fork of Lemmy will have all of Lemmy's problems but now you're responsible for them. No thank you.

Happy to help out :) Web scraping is hard, good thing Lemmy gives an API. Hit me up on matrix if you're there @penguincoder:hive.beehaw.org or just PM.

Did you do this by hand ??? My dude.

🥂

I used to know a clever toast.
But now I cannot think it.
So fill your glass to anything.
And damn your souls, I’ll drink it.
-- Wallace Irwin

Thanks for letting us know. Unfortunately, Lemmy itself does not distinguish between a 404 and a 500 error, typically passing the 502 instead of the not found. Working on fixing that properly and also finding an acceptable workaround.

Oh Lord I don't want to think about that...

Between $500-$650 😜 all in.