• 1 Post
  • 27 Comments
Joined 1 year ago
cake
Cake day: July 7th, 2023

help-circle
  • nice! I see we both landed on very similar solutions to this. I’m going to implement your double-reversi loop to see how that plays out - it’s the main difference to mine which keeps the secondary piston extended by default, and it retracts and pushes based on the pulse-extender decaying fully.

    I like this, thanks for sharing!


  • OK, so here’s the update. thanks to all the suggestions - I combined a few ideas, and came up with the following solution.

    The observer triggers as items drop, this does two things at once:

    1. Drives a pulse extender which immediately retracts the secondary piston
    2. Pulses the primary piston after a short delay to push the items into the space that the secondary piston just made

    As the clock decays fully the secondary piston fires and pushes the items.

    An added bonus here is spam protection - so if items drop consecutively more quickly than the clock decays, it simply resets the clock so you don’t get pistons firing together, or too quickly. This way nothing ever ends up on the top of the slime/honey blocks. I’ve added a front-side view for those curious as well.

    Thanks for all the help and tips!



  • I tried to implement this, however my right hand side piston stays extended for the duration of the pulse extender rather than firing and retracting like the left hand side one does. Not sure if I am missing something in the pic that I cannot see. I also wasn’t able to figure out what you’re doing with the dropper - seems like it’s on top of the observer for some reason and the clock coming out of it doesn’t do anything?















  • Swaziboy@lemmy.worldtoAsklemmy@lemmy.mlWhich email provider?
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    10 months ago

    Check out Fastmail. Pretty much ticks all the boxes, I’ve been using them for a decade or more. Ultra reliable, good value and constantly innovative and adding features especially in the collab space.

    My only gripe with them is their mobile app is online only in that it doesn’t work in a cached offline fashion. That can be addressed through alternative clients though and their web app is pretty slick.

    Bonus points for them, you can host your DNS with them too and you can manage it all fully integrated.

    Edit: typos


  • Ok I got ya. Doesn’t that then limit the effective use of the hierarchy to the instance you’re on and the hierarchy you’re familiar with? In that the further removed you are from your home instance’s hierarchy the less likely things will match up. So ultimately searches loose effectiveness I think?

    Anyhow like someone else said, not trying to disparage the idea - it’s interesting and I’m enjoying the various input and thoughts folks are bringing.


  • Structurally the idea has some merit. I think the challenge that you will encounter especially in a federated environment is gaining agreement on how to fill that structure and the hierarchy that you’re implying and demonstrating. Using the pug example, you’ll likely find very little argument on a good hierarchy, but using a more contentious example, let’s say gender, how will you gain agreement across instances on what the hierarchy within the data should represent?