Someone said I was a casual gamer because I was finding the core gameplay loop (the process of leveling, etc) of WW to not be something I was enjoying and both my girlfriend and I were like… whut.
There's nothing wrong with being a casual gamer, and also. What even. What definition of 'casual' are you using here, exactly, given that I play games a whole hell of a lot more difficult than WW.
The hardest part of building a quality filter for the fediverse has very little to do with the scoring system.
There are massive social problems and a host of tedious technical problems, but the actual scoring system for the filter itself? Not terribly difficult.
Like, sure, it's difficult to optimize and get right in the long run and there are gotchas along the way, but fundamentally all of that is gated on the rest of the system behaving and the social problems being solved.
Evidently a few men have tried "would you rather talk to a woman or a tree about your feelings" as kind of a weird "clapback" to the man vs. bear thing and I'm like… you'll talk, voluntarily, out loud, about your feelings and not make it some poor random non-therapist's problem? Really?
Please do men! Go forth! Spill your secrets to trees. May you find it to be very fruitful.
Stop sharing things that discourage people from donating to charity because you saw in a meme that a corporation is doing something that they aren't actually doing.
Arkansas is ranked above Colorado. Alaska is one of the top 4.
Arkansas does not have discrimination protections for gender orientation or identity. It does not have a hate crime bill and the "watered down" hate crime bill it does have does not include gender orientation or identity "implicitly or explicitly." They ban trans people in athletics.
They passed a bill to allow healthcare practitioners to deny healthcare to LGBTQ patients.
If you have a model and it puts Alaska and Arkansas above Colorado, you need to treat that as a signal that your model is so wrong as to be no longer usable and you need to seriously question whether to share it with others, at least without massive caveats.
It is unconscionable—data malpractice—for a group to release a report like this.
@hrefna My god in no world would I say Arkansas has a higher safety grade than Washington. I grew up in Missouri/Arkansas and moved to WA. Are there places in AR you'd feel safe? yeah! Are there more places in WA you'd feel safe? Absolutely.
It'd be very convenient if I could negotiate with ants.
There are a group of western harvester ants in a rather inconvenient spot and I'd love if they could move like… 20' over. Or a few hundred feet in any of three different directions.
I saw an item on Dutch news not long ago about how invasive ant species in the Netherlands form supercolonies with millions of ants stretching out under complete street blocks and only growing further.
One of these is the Tapinoma Nigerrimum ant coming from the mediteranean with the warmer weather.
They do invade houses and apparently are attract to electricity. They also dig up sand for their colony, causing roads to get uneven or even have sinkholes in them.
One idea I've toyed with before that I think is really interesting is the idea of having a persistent inbox but an offline processor
So think of it like this:
You have a queue that sits online with a webserver in front. The queue has some logic (the kind you can configure with RabbitMQ) for deduping and routing, but is still just a queue.
That's the only persistently online piece.
(@jenniferplusplus mentioned this earlier as well, this is not unique nor original to me as a thought)
@hrefna ooh are these thoughts about how an actual activitypub client might work? thought about this too, but my other ideas got mad at me for having yet another 😭
"this could be distributed IM.. would just need connector servers which could handle federation by providing persistent queues.." and then i realized i would have to look into how ap actually works in detail and perhaps even gasp read some other implementations' code.. it'll probably be in js or php :blobfox0_0:
@hrefna@jenniferplusplus I've had this idea before too. What specifically is the application? Is this in the context of ActivityPub? Or more generic?
This does sound, basically, like how email worked for most people once upon a time. SMTP+POP. The SMTP server was "permanently" online. When the user wanted their email they connected to the internet and downloaded the new messages through POP.
Would this be a more generic and less sucky version of SMTP?
There's a design pattern that is (somewhat tongue in cheek) named multi-single-tenant.
The idea is basically that you have individually created (and often provisioned) systems that are run on the same base system, sharing many of the same core pieces of infrastructure but in a way that keeps strict separation between them.
So I can deprovision someone and that's basically a wipeout. No tracking data to weird places, it's all under one provisioning handle.
I don't think either choice is bad and I think you can fit either model into a conception of the future of the fediverse, but if you are going to treat a position as a moral good then you need to understand the problems that led to the current state and you need to have an answer for how you address them.
Our software today is neither fish nor fowl and wildly out of alignment with what people seem to say that they want. That's my frustration here.
What interests me here is the upcoming trend to build local-first clients, and how these may fit into a social web. Of course there are servers in that picture, but if the social web were service-oriented and the client an 'orchestrator' of services, it would be a whole different paradigm.
You get rid of the "technical self-hosting" problem.. just install a client. You can deal with the ownership of data issue.. at the client.
And the social web would be a 'marketplace' of services.
Me: "Maintaining an always-online server is overly complex and not something we can ask people to do who just want to do some social networking."
Reply: "Oh this is a long solved problem between these various technologies with obscure acronyms and guides! This was being done before Docker, that's not a requirement!"
Thank you for proving my point for me.
Also I don't understand why people keep talking about Docker with me when I talk about things like this. Like, seriously, do not get it.