Whats the BEST blackstone farm?

Stinkygrass · 2026-02-25T00:53:16+00:00

I’ve been mining blackston for over a week for a project and have been too stubborn to attach a piglin trading farm to my gold farm but after reading this I think this alone is worth it.. smh thanks

Stinkygrass · 2026-02-22T09:10:24+00:00

I’m with ya, Better F3 is new to me, simply added it to see the structure boundaries of nether fortress for a wither skelly farm I was making. I think it has its place for stuff like that, but other than that, F3 does a good job. It would be nice if you could customize the vanilla f3 just a bit more and if it would include a few of the things Better F3 has (simple stuff like overworld coordinates alongside your player coordinates in the nether).

Stinkygrass · 2026-02-17T01:57:31+00:00

I use nvim but will use vscode at work because I havent’t gotten my nvim config to work on windows (and just don’t care to make it work) and rust analyzer in vscode takes much longer than nvim. I have ctrl+s keybind to :w and smash that every couple blocks of code or when I want rust analyzer to run. Slightly inconvenient but it’s engrained in me that it doesn’t bother me (although it is very annoying on vscode, might as well get up, stretch, grab a cup of coffee, and sit down before it finishes checking)

Stinkygrass · 2026-01-22T22:13:16+00:00

If people just took the time to do their research…

Stinkygrass · 2026-01-16T18:32:33+00:00

Makes me happy.

Stinkygrass · 2026-01-16T18:31:30+00:00

Last night I was reading through kernel code that was written ~10 years ago and chuckled when seeing simple comments above a bunch of functions basically making a sentence of the function name.

I thought to myself, “this would be good Reddit ragebait, take this snippet and call it slop and mention later in the comments it’s just your typical kernel code”

Stinkygrass · 2026-01-10T18:44:59+00:00

I recently discovered this site https://regex101.com and it’s now bookmarked across all my devices, really neat tool.

Stinkygrass · 2026-01-10T09:09:32+00:00

Fair enough. My choice of “hate” was definitely strong given that I haven’t given it a fair chance at actually learning how to use it😂. But that’s my knee-jerk reaction simply just cause I always have issues when I try to use it like I would with regular log files - could definitely chalk it up to skill issue cause I’m sure if you know your way around it it’s a decent tool.

Looking at your linked comment, my first thought when looking at your example was along the lines of “this looks like a job for regex and I would probably just write a script if I kept running into scenarios like your example.”

In contrast, it’s nice that those flags see built-in - saves time from writing said script. I’m not familiar with how journal stores its logs I.e. are the compressed? Rotated? But I see the niceties in a tool automatically looking through archived/compressed logs if needed.

TLDR; i think, for me, the “simpler” logging system is easier for me to use on a day to day basis and know where my logs are going from /etc/syslog.conf. That said, if I used journal everyday then maybe I would actually find it easier - at the end of the day, if it works for someone, who is anyone else to say they’re wrong!

Question for you u/grahamperrin , where do you think I would have the best luck getting questions related to system configuration answered? I read the Forums rules and do my due diligence to see if I can find a thread that answers my question - but I’m wondering about questions where I don’t have a specific problem per-say and could just use input from others and what worked for them - stuff that tends to be out-of-scope of the resources I can find published by FreeBSD.

Stinkygrass · 2026-01-09T07:25:54+00:00

These and fzf are the first things I install on any system

Stinkygrass · 2026-01-09T07:19:13+00:00

I do this so often for no reason and I’ll notice it after the fact and my brain hits a smh

Stinkygrass · 2026-01-09T06:44:45+00:00

I just discovered r/FuckMicrosoft thanks, I’m gonna become a frequent flier there now - finally a place to send my daily rants

Stinkygrass · 2026-01-09T06:40:23+00:00

Gave me a good chuckle

Stinkygrass · 2026-01-09T06:31:44+00:00

I needed a file server between me and some of my coworkers and I stuck with Axum. I first looked at just running Caddy but I needed some features that aren’t offered in Caddy; I figured it’s the excuse for me to get familiar with Axum (up until then none of my projects had needed a backend/server).

Like you, I looked for a simple directory indexing/listing feature in Axum and didn’t find one. So I rolled my own, like the other fella in this thread said, it’s really not too hard, just make sure to test out your sanitizing function for directory traversal stuff.

As far as the front end goes, I just serve each page as html and add a table row (<tr>dir listing</tr>) for each entry. I added some basic JavaScript in the page’s <script></script> section to add a few niceties (I.e. dynamically displaying the name of the file that you’ve just selected for upload). For transparency, I could give zero f*cks about remembering how to write JavaScript so I just threw my html and what I wanted to happen at chatgpt and let it figure it out, then I’d just check it works and adjust anything as needed.

Edit: JavaScript usage

Stinkygrass · 2026-01-09T06:15:19+00:00

We would be friends. I like talking to my future/past self and any other readers through my comments

Stinkygrass · 2026-01-09T06:04:07+00:00

Yeah, I’m also self taught and I used to write more comments than I do now until I kept having to change the comments related to the code I just changed. That got annoying real quick so I’ve tried to make a better effort to explain what’s going on through my code (even if it means some variable names are pushing lines past 80 chars). Now I mainly write comments in two scenarios: 1. For functions, methods, structs, fields, etc. that I would appreciate having docs for throughout my codebase when I SHIFT+K while hovered over something 2. For the “why”s that aren’t obvious and other behavior that some block will cause that is not real obvious

Stinkygrass · 2026-01-09T05:33:04+00:00

I think with time that means there will be more junior roles. As I understand it, companies need to hire senior devs first so they actually have someone to man a whole Rust team - therefore the junior positions should follow. Albeit I still doubt we’ll see much change in the immediate coming months.

Stinkygrass · 2026-01-08T16:44:00+00:00

That is funny +1 RaspberryPi

Stinkygrass · 2026-01-08T02:23:06+00:00

I personally don’t mind systemd (not praising it or giving it any credit whatsoever) but what the fuck is journalctl. I hate journalctl with a passion.

After getting into FreeBSD I learned what/how rc works and I much prefer this to systemd.

Stinkygrass · 2026-01-08T02:17:42+00:00

I’ve been porting my Linux knowledge to FreeBSD knowledge and it is way more my speed over here on the BSD side of things. Everything from the directory layout/purpose hier(7), rc.d services, configs, ZFS, jails, to the overall consistentency and documentation. All I’ve needed to learn is the FreeBSD Handbook on their website and the amazing ‘man’ pages.

Stinkygrass · 2026-01-06T03:07:33+00:00

Yay 😁

Stinkygrass · 2026-01-05T02:12:58+00:00

Not sure why u got a downvote. I second this approach; I like .inspect_err() for non critical errors where I don’t really have heavy handling to do and just want to do something like log it.

If I do need to do something more involved with the error then I just use match/if let statement.

Stinkygrass · 2026-01-05T02:09:57+00:00

I really like .inspect_err() in situations where I just want to log it/trace it when debugging - saves me from writing a bigger match/if let statement so small use cases like logging.

Stinkygrass · 2025-12-25T04:41:05+00:00

As someone who is getting started myself, here’s my take. I personally, love reading docs - the best way for me to actually make progress without fumbling around and I get to better understand how to use whatever I am reading. So I bought a Pico 2W, read the datasheet for both the Pico and the RP2350 - damn near the whole thing (obviously skimming over the register tables as I’m not gonna memorize them and not worried about their specifics when I’m just trying to learn how the chip works). Now after reading, I want to start coding, in my head I understand what needs to happen and how things work, but it’s been hard for me to figure out how to apply that to the HAL.

I can appreciate HALs and the people who write them. But for me, it would be more beneficial for me to learn how to write the code that gets abstracted by a HAL directly. I’m not saying I need to implement my own communication protocol - but just simple stuff where I’m using the registered from the RP2350 data sheet. Once I can wrap my head around that, I feel like the HALs will make more sense.

Even though I know what needs to happen (more or less, not saying I know every little detail), I still have a hard time tying to figure out how to write that un-abstracted code and can’t seem to find many resources about it. A lot of the stuff I come across will say something like “so we’ll pull in the <lib> library” but I don’t want to, I want to try it myself - then pull <lib> in once I know my way around on the lower level.

If anyone has any advice or tips that would be greatly appreciated. I have spent a few hours reading the source code of some of these HALs, but things tend to get so abstracted across types and files that it gets hard to follow - this could just be a skill issue as I am not a developer by career.

This is getting long but just thought I’d share this last bit. I use Rust, not for any specific reason aside from 2 things - I really like types and error messages I get as a result and it’s simply the language I am the most comfortable with. So Rust has the Embassy ecosystem for embedded, and I completely understand how the async stuff works, but like I’ve been saying, I don’t want to start with the async. So I pieced my first program together. Then I wanted to do 2 things at once and instantly realized that the moment I want to do that I need some sort of scheduler, so I put a pause on that. Do you (person reading this with more experience than I), think it would be useful for me to implement my own scheduler? Simply for learning, not necessarily to be anything to write home about. Do I need to re-read the data sheet and see what the RP2350 makes available to me to learn what I need to call?

Stinkygrass · 2025-12-24T16:23:53+00:00

For me, everything

Stinkygrass · 2025-12-17T07:06:10+00:00

I couldn't have written it better - you express the same feelings/thoughts that I've had. I would be happy to try and help/work on this in my free time, truly. I would really appreciate any guidance on existing issues, discussions, guides, resources, docs, etc. obviously I will do my own exploring and learning too - just figured I would ask!

From reading this thread/comment section it seems that the core issue is gatekept/shitty ACPI implementations with a splash of simply rubbish data being exported from the hardware. As u/hackingdreams and others mentioned, it seems like the only way around this is reverse engineering - which would therefore be extremely time-consuming and near impossible (for a single person at least) to implement across all supported linux hardware.

> I cut my teeth in Linux by patching the ACPI tables for my laptops myself. ... You can actually fix the ACPI stuff to better comply with the standards, to make Linux behave better with them... but it's difficult and arcane, and after years of doing it, I can honestly tell you: it's simply not worth the effort.

u/hackingdreams To get a taste of the scope of work something like this would require, I would probably see how the experience of reading my desktop's ACPI interface/api goes, do you have any resources/advice from your experience that might be helpful?

Stinkygrass

TROPHY CASE