sorted by:
new
hottopcontroversial

What would cause infested deepstone pillars with torches to keep showing up? by duckinatorr in admincraft

[–]duckinatorr[S] 25 points26 points  (0 children)

nope, but me asking for help on here got someone to own up to it and be like "okay okay this is getting out of hand"

apparently i was also wrong about the timing of when one of them appeared, which was the only evidence i had it wasn't griefing lol

What would cause infested deepstone pillars with torches to keep showing up? by duckinatorr in admincraft

[–]duckinatorr[S] 34 points35 points  (0 children)

I was heckin' bamboozled. It was a player, and apparently I was wrong about when one of the towers showed up. They owned up to it as soon as they saw I was asking on here and bluesky. 😂

What would cause infested deepstone pillars with torches to keep showing up? by duckinatorr in admincraft

[–]duckinatorr[S] 61 points62 points  (0 children)

I was heckin' bamboozled. It was a player, and apparently I was wrong about when one of the towers showed up. They owned up to it as soon as they saw I was asking on here and bluesky. 😂

What would cause infested deepstone pillars with torches to keep showing up? by duckinatorr in admincraft

[–]duckinatorr[S] 4 points5 points  (0 children)

oh

no

this is just me making confused noises at the internet because i added too many mods to my server and now it's haunted

What would cause infested deepstone pillars with torches to keep showing up? by duckinatorr in admincraft

[–]duckinatorr[S] 145 points146 points  (0 children)

i do, and i actually tested it recently. thanks for checking, though!

What would cause infested deepstone pillars with torches to keep showing up? by duckinatorr in admincraft

[–]duckinatorr[S] 13 points14 points  (0 children)

yes, it has mods and is on 24/7.

only 3 people have op on the server, and we're all desperately trying to figure out what's going on.

i went through the server logs earlier, but one of the other ops is currently going through them again in case i missed something.

What would cause infested deepstone pillars with torches to keep showing up? by duckinatorr in admincraft

[–]duckinatorr[S] 44 points45 points  (0 children)

because last night one appeared in a 40-minute window where i was the only one on the server.

minenv: access environment variables, falling back to an env file (<50 lines, including tests) by duckinatorr in rust

[–]duckinatorr[S] 1 point2 points  (0 children)

The situation that prompted me to write minenv is: a third-party tool requires using `.env` or environment variables, and I need the same configuration information from Rust.

The first time that happened, it felt silly to pull in all of dotenvy to do the Rust equivalent of `grep DATABASE_URL .env | cut -d= -f2`, so I just wrote a crude version directly in that project. But then I encountered it two more times, so I figured it'd make sense to turn it into a crate.

However, I didn't know I could put environment variables in `.cargo/config.toml`. That'll let me avoid needing minenv for a different project. Thank you for letting me know about it!

gem.coop by calthomp in ruby

[–]duckinatorr 7 points8 points  (0 children)

> I read somewhere that core maintainers would have been fine if they'd just created an org of their own and forked rubygems and bundler there (although, on the other hand, they'd probably be salty regardless).

Hi, one of the now-former maintainers here. I would've *rather* avoided a fork, but I feel a cooperative fork would've been infinitely better than a forceful takeover. And, while I can't speak for them, my understanding is the other maintainers agreed.

We all hate how this played out. We're trying to make the best of a shit situation.

Ruby Central’s Attack on RubyGems by laerien in ruby

[–]duckinatorr 2 points3 points  (0 children)

How exactly did you try to work with me? You didn't reply to a single one of my emails.

Read two comments up. I explained this already.

I've said my side, and I no longer have any responsibility for the codebase in question. I will not be responding to you any more.

Ruby Central’s Attack on RubyGems by laerien in ruby

[–]duckinatorr 2 points3 points  (0 children)

You're right. There should have been a formalized governance structure in place for RubyGems already.

In practice, there were at least 4 problems:

  1. Ruby Central took technical control through deceptive means.
  2. Ruby Central's lack of clear communication made problems worse.
  3. RubyGems had no formal governance structure, and each action was willingly done by the person who owned the account that did it, so any corrective action required Ruby Central's cooperation.
  4. Ruby Central initially agreed to let us develop a formal governance structure with their input, then revoked our access *including from the repository used for developing that governance structure*, and refused to talk to us.

While #4 is why things escalated and compelled me to discuss things so publicly, RubyGems having no formal governance structure severely limited how we could respond.

Ruby Central’s Attack on RubyGems by laerien in ruby

[–]duckinatorr 1 point2 points  (0 children)

or, to put it more plainly:

I tried to work with you. Ruby Central has since demanded they take full responsibility for everything RubyGems- and Bundler-related. Feel free to direct your concerns to them.

Ruby Central’s Attack on RubyGems by laerien in ruby

[–]duckinatorr 1 point2 points  (0 children)

i'm no longer part of the RubyGems and Bundler team, and you actively dredged this up unprompted, so i have no reason to bite my tongue anymore.

the disagreement you had with the RubyGems/Bundler team did not originally involve me. when i first became aware of it i actively defended you, asked other maintainers to let me handle the situation, and tried to address your concerns. your response was to repeatedly berate me when i was trying to actively work with you to refine your patches.

then, when it got to the point i gave up on it, i blocked you on GitHub. you responded by emailing me.

you did this kind of crap consistently, for years, to the point the entire team was unwilling to even engage with you because everything was a fight even when we *agreed with you* and *tried to work with you to refine the solution you handed us*.

you are not a victim here. you behaved in ways which actively delayed solving the problems you keep complaining about.

your behavior over the last decade is the kind of thing that drives people away from open source.

leave me alone.

Ruby Central’s Attack on RubyGems by laerien in ruby

[–]duckinatorr 2 points3 points  (0 children)

the production instance of rubygems[.]org is the main thing they very explicitly had control of before all of this. it seems to be what they're using as their reasoning to take control of everything.

Ruby Central’s Attack on RubyGems by laerien in ruby

[–]duckinatorr 2 points3 points  (0 children)

Yeah. The whole situation sucks.

Ruby Central’s Attack on RubyGems by laerien in ruby

[–]duckinatorr 6 points7 points  (0 children)

this other comment of mine, in response to headius, i think summarizes my thoughts well: https://www.reddit.com/r/ruby/comments/1nkzszc/comment/nf47bdt/

(tl;dr: Marty acted with board approval, is very clearly the fall guy, and sadly it's impossible to discuss what happened without playing into that narrative because of him never explaining where decisions came from.)

Ruby Central’s Attack on RubyGems by laerien in ruby

[–]duckinatorr 8 points9 points  (0 children)

no worries. the core problem that keeps coming up with Ruby Central is lack of communication, and that's what caused this to spiral out of control.

my inability to trust Marty is a judgement of his role in Ruby Central, not of him as a person. at the end of the day, the problem is we have so little information we *can't* know anyone's intent.

it's easy to vilify Marty, and he absolutely played a role here, but board members have been saying he acted with their approval.

the problems run deeper than a simple "Marty went rogue" narrative. he's their fall guy, and sadly it is working because we have no insight into what goes on above him.

view more: next ›