Posts by supakaity@blahaj.zone
(DIR) Post #AQ45kulQ8CySQEdTwO by supakaity@blahaj.zone
2022-11-28T14:03:36.831Z
0 likes, 0 repeats
@addmen@mastodon.thefword.club I'm trans and I'm not ashamed of it.But I'm a woman also, at the core. I don't mind being referred to as a trans woman to differentiate my existence from that of a cis woman when it's appropriate to do so.However, being othered is not okay. I'm not a different species or third gender. The compound term "transwoman" is especially offensive in its othering.So yes. I'm a woman who's transgender.
(DIR) Post #ATIsEZWJVUEqD6EpG4 by supakaity@blahaj.zone
2023-03-05T08:37:52.524Z
1 likes, 1 repeats
We need your help.First us, next you.Even if you don't know a single trans person in real life, or don't truly believe that we really are as we say; stand up anyhow before they start talking about killing people who you do know and do care about.It starts with us, but it ends with you.RE: https://blahaj.zone/notes/9bymrcqgkv
(DIR) Post #ATS0PYtasdIke1iZU0 by supakaity@blahaj.zone
2023-03-09T20:35:42.527Z
0 likes, 1 repeats
This Sunday, I, along with my spouse, my best friend, my brother and a whole lot of others will be attending the counter protest against the fascist TERF "Posie Parker" in Brisbane city.I want to appeal to our allies, to come and attend with us. We all need to stand up together against fascism, and alone, trans people're literally < 1% of the population. We can't do this alone, we just don't have the numbers.Warning:If you're a cis woman, regardless of how you look, you'll likely be assumed to be a transgender woman. You'll get told that you'll never be a woman, that you're just an ugly man, that you're putting women and children at risk, and that you shouldn't be using women's public restrooms.However if you're a cis man, regardless of how you look, you'll likely be assumed to be a transgender woman. You'll get told that you'll never be a woman, that you're just an ugly man, that you're putting women and children at risk, and that you shouldn't be using women's public restrooms.Standing with us, you'll be taking on the risk of being assumed to be one of us, but WE will appreciate every one of you that lends us your support.Please, please consider coming. And if you can't come, please boost this post. Standing up to fascists and bigots is all of our responsibility.Thank you for reading.:Blobhaj_Heart_Trans:https://fb.me/e/5Ck2oeWin
(DIR) Post #ATf0w62wadtZtv7lIm by supakaity@blahaj.zone
2023-03-16T03:06:12.850Z
1 likes, 0 repeats
I have implemented support for sonic server on Blåhaj zone's Calckey instance.I am in the process of reindexing approximately a metric boatload of posts, quotes and replies from postgres into sonic, but currently, new posts are getting indexed into and searches are being served from sonic and not postgres anymore, which should make searching a lot snappier and less grindy.
(DIR) Post #ATfLDWxBnjM1MH1UX2 by supakaity@blahaj.zone
2023-03-16T07:12:33.361Z
0 likes, 0 repeats
@icedquinn@blob.cat I have, but it is realistically a paid product, I'm not against paid products per-se, but I typically write (myself) and support libre software when I can.I also considered toshi, pica and bleve before settling on sonic. It's fast, has a nice blend of features and is 100% free and opensource.
(DIR) Post #AVk5KMxVr5PimXxFw0 by supakaity@blahaj.zone
2023-05-17T08:37:15.384Z
0 likes, 1 repeats
Preface: This is a long, technical post so I apologise in advance. Please avert your eyes if such things offend you.Hi everybeings!Overview@Ada and I have discussed many areas where we see problems in the way the Fediverse currently works and where would like to see improvements made to improve safety of the fediverse.Safety on the fediverse is one of the topics we hold most dear.One of these areas (and one that has recently garnered a lot of attention) has been in the area of full-text search, and despite the option for account-wide no-crawl options in many pieces of fediverse softwares, this option is not-federated, non-specific, non-granular and not-for-purpose with regards to fediverse searching. It's specifically designed and worded for crawler bots at a html scraping level, and while we could repurpose it for fedi-searching, it just doesn't feel right or quite fit.There's been a lot of talk on a lot of different levels out there, but nobody's come to a concensus. A lot of people are talking about how we should do it and what standards we should use, and generally making the whole concept a lot more complicated than it needs to be.In this post, I want to share with you some of the ideas that I've gathered through my research, and implemented in a way that is simple enough (KISS), not overly complicated (YAGNI) yet still fit for the purpose I need as both a software engineer and an instance admin, and that anyone accessing the content will need.The idea in sharing this is not to convince me that it shouldn't be done, or to create the absolutely most perfect solution possible that's going to take 20 years to build and will be outdated by the time we get there.This will be getting built and going out in weeks, not months, not next year. It's needed now. This is my current plan how to implement something we needed months ago, now. This is your chance to change my mind and help refine this plan before I start really coding it up.Technical/implementation detailsA lot of these options will be settable as a default value in your settings as well as at an individual post / file level during composition or afterwards at editing stage.In terms of inbound federated AP objects which do not support these new fields, we will try to infer the intent based off existing AP fields and other metadata when present.Specifically, we will be using the Mastodon Account Lookup API (GET /api/v1/accounts/lookup?acct=) to get and store the noindex flag during actor creation/refresh. This will also allow us to put the noindex meta tag on any HTML pages containing that actor's posts.SearchabilitySo you don't want people to be able to search for you. But is that everybody? Maybe you want your followers to be able to find your posts? Maybe the people you mention should be able to find your post? What about actual users on your local instance? Maybe a particular post you never want to appear in searches? Maybe a particular post you write contains stuff you want everyone to see?We will be adding a global default and per-post override federated in AP as hk:searchableBy which will be settable to public, private or a combination of followers, mentions or local. This is different to the currentvisibility in that you can have a public visibility post that is searchable by followers and mentions for example.{ ... "searchableBy": ["followers", "mentions"]}InteractivityThe other problem is that at the moment you can't control who can reply, boost, vote and/or react to your posts.To this end, we will be adding per-post overrides federated in AP as hk:canReply and hk:canInteract which will allow you to specify like on searches a combination of public, private, followers, mentions and local for replying to, and boost, voting or reacting to your posts respectively. { ... "canReply": ["mentions"], "canInteract": ["public"]}LicensingLicensing and attribution can get pretty tricky. On the fediverse, we're assuming that if you're making a post, then you have the rights and willingness to let the content be federated. If you didn't you wouldn't post.However posting content sometimes requires you to provide the license and attribution that you're using along with the content. At the moment there's no reasonable or standardised way to provide this information on an image or in a post, thus you're in breach if you post a CC-BY licensed image.So to alleviate this, we will be providing 2 federated AP fields hk:licensing and hk:attribution. The licensing field will contain the URL of the license under which the content is being shared and the attribution will contain any links to the source content/s and/or creator/s.{ ... "license": "https://creativecommons.org/licenses/by-sa-nc/4.0/", "attribution": [ "https://github.com/supakaity/icons" ]}CrawlabilitySo crawlability is about indexing of the content by external parties whether they be search engines or fedicrawlers. It will provide a per-object level flag under the AP field hk:crawlable that lists whether the item may be processed by a bot. The possible values are true or false.{ ... "crawlable": false}QuotabilityNow this is a controvertial one. Sometimes people out there don't mind their posts being boosted, but don't want them to be quoted. You know what we say? If you don't want your posts quoted, we should respect that and not allow people to quote you. So we'll be supplying an AP field hk:canQuote that lists who can quote your posts using the same combination of actor types as above.{ ... "canQuote": ["followers"]}
(DIR) Post #AVkFgVjwt1kfveo5iq by supakaity@blahaj.zone
2023-05-17T11:01:51.532Z
0 likes, 0 repeats
@cody@misskey.codingneko.com @Ada@blahaj.zone the answer is that we don't plan to enforce it.These are advisory mechanisms that allow you to express your wishes.We want to be good citizens, we want our users to be able to be good citizens. At the moment there's no real way for someone to tell us how they want their content treated.We will apply them on our instance.Hopefully other well behaved instances will as well.Deliberately misbehaving has other recourses available.We will of course highlight (or lowlight rather?) bad actor's actions in the thread view and probably add options to toggle them hidden, collapsed or shown (depending on user preferences), on the main instance, and maybe not even include their actions in the conversation list for onward federation.But really, enforcement is not the point at all. At the moment there's no way for the author to even tell us any of this stuff so that good actor's can act good.
(DIR) Post #AVkKfpfRoLNpDKCIHQ by supakaity@blahaj.zone
2023-05-17T12:18:12.336Z
0 likes, 0 repeats
@Jain@blob.cat @ada@blahaj.zone @cody@misskey.codingneko.com I actually don't want to get dragged into the enforcement argument.You're absolutely right in that it's not going to be possible to stop actors deliberately doing bad things on the fedi.The whole point is that at the moment, as a good actor on the fedi. I don't know your wishes, because there's no way for you to tell me that you don't want me to be able to full-text search your posts, or that you're not interested in my opinion on a particular topic if I wasn't mentioned.How do I be a good actor if I don't know how?Well, we give you a way to tell me.
(DIR) Post #AVkKiktC26vRGN1KKm by supakaity@blahaj.zone
2023-05-17T12:22:05.395Z
1 likes, 0 repeats
@Jain@blob.cat @ada@blahaj.zone @cody@misskey.codingneko.com Moreover, it has not yet been discussed to what extent the answers to a thread should take over these flags. I can well imagine that especially the restriction that not all can answer is generally very difficult. You would either have to accept that the replies have their own/different values for the flags, or you would have to share whole follower/blocklists to be able to restrict a post really cleanly.Just like you can't expand visibility on replies, you shouldn't be able to expand rights on replies. There's a whole bag of worms waiting under the "but should you be able to futher restrict on replies" and the answer is probably yes... but that's gonna make my brain sore when I start thinking about it...
(DIR) Post #AVkQGlMjGfHAMCs4RM by supakaity@blahaj.zone
2023-05-17T13:14:43.211Z
0 likes, 0 repeats
@Jain@blob.cat @ada@blahaj.zone @cody@misskey.codingneko.com Again it's going down the path of focusing on the "bad people", but I'll indulge you a little.Does using software that doesn't support it make you a bad actor? Not necessarily. It may makes you an unaware user. And that's not necessarily bad. Or you may be a user that's deliberatley using old software to bypass these restrictions. It's not an uncomplicated situation, and someone may chose to block you if you keep posting after being informed, that's dependent upon the two user involved. If that user keeps doing it, maybe it goes up the chain. We already have moderation processes to deal with these scenarios.Is it possible in the current framework? I don't believe so. I've done substantial research into this, so I'm not just pulling this out of nowhere.Will it harm more than it solves things? There's significant harm being done at the moment, and no movement on solving the issue. Is this the right answer? I think it's a good start.Is it user friendly and understandable? Explaining the advisory nature of this feature, documenting it and raising awareness of it is a big part of the implementation that needs substantial consideration.Unfortunately automatically parsing a profile page is a very poor way to determine if I should show a specific federated post on my instance to users who are entering a search term.I'd prefer to be given a clear direction on if a certain user can see your post in their search results rather than guessing and even worse guessing wrong.
(DIR) Post #AXwzcSMyzArqvbCF60 by supakaity@blahaj.zone
2023-07-21T00:54:42.112Z
1 likes, 0 repeats
The fire shark, or eldhaj.