[-] hogleg@forum.guncadindex.com 2 points 3 weeks ago

I wanted to make sure I updated this for anyone following down the road. I didn't realize what the problem was until I printed the actual R2 Galileo barrel nut and compared; the hole for the barrel on the R2 was much wider than the Decimator v3. I dropped a 23.2mm negative cylinder into the center of the Dv3 barrel nut and it resolved the problem. I've not got any experience with printed barrels to compare, but I imagine their OD is narrower than the widest portion of the factory barrels I was working with.

[-] hogleg@forum.guncadindex.com 2 points 1 month ago

You're too kind! I didn't think I would ever actually need any of them, to be honest. Was preparing for a "grid is down" scenario, not a memory-hole situation.

It's unfortunate that we're entering a period where knowledge is actively suppressed.

So much the better than you've got this forum for us. I don't know when they new subreddits are going to catch the banhammer, but I sure would like to see people migrate off a corporate platform. No freedom in a company town.

[-] hogleg@forum.guncadindex.com 3 points 1 month ago

Beautiful! Not only do we have the knowledge saved, but with any luck, we'll catch some of those people who would otherwise wander off into the void.

1

I have been incapable of finishing a decimator build with an OEM barrel; 2 different OEM barrels as a matter of fact.

I've reprinted the upper twice (once because I wasn't sure if I just really messed up the print, once for stripping barrel nut threads) and I've reprinted the barrel nut 3-4 times at this point.

I started this build just before fosscad was nuked, and since the Ark is back up (https://forum.guncadindex.com/c/ark@fosscad.io), I was able to see that there are threads where others have had this issue.

Has anyone overcome this issue personally? The build looks great and I love the AR fcg but I'm hitting a wall here. Should I just drill and pin the barrel nut with a couple of set screws?

[-] hogleg@forum.guncadindex.com 1 points 1 month ago

Submissions are in git, but comments still have awhile to cook. Wanted to stay up for them tonight but I don't think they'll be done til morning. I'll check in when they're uploaded.

[-] hogleg@forum.guncadindex.com 1 points 1 month ago

Oh, that's awesome, thanks! Grey Summit Gear has actually got a lot of this built out; I'm working on getting the last couple years of data ready and then he can finish rebuilding the fosscad sub at https://forum.guncadindex.com/c/ark@fosscad.io

[-] hogleg@forum.guncadindex.com 2 points 1 month ago

Just a heads up; I was able to finish pulling down the archives, but it's going to take awhile to parse; wasn't expecting to need this much storage touching my compute lol. I'm hoping I can have those ready for upload tonight or early tomorrow AM.

[-] hogleg@forum.guncadindex.com 1 points 1 month ago

I just restocked but I'll definitely use this link next time.

[-] hogleg@forum.guncadindex.com 3 points 1 month ago

Hey, if you hadn't built this platform for us, it wouldn't be happening. Seeing a bit of the old internet come together really warms my cold, dead heart.

[-] hogleg@forum.guncadindex.com 2 points 1 month ago

Amen to that!

Looks like the download speed dipped a bit while I was out; around halfway through now. So another 12 hours or so before the torrents are done, sooner if it picks back up, then I'll need to parse.

I'll ding you as soon as I've got the new zst's up.

And thank you! Would have taken me a week to put that scripting together.

Go team venture.

[-] hogleg@forum.guncadindex.com 1 points 1 month ago

Sorry I missed this earlier! Thanks so much!

[-] hogleg@forum.guncadindex.com 1 points 1 month ago* (last edited 1 month ago)

Had to rearrange some things, but I'm pulling data from end of 2022 through 2024. It's a chonker. This is everything, so will need to parse through and find anything id'd as fosscad. Not sure how long it would take to iterate through all of that; it's over 1TB.

I'll be back this evening to update progress; download speed is pretty decent so if no big changes, should have the raw files tonight.

Edit Happy surprise; it's everything from 2023 to 06/2025. So losing the last handful of months of data (unless more gets added later). Still a pretty huge win.

Thanks to Grey Summit Gear for kicking the shit out of this, and the folks who pulled all these dumps!

[-] hogleg@forum.guncadindex.com 1 points 1 month ago

Oh, that's awesome. If you've got a bot that can already parse and push to fosscad.io, we should definitely be able to tweak that. I'm not active on discord (any social media really), but I imagine that's the place to organize an effort like this. If there is an alternative that others prefer (I've heard about matrix and element), I'm open to suggestion.

I've been fighting the flu the last couple of days, but on the upswing now. Dunno how much I'll be able to dig in today, but I'll get a github set up; I can dump the zst's there and some psuedocode and notes. If I can see what your bot is ingesting, I can try to match output from the zst's to it.

I think there will be a bit of work marrying comments to submissions; they're split up into two separate archives. Since the pictures are time sensitive (potentially), maybe the move is trying to focus on looping through the submissions and grabbing the pics from their urls, then rebuilding after the fact.

I've got plenty of local storage for pics or if we can dump straight to lemmy, that would be great. I'm completely ignorant to this platform as far as rate-limiting, storage, any of that fun stuff. I don't know how big a whole subreddit will end up being, but I imagine it's not inconsequential.

4

Apologies if crossposting is against the rules; I'm not entirely sure where the lines are drawn here yet.

I posted this in lemmy.fosscad (fosscad@lemmy?), but realize that may not be the most active venue.

I grabbed archives of fosscad and took a look at the contents of the zst's. I think I could probably rebuild the contents of the subreddit in some manner or another; the question is scale and hosting. How would we make the posts easily searchable, where would they live, what endpoint can we upload hundreds of thousands of comments into in a reasonable time frame... all that fun stuff.

The archives don't contain pictures, but contain links to the pictures and the ones I've checked are currently still live (meaning the pics are still hosted on reddit). Dunno how long that will remain the case.

I have no idea what the size of the archives would be with pics downloaded; gigs, a TB, no clue. I'm posting this to gauge public interest and I haven't done much preliminary work (oh, these are json. Yep, dictionaries work. Wingo.)

Is there any interest in making this more publicly available? I've run into an issue with a particular build and I'll be diving through the archives to fix it for my self. It seems like a shame that all this information would be inaccessible to everyone who isn't able or interested in trawling through their own local archives.

I'm not a programmer by trade, but work in an adjacent space. I can plink along on this if other people are interested (and if anyone is interested enough to help pitch in, even better).

10

I grabbed archives of fosscad and took a look at the contents of the zst's. I think I could probably rebuild the contents of the subreddit in some manner or another; the question is scale and hosting. How would we make the posts easily searchable, where would they live, what endpoint can we upload hundreds of thousands of comments into in a reasonable time frame... all that fun stuff.

The archives don't contain pictures, but contain links to the pictures and the ones I've checked are currently still live (meaning the pics are still hosted on reddit). Dunno how long that will remain the case.

I have no idea what the size of the archives would be with pics downloaded; gigs, a TB, no clue. I'm posting this to gauge public interest and I haven't done much preliminary work (oh, these are json. Yep, dictionaries work. Wingo.)

Is there any interest in making this more publicly available? I've run into an issue with a particular build and I'll be diving through the archives to fix it for my self. It seems like a shame that all this information would be inaccessible to everyone who isn't able or interested in trawling through their own local archives.

I'm not a programmer by trade, but work in an adjacent space. I can plink along on this if other people are interested (and if anyone is interested enough to help pitch in, even better).

view more: next ›

hogleg

joined 1 month ago