• 26 Posts
  • 495 Comments
Joined 2 years ago
cake
Cake day: December 31st, 2023

help-circle
  • From my own experience querying public mastodon timelines via API (edit: removed incorrect /api/v1s in the AP_IDs):

    • Mastodon user accounts have an ActivityPub URI of https://<instance.domain.tld>/users/<username>
    • Mastodon posts have an ActivityPub URI of https://<instance.domain.tld>/users/<post_author_username>/statuses/<post_id> (they also have a url property of https://<instance.domain.tld>/@<post_author_username>/<post_id> but that tends to serve the html view of the post)

    To see for yourself, pick an instance that allows viewing their public timeline without logging in (mastodon.social is perfect for this) and follow the “Playing with public data” section of the docs. That page ellides most of the info you’re looking for in the example payloads they give (as the JSON payloads themself are quite large and nested), but I can assure you that AP_IDs for user accounts and posts can be found pretty quickly from a single timeline query.

    I don’t think Mastodon has any notion of community, nor does it distinguish between posts and comments (when following a lemmy community, both posts and comments show up in my masto feed as “top-level” statuses (ie posts)).





  • I guess that’s a tad better, though if the rule is named react-hooks/exhaustive-deps then we’re still not explaining why we’re disabling it.

    What I’m really looking for is something that explicitly tells the programmer/code reader “this blows up into an infinite loop if we respect exhaustive deps, but here we don’t need exhaustive deps for the code to be sound”.

    My own, hair-baked proposal: have the linter recognize [foo, baz /*, @causes-infinite-loop bar */] (or something along those lines) as an explicit, programmer-validated escape hatch for not respecting the exhaustive-deps rule.




  • As someone who started using react about 6 months before they introduced hooks, I remember there was a period where people were really complaining about having to manually reason about what went into every single hook dependency list. Eventually the linting rule was published. I distinctly remember appreciating the rule in situations where a variable that used to be a “plain” variable became a useState hook - it caught some existing uses of the variable in hooks that otherwise were unrelated to the code being changed.

    I also distinctly remember being disappointed that there was no specific way to annotate code that needed to disable that rule to prevent infinite loops, just a generic // @eslint-ignore… I guess they still haven’t shipped a better way?



  • In my experience, they weren’t silent, nobody was interested in paying attention to what they had to say in the first place. The Muslim community doesn’t have it’s own television or radio stations, unlike the far right and capital interests who spent so much time on the country’s radios and television stations and newspapers asking “why don’t we hear anything from the Muslim community?”. How is it they never find a single Muslim to interview? Maybe Muslims just aren’t ignorant enough to walk into the trap.

    Not to mention if things really were that simple, then the French would be as critical of their own when they burned down the house of a mayor who was going to set up an asylum seeker’s refuge.

    So yeah, I can and will blame the French for being intellectually lazy and succumbing to bigotry. Nothing new for them/us.


  • Chatting about video games seems to be the best chance at having a fun convo that doesn’t turn into dehumanizing groups of people. If we can pull that off, given Luigi’s supposed internship at Firaxis, the rotation could scrape by a passable 7/10.

    More realistically, a 2 or 3/10 if the weed is really good. Otherwise I don’t know if I would even bother.






  • And they just. keep. doing it!

    Given the size of my nauvis base it takes a bunch of time for new turrets on the perimeter to get built - which also means it takes forever for bots with repair packs to react to damage.

    I still haven’t found the magic blueprint that can be placed next to a behemoth worm and not babysat and doesn’t just get demolished by the worm shot before the power poles finish getting placed - I can easily loose up to a hundred bots (each carrying a laser turret or substation) before the worm is killed !


  • Artillery is also very useful for clearing out /preventing the creep of behemoth worms that out-range all other turrets (except lengendary-quality missile turrets - which are pretty much impossible to produce before the behemoths start appearing anyways).

    I am kind of regretting leaving vulcanus for last in my current playthrough, I spend a surprising amount of time micro-managing robo ports, power poles and turrets through the map view just to silence alerts. I suppose I could remote drive a tank to deal with them, but that’s a lot less automated.




  • Op, I appreciate that you seem to be genuinely interested in these topics, and are not just farming engagement (which is kinda meaningless here on the Fedi, anyways…). If I may offer a suggestion, try to find a tone that doesn’t sound like a roadmap for some corporate brand strategy. Most of us that are here and would be interested in a “fediverse permaculture” are severely put off by the structure of your post, not to mention it lacks in depth for most suggestions to be directly actionable (for example, the merch you would sell to support the insurance still needs to be made somewhere, by someone, who either needs to be paid for their time or are already independently wealthy).

    Have you taken a look around !permacomputing@slrpnk.net ? Permaculture is not just about principles of mutual support but also a long process of experimentation to see which combinations of which plants and practices works out “for the best”. You might foster more of the conversation you’re looking for if you can bring some more concrete examples or proposals to serve as topics instead of an all-encompassing manifesto post.