• +30 yo • demigirl • Brazil • QA Architect • Community Moderator • Português • English • Español • Français (un peu) 🎗 🚂 ☭ 🍉 Icon by @alphajn.bsky.social ATmosphere: linkat.blue/did:plc:fip3nyk6tjo3senpq4ei2cxw Tags: #Blog • #BskyTips • #Cupom
https://bsky.app/profile/thisismissem.social/post/3m6iqez76wc2i
Here a direct link to the thread talking about it in more detail, plus credits to Emelia for the information about their API to partners.
I was in the thread talking about this, and indeed the StopNCII website doesn't help to answer this question. But their API has a way to receive feedback from their partners if a hash may not be legitimate.
Bluesky Safety thread definitely wasn't enough to provide reassurance for their users about how they would prevent this system of being abused by ill intentions, how and when they will review hashes detected. A blog post would've better if you asked me. I hope they are taking notes of people questions to answer them.As you said in the same paragraph: "Maybe we can have a little centralization, as a treat?"
I enjoy Pix a lot here in Brazil, combined with Open Finance we have here too, the flexibility and velocity to send and receive money from/to anyone, 24/7 and no matter the bank, it's very amazing, no wonder it's heavily used by Brazilians (and even some other countries that have an economic relationship with Brazil) in just a few years after being implemented (example: I can just open my Google Pay wallet on my phone, send or receive money with Pix using NFC or QR code or a key, directly to/from my bank account, without opening the bank app, I use it almost every week).
Solutions more in this kind of direction (easy, quick, high availability, low to no barriers) is what I think it's going to really be the future of money.
Web3 could try to incorporate some lessons (I know a decentralized system can't follow the same steps as a centralized system - Pix implementation is managed by the Central Bank of Brazil, how the system works is defined by them and then applied by every bank or fintech).This is one of the reasons I think crypto will never be really mainstream across the world. At least, not until it changes drastically to be more user friendly (but even then, there will always be a part of the population that doesn't like blockchain and crypto at all, let it be by preconceived opinions about the tech or just personal preferences).
Companies can try to abstract a lot, to help, but doing so, in the end, the user won't have full control of individual crypto in their wallets (example: I experienced with one Brazilian Investment company that made it very easy to invest in the most famous cryptocurrencies, but you didn't actually buy directly, it was through crypto funds they managed, so it was easy and quick to invest, but I could never send some Ethereum to someone's wallet).Oh that's pretty cool 👀 taking notes to search up more about itYes! I thought of this too. Just logging in started the lexicon migration process in the background.That was hard to choose...
I effectively voted for image gallery for the artists, but table and footnote would help me a lot, and event is cool because we love to see more integration between different apps.
Audio could be very interesting too.TOKIMEKI too, but it's kinda a way to figure how to work with this field for now, since the Bluesky itself doesn't use it yet.
Would be nice if the pronouns appears when you are reading someone's post, like the current pronouns labels. Keeping it only on the profile feels like following too much how other big tech social media do things instead of trying to improve the user experience. But that's just my own opinion.The reader is awesome and finally made me change my home page theme to a custom one.
And I'm loving all the new feeds, especially the one of who I'm following (a great way to discover potentially new publications of my interest to subscribe).Testing out the comment inside a subpage, such inceptionHumans are biased in some degree, always. So everything that is made by humans, the news, algorithm, AI, articles, social media commentary, everything has some level and type of bias.
The problem is when they try to hide it, masking it as neutral or having a different bias than the reality.While using TOKIMEKI, you can choose to show the "via" information in the settings, but since they are the only client using this pattern, only posts made in TOKIMEKI show information there.Some already do that but for now it's not a shared pattern.
I know Flashes and Pinsky adds some kind of hidden tag inside the post lexicon, that works inside Bluesky to search and mute.
TOKIMEKI adds this info inside a "via" field inside the lexicon.
TOKIMEKI example: https://pdsls.dev/at://did:plc:b5qihcej3titzzr2iauzvrer/app.bsky.feed.post/3lz5haz4i3c2u
I don't have at hand right now examples from Flashes and Pinsky, but I can find those later to provide a link too.
Also, once we got more options for other parts of the ATProto stack like we have with relays, I can see we having many types of "remixes". I mean different applications using a mixed selection of services.
But stuff needs to mature more to handle millions of potential users.You can only go so far alone. I feel that, once we have more traction with multiple communities efforts and working groups, problems like moderation for videos and images at scale, diverse appviews, will come along.
Just like Blacksky started, as a need for one specific community, Northsky and Eurosky likewise, I can see it happening for other communities, given the time for them to organize and build for their needs.
I think there is a place for clients, hybrids or completely separate apps from the Bluesky itself and the company. It's good to have clients like deer and zeppelin, that showed us some possibilities to deeper user customization for the backend and moderation, but also clients more dedicated to customize your visual experience (client dedicated to photos, or to videos, like you mentioned a bunch).
Tldr I think we need to give more time for people to get together, organize their efforts and money to build more diverse stuff with the protocol.I would love some kind of subpages with publications posts too, for when the post might become too long, so we could segment it into chapters.
The subpage for standalone docs works so well, easy and intuitive.🙏 Thank you to listening the people complains, investigating, and taking action to fix it.