highly recommend "A Psalm for the Wild Built" by Becky Chambers as a heartwarming, beautiful comfort read during these cursed times
I'm gonna do a re-read... the first time felt like a mental health b12 shot
it's got a hopeful solarpunk vision of a beautiful, possible society that's overcome a complicated, familiar history. the nonbinary main character is able to just exist without explanation. there's an adorable, curious robot buddy and delightful musings on human (and nonhuman) experiences, our place in the planet, and everything in between.
there's also a sequel, "A Prayer for the Crown Shy", which is very lovely as well
take care and stay safe. the next few weeks might get ugly 💜💜💜
#selfcare #reading #fucktrump #socloseandyetsofuckingfaraway #worsttimeline
Speaking of which: if you're interested in building your own search engine for something, and want to test out this software, let me know! All it should require to know is basic (JS) programming knowledge, and jQuery syntax. The backend handles the rest of the complexity. The software will run on a laptop easily.
(For hopefully obvious reasons, I will not assist with unethical projects like scraping personal information)
If you want to be with them, be with them.
If you don’t want to be with them, leave.
If you would like to be with them, but think they are treating you unfairly, demand a better relationship, and leave if you don’t get it.
Nobody is entitled to your association.
As a society we should make it as easy as possible for people to leave bad families in fair and equitable ways.
That is essential to having an egalitarian society. Freedom of association, and also freedom of disassociation.
I should probably start tagging these project update posts with #seekseek or something.
Anyway, current status: rewrite of the scraping backend is almost done. I'm a lot happier with this version than with the previous one, and this one should be a lot more suitable for the original goal of making it easier for people to build their own search engines.
Some big items remaining: switching to embedded Oxigraph instead of a stand-alone server (requires writing some Neon/Rust bindings), rewiring the code so that it can actually load multiple configuration modules with their own namespaces (as it's meant to do), implementing auto-expiry of dependents, worker threads, custom TTLs, and converting existing scraper modules to the new API.
The API didn't change *much*, but enough to need some changes. That should actually end up simplifying the modules!
Update 1.1: added a line about profits and changed to a free license.
#Piracy #AdBlock #YouTube #Netflix #Invidious #DRM #Torrent #P2P #FileSharing #Ads #Piped #Streaming #StreamingServices
@dominicstucki @jon Every time I see a picture of (or interact with) a ticket machine elsewhere, I am reminded of how good we still have it here with the NS ticket machines...
(They're not quite as good in some ways as the old ones with physical buttons, though. But that's definitely never coming back.)
Details are here, for anyone who wants to see some concrete numbers: https://github.com/oxigraph/oxigraph/discussions/924
reference to abusers
@hipsterelectron @foolishowl @skye Both of these things happen in practice; ostracizing mechanisms being misused by abusers, as well as people being prematurely ostracized through emergent community dynamics with no ill intentions. Different types of problems with their own solutions.
I also feel like the original post already addressed this point sufficiently to make clear what the intention was; it did not call for the opposite, it called for 'something inbetween' (which implies addressing *both* issues, which is actually harmed by framing it as a binary choice between 'always ostracize' and 'never ostracize' because many conflict-averse people *will* choose the latter).
I am very much in favour of less- or non-hierarchical moderation approaches as well. But making that actually work in practice requires recognizing that harmful ostracizing *can* still happen without hierarchy, and that that's a thing you need to account for in your culture.
@JetlagJen @skye I... sort of half disagree on the "impossible to quantify" part? Like, it is correct in the most literal sense, but IMO the more important thing is that it's not really *necessary* to quantify exactly.
Generally speaking the people who are unwilling to change, are *very very obviously* unwilling to change, to the point that to anyone vaguely familiar with the signs, there's really not any doubt.
That leaves a small amount of cases where it really is difficult to deal with as a community (think "always immediately promises to change but never does"), but those are generally few enough that they can be collectively handled on a case-by-case basis.
subtooting hackernews
@me But that's the thing, though? The best way to ensure that would be to push for change in Git itself, improvements to the unintuitive stuff, so that people don't walk away and abandon Git?
https://en.wikipedia.org/wiki/International_Non-Binary_People%27s_Day
> The day was first celebrated in 2012, started by Katje van Loon. The date was chosen for being precisely midway between International Men's Day and International Women's Day.
I laughed
Happy NB people's day!
subtooting hackernews
Every single time there's a thread on HN about the issues with Git, it doesn't matter what, there *will* be people jumping in defending it as "it's not that hard, you must just not have taken the time to learn it".
And the fact that such vast swathes of developers, including highly experienced ones, continue to find it unintuitive and unpleasant to work with, *somehow* doesn't register to them as a signal that maybe the problem is actually with Git itself...
I really don't understand people who behave like this. How many people need to complain about something before you're willing to concede that maybe there's room for improvement? Why are you so invested in insisting that it's perfect?
@Schouten_B @McCovican @mathew @RenewedRebecca the attitude of an ethical technology company should be that they provide an unsurprising technology that has their interests at heart - including getting consent from them for features that they might not like. it should not be that the users don't know what they want and it's too complicated to explain things to them
In the process of moving to @joepie91. This account will stay active for the foreseeable future! But please also follow the other one.
Technical debt collector and general hype-hater. Early 30s, non-binary, ND, poly, relationship anarchist, generally queer.
- No alt text (request) = no boost.
- Boosts OK for all boostable posts.
- DMs are open.
- Flirting welcome, but be explicit if you want something out of it!
- The devil doesn't need an advocate; no combative arguing in my mentions.
Sometimes horny on main (behind CW), very much into kink (bondage, freeuse, CNC, and other stuff), and believe it or not, very much a submissive bottom :p
My spoons are limited, so I may not always have the energy to respond to messages.
Strong views about abolishing oppression, hierarchy, agency, and self-governance - but I also trust people by default and give them room to grow, unless they give me reason not to. That all also applies to technology and how it's built.