GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Notices by Chee Aun 🤔 (cheeaun@mastodon.social), page 4

  1. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Tuesday, 21-Oct-2025 13:21:53 JST Chee Aun 🤔 Chee Aun 🤔

    Random thought: maybe custom emojis should've be called "Stickers" 🤷♂️

    In conversation about 8 months ago from mastodon.social permalink
  2. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Thursday, 16-Oct-2025 22:20:00 JST Chee Aun 🤔 Chee Aun 🤔

    Just read this long post on "the current state of Cara" https://cara.app/post/2e0d29d3-a57a-4b70-b0d0-9cefc15176ca

    🤔 "Not having an algorithmically recommended feed is the biggest reason why people dropped off from Cara after we went viral. In a chronological timeline, if you only follow 2 people who post once a week, you’re going to have nothing new to see and no reason to return to Cara after one day."

    #CaraApp

    In conversation about 8 months ago from mastodon.social permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: images.cara.app
      Jingna Zhang (@zemotion) | Cara - Artist Social & Portfolio Platform
      About the current state of Cara— Hi all, I’d like to address some users' concerns about Cara’s stability, algorithms and reach, and why we don’t actively promote Cara and recruit new users. I have touched on most of these before through other posts, but I’ll like to go over the main points and put them in one place since they often come up as recurring questions: — Cara’s longevity/stability > "A few weeks ago, after learning how much Jingna was struggling with her personal life, I thought, If something happens and this website shuts down for some reason, my online presence will die because I don't have any other social media." You are right that I am not a multi-billion, or even multi-million corporation like other social media companies. I am an individual. But I have had my photography business for 20 years, and taken it to a place where people did not expect of me. I think I can safely say that I am good at committing myself to things I care about and doing a good job.  People have said we won’t be able to launch a platform like Cara before we launched, but we did. Then they said I’d quit in a few months, but it’s been 3 years. And then people said that only a few hundred people would use Cara, but we grew to over a million. I believe the results of my work and capabilities speak for themselves, and will continue to do so. In terms of health, I knew that posting about it could have an averse effect on confidence in the platform. But I accumulated these health issues because I was working on Cara. I wanted to be transparent and share my thoughts on developing Cara and its progress—that includes not only the good, but also the toll it takes. So while I understand the apprehension, I want to say that as an artist, I used to think I would remain on DeviantArt forever, until Facebook, and then I moved to Instagram. Other companies may change, but my track record speaks for itself. — User traffic compared to Bluesky > "I don't sell commissions to artists, which is Cara's user base and what I see getting the most sales here so I understand." > "I can't yet say if Bluesky is good for me in terms of conversions because I just started, but the 450 followers I got on Bluesky in just a few weeks have clicked on my Patreon page more than the 4,500 followers I got on Cara" Bluesky has close to 40 million users, according to Google. Cara has 1 million. I know the comparison here is 450 followers to 4,500, but follower number isn't indicative of the full picture. Think about TikTok, and how you can have 50 followers but have posts that reach millions of views. The size of a platform's user base and how posts are pushed to people who don’t follow you when there is an algorithmic feed makes a huge difference. To make a fair comparison, you have to consider those factors too. What happens when you post to Cara right now is that we show your work to your 4500 followers in a regular, chronological feed. And when you post to Bluesky, Instagram, TikTok, or other social platforms, instead of just your followers, it can potentially reach 40 million users on Bluesky, 1.5 billion active users on TikTok, and 3 billion active users on Instagram. And all of those people make up the potential audience who might click on your links. Reach and engagement will always vary significantly between platforms depending on the system used to show posts to users, what stage it’s at, and the size of the user base. Expecting to see a user base of 1 million to equate to 40 million in activity, in any form, is imo a stretch and somewhat unfair comparison.  TLDR: You cannot calculate the engagement rate on Cara the same way as you do other social platforms, when the mechanism of delivery, discovery, and size of the platforms are completely different.  — Algorithms & Reach > "I don't feel like it's really welcoming to everyone. If someone only likes photography, but only sees anime when they join, it's kind of a bummer, and they'll just leave. If someone is really into traditional art and doesn't care about digital art, they might get tired after scrolling through a few minutes of content they don't like. > "Even though Cara doesn't use an algorithm, I wish there were features similar to subreddits or Bluesky feeds, so users could navigate the website or app without needing to use the For You, Home, or Discover pages." What you’re looking for is a recommendation algorithm which I have talked about before, but TLDR is yes, I agree there is a need for it, for the reasons you have stated. People often complain about social media algorithms, with good reason. Many are valid criticisms about how platforms deploy them today and the habits they lead us into. But what people sometimes fail to consider is that for many others browsing a platform, they often just want a feed that automatically shows them content they relate to. Or at minimum, a way to fine-tune their preferences and receive posts on their home feed that’s aligned with their interested topics. Like your example of wanting to see photography versus not wanting to see anime, we had a new user who once signed up and immediately cancelled their coffee subscription, because of this exact scenario. Viewers want to be able to easily find content they care about and to see less of things they don’t. Not having an algorithmically recommended feed is the biggest reason why people dropped off from Cara after we went viral. In a chronological timeline, if you only follow 2 people who post once a week, you’re going to have nothing new to see and no reason to return to Cara after one day. So designing and building such a feed is necessary, but doing it carefully requires great engineers, designers, and full time staff that we don’t currently employ or have the money for. Which brings me to your next point: — Fundraising & Finances > "The problem is not getting capital for servers or even not getting more users." Bluesky raised $15 million from a crypto VC when they grew, so they can afford to employ people full time. We don’t have that.  When we went viral last year, we looked at a range of options for raising funds and I laid out my considerations for each one in a post about Cara’s financial situation. But the moment I mentioned VCs, even with safeguards in place to legally protect ourselves and Cara’s vision, we faced intense backlash. Some new volunteers who joined during the traffic surge threatened to launch campaigns against us, some others harassed people I knew to get at me personally to do what they wanted.  These were vocal, active, and involved members of the artist community. It got so bad that one of our long-time staff became so afraid of saying or doing anything that they suffered a breakdown. I want to protect our team and make sure this doesn’t happen again.  The backlash affected me too. Up till very recently, I felt like I had to walk on eggshells any time I wanted to say anything. I’d compulsively write, rewrite, and rewrite again dozens and dozens of times. Each piece would take multiple days and I’d be unable to do anything else, and sometimes I still couldn’t let myself post in the end. This post took 12 hours. You might think this seems excessive, but over the last 3 years, every single time we have gone viral on other platforms promoting Cara—something I was confident about and succeeded at—there would be art accounts who would take the opportunity not to only diss us (which they were entitled to), but also spread misinformation and make up false *criminal* allegations about me that dealt real damage, not only to Cara, but also my professional reputation that I’ve worked two decades to build as an artist. For that, I was less prepared for. Because of what happened, it became difficult for us to add new volunteers. So the work on Cara has significantly reduced this past year compared to our first two as we reevaluated our vetting process. Right now, we have 1 engineer who updates the mobile app regularly, for which I am extremely grateful. And when we have emergencies, our previous team members still come together to help out. But working on an algorithmic feed and delivery system—that’s an entire different beast, and requires a significant amount of full time work to be done.  Recently, I’ve finally come to recognize that the best course of action to help make the team and I feel safe would be to seek legal and professional assistance instead of attempting to deal with it ourselves. It’s common sense in retrospect, but to hire lawyers, we'd need money. And for a long time I just didn’t feel like it was a place I should be spending our funds and time on, when so many other things were important and needed our attention. Of course, no matter the reasons, I was the one who ultimately did not raise when we had the leverage to do so. With everything else that went on, I wanted to be extra deliberate about vetting for people who aligned with our vision. I didn’t think it was a bad thing to wait for the hype to wane—because if someone was still interested in us after the buzz was over, then they would be more likely to be someone who genuinely believed in what we’re building. (If you notice a pattern in how I make decisions when it comes to hype, you’re not imagining it. I’ve done this the counterintuitive way my entire career, and it has always worked very well in putting together the best teams and collaborators.)  There are many options for us now and I’d like to focus on looking forward. I have some thoughts and plans around our financial matters, and will put out a post when I’m ready. I know this is a lot, but I wanted to provide some context to the situation and hope that will make it easier to understand why we’re at where we are. — Recruiting new users > "I know you say Cara needs to be ready before it's released to the public, but it's already amazing! Every social media platform has hiccups and bugs, and nobody cares." > "In my opinion, the problem is retaining new users." You say you think Cara is ready as is to be promoted to a broad audience, but as you yourself have observed, Cara without an algorithmic feed impacts how people can scroll and discover creators on Cara. When they can’t find the content they want because they’re expecting Cara to operate the same way every other platform does, the result is they leave.  Without a recommendation system, promoting Cara to a broad audience is a net negative. It will get people signing up only to find themselves disappointed, and they’ll go on telling others that it doesn’t work for them. Once people have experienced a product once, it will take a long time before they’d be willing to try it again. So as much as it sucks to feel that our user base is small, rushing to grow for the sake of growth at a time when we’re not ready will only do more harm than good. What we’re doing is a deliberate choice. As for a recommendation system, it’s not trivial work. ML engineers have historically been paid extremely well because timeline feeds take work to do, and it’s been one of the most important pieces of technology on a social media platform for so long, for a good reason. There are literally research papers written about TikTok’s algorithm.  To do any of these, we need not just full time engineers and designers, but people who are *great* at it. We also need to set aside funds for moderators, lawyers, and operations team.  The community we had last year had a vocal few who strongly opposed us raising funds to operate Cara like a business. They came as a result of our sudden growth. And while I prioritized those concerns, I recognize that after time passed, the overall outcome has been a net negative on Cara’s development. In that time I’ve settled our unexpected bills, and have worked doggedly on moderation tools on the backend. That has been our priority and is something I believe is critical to have before we can think about more growth. You may not give much thought to it as an everyday user, but there are so many things with big impacts we need to have ready before we can grow to 10 or 50 or 100 million users. Without a good foundation on moderation tools, there will be bottlenecks if we had explosive growth again. We barely survived by the skin of our teeth last year. So not everything comes down to simply getting more people signed up. In fact, I’d say the funnest and easiest part of everything is getting new users. What’s hard is the groundwork for all of the foundations we need that comes before the signups, those take time and preparation. For anyone old enough to remember when CGHUB was the #1 website for the entertainment industry—I was in charge of inviting users in its early days. So trust me when I say getting people to join is the least part of our concerns. It’s really the most enjoyable part for me. But only when we are ready. (To be clear, feel free to invite your friends to Cara! We love being recommended and having steady, organic growth. It’s the explosive traffic that comes with massive promotion that could impact platform culture that I’m concerned about.) A final word on the 'slowness' and 'quiet' you may experience right now: aside from the algorithm, to me, this is an important part of the current process, even though it’s counterintuitive.  I want to build a strong foundation and culture with the user base that’s here on Cara when we don’t yet have a recommendation system. This is so that people are firmly in the understanding that Cara is about interacting with the community and finding a healthier frame of mind when thinking about socials. This way, when we do introduce recommendation systems, we will have existing users who can walk new people through the culture of the platform and help others understand. I’ve explained this reasoning in our first year, our second year, and I am again now. I think the users who were there for those moments before can attest that it works, and I want us to very carefully preserve what we’ve worked so hard to build. — Conclusion I am one person doing 20 people’s jobs, unpaid. I set aside all of my savings in case Cara needs it, to the extent I didn’t have the financial comfort of fixing my own health. I have to catch up on all the work I had to deprioritize due to focusing on Cara last year. I have to finish up a photobook that was due when I started Cara, for which I have a legal obligation to deliver. I am the lead plaintiff in 2 class action lawsuits against AI companies, which require me to routinely spend lengthy time reviewing legal documents.  People are used to things happening quickly and rapidly. I can understand getting used to the rate that other venture-funded companies can operate, I’m just saying that I am one person, and I cannot be 5000 people all at once, I’m not a machine.  Everything that was said about Cara here is understandable, and how you feel is absolutely valid. I hope by sharing things from my perspective, I’ve answered some of those questions and provided more context as to the reasons why we do certain things a certain way. I believe I have been above and beyond in being transparent, and me sharing my health issue is exactly why you can now say that you have lost confidence in Cara—which coincidentally, is the exact reason why companies often do not want to communicate things to the public.  I want to remain as transparent as I can. But there are a million things I may not share in public, whether it’s for security, legal, safety, or other reasons. But at least for why we may not be building a feature or doing something, trust that it’s usually a conscious decision made due to money, manpower, or the harassment we experienced before—and that we are doing all we can in the best way possible in the current moment, with thought for the longevity of the platform. — TLDR: I am confident about my decisions and directions for Cara. They are what brought us to where we are today. When people said we won’t have more than a few thousand users, we now have well over a million. I’m confident about the plans for the next million users, and millions after that. Right now, we just don’t operate at the same speed as everyone else.  I know that not actively promoting Cara on other platforms or recruiting users can feel like we’re missing something, but I assure you that it’s part intentional, part for good reasons. It’s so that we can build culture on Cara and not let it be overwhelmed by outsized traffic, and also because we need time and have to work within the limits of our manpower and funding in the moment.  It’s completely understandable if this point of view doesn’t work for everybody, ultimately, everyone should do what’s best for their business and themselves. I want to do the same for Cara, too, and will continue developing it according to the vision I believe is important, at a pace that’s sustainable and makes sense for us long term.   While we’re on the topic, for those who’d like to support us in saving up to hire a team, you can subscribe or buy us a coffee on Cara! - https://cara.app/coffee ☺️ And on the off chance a super wealthy reader is reading this, and would love to support Cara like it’s a lifestyle business and think that doing things counterintuitively is fun, please reach out!
  3. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Friday, 03-Oct-2025 06:38:17 JST Chee Aun 🤔 Chee Aun 🤔
    • Scott Jenson
    • Abraham Williams

    @abraham @scottjenson I start to iterate using “private” because both requires login. But I get your point on it being related to privacy stuff. Though we already have “Private mention” here 🙃

    In conversation about 9 months ago from mastodon.social permalink
  4. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Thursday, 02-Oct-2025 22:57:26 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    Stashing my dev notes here https://github.com/cheeaun/phanpy/discussions/1294 — probably useful for other devs too 🙇♂️

    Implementation is almost done; just 3 things:
    1. There's no way to test "Request to quote"
    2. QP filtered for limited accounts
    3. Post content is optional if there's CW and quote (doesn't seem to work on official site yet, will check later)

    In conversation about 9 months ago from mastodon.social permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
      Quote Post · cheeaun/phanpy · Discussion #1294
      Quote post Official docs: https://docs.joinmastodon.org/user/quote-posts/ Official PR: mastodon/documentation#1710 Basic cases Quote button/menu mastodon/mastodon#35822 Quotes count mastodon/mastod...
  5. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Thursday, 02-Oct-2025 22:57:25 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    RE: https://mastodon.social/@cheeaun/115242149735813956

    Seems like quotes will be viewable for other people's post (soon) https://github.com/mastodon/mastodon/pull/36301

    Previously, only limited to own posts.

    Docs updated: https://github.com/cheeaun/phanpy/discussions/1294

    In conversation about 9 months ago from mastodon.social permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
      Quote Post · cheeaun/phanpy · Discussion #1294
      Quote post Official docs: https://docs.joinmastodon.org/user/quote-posts/ Official PR: mastodon/documentation#1710 Basic cases Quote button/menu mastodon/mastodon#35822 Quotes count mastodon/mastod...
    2. Domain not in remote thumbnail source whitelist: files.mastodon.social
      Chee Aun 🤔 (@cheeaun@mastodon.social)
      from Chee Aun 🤔
      Attached: 1 image ✅ See quotes of a status https://docs.joinmastodon.org/methods/statuses/#quotes Turns out this quotes list is only viewable for own post and by self ("private"?). This means I can't view quotes of posts authored by other folks 🤔 This limited my experimentation a bit, thus the crude UI for now. It should paginate but I'll need more people to native-QP my posts 😂 Also throwing in a quick PR doc fix: https://github.com/mastodon/documentation/pull/1729

  6. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Thursday, 02-Oct-2025 22:57:25 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    Updated docs regarding attaching a quote with media and/or poll https://github.com/cheeaun/phanpy/discussions/1294

    - Mastodon: ✅ Quote ❌ Media ❌ Poll
    - Bluesky: ✅ Quote ✅ Media 🚫 Poll (doesn't exist)
    - X: ✅ Quote ✅ Media ❌ Poll
    - Threads: ✅ Quote ✅ Media OR ✅ Poll

    On #PhanpySocialDev , I'm testing Threads' route for now.

    In conversation about 9 months ago from mastodon.social permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: opengraph.githubassets.com
      Quote Post · cheeaun/phanpy · Discussion #1294
      Quote post Official docs: https://docs.joinmastodon.org/user/quote-posts/ Official PR: mastodon/documentation#1710 Basic cases Quote button/menu mastodon/mastodon#35822 Quotes count mastodon/mastod...
  7. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Thursday, 02-Oct-2025 22:57:25 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    I got it wrong. Quote notifications are no longer grouped. They'll have same UI treatment like replies/mentions.

    Combined grouped notification with other interactions (e.g. "X people boosted, quoted & liked your post/reply." or "[ACCOUNT] boosted, quoted & liked Y of your posts.") also doesn't make sense because quotes have their own posts. Boost/like points to Post A, but quotes points to Post B quoting Post A.

    In conversation about 9 months ago from mastodon.social permalink

    Attachments


    1. https://files.mastodon.social/media_attachments/files/115/281/441/237/209/920/original/c8fb3533e8d300ff.png
  8. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Saturday, 27-Sep-2025 10:33:19 JST Chee Aun 🤔 Chee Aun 🤔

    RE: https://mastodon.social/@ricmac/115271555614918116

    Thanks for the feature 🙇♂️

    In conversation about 9 months ago from mastodon.social permalink

    Attachments

    1. No result found on File_thumbnail lookup.
      Richard MacManus (@ricmac@mastodon.social)
      from Richard MacManus
      In this week's Web Technology News, I discuss my interview with Evan You — the creator of Vite and (I'm suggesting) one of the new rock stars of web development. https://webtechnology.news/wtn-8-the-new-rock-stars-of-web-development/ As usual, you'll also find other news in these 3 categories: Web Platform, Open Social Web, Web + AI. Fedi folk featured in this week's newsletter: @jaredwhite@indieweb.social, @cloudflare@noc.social, @_elena, @sia@front-end.social, @cheeaun, @deane@contenttechtodon.org You can sign up to WTN via email and/or follow @feed@webtechnology.news here on Mastodon.
  9. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Saturday, 27-Sep-2025 10:30:12 JST Chee Aun 🤔 Chee Aun 🤔
    • Tim Bray

    Had a quick thought about this: https://cosocial.ca/@timbray/115260431864647847 @timbray

    Found some resources:
    - "FEP-8967: Generating link previews for attached links" https://codeberg.org/fediverse/fep/src/branch/main/fep/8967/fep-8967.md
    - Discussion: https://socialhub.activitypub.rocks/t/fep-8967-generating-link-previews-for-attached-links/5598

    Randomly found this pretty interesting read: "Link Previews: How a Simple Feature Can Have Privacy and Security Risks" https://mysk.blog/2020/10/25/link-previews/ (2020)

    In conversation about 9 months ago from mastodon.social permalink

    Attachments

    1. No result found on File_thumbnail lookup.
      Tim Bray (@timbray@cosocial.ca)
      from Tim Bray
      @cheeaun@mastodon.social You know what would be cool? When I paste a link into a post, to find out whether it has a nice og: preview because, if not, I'll paste the headline in too. Just posted a link, included the headline, and now it appears twice in the post, looking kind of dumb.
    2. Domain not in remote thumbnail source whitelist: codeberg.org
      fep/fep/8967/fep-8967.md at main
      from fediverse
      fep - Fediverse Enhancement Proposals

    3. Domain not in remote thumbnail source whitelist: mysk.blog
      Link Previews: How a Simple Feature Can Have Privacy and Security Risks
      Link previews in chat apps can cause serious privacy problems if not done properly. We found several cases of apps with vulnerabilities such as: leaking IP addresses, exposing links sent in end-to-end encrypted chats, and unnecessarily downloading gigabytes of data quietly in the background. We think link previews are a good case study of how a simple feature can have privacy and security risks. We'll go over some of the bugs we found while investigating how this feature is implemented in the most popular chat apps on iOS and Android.
  10. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Saturday, 27-Sep-2025 10:28:56 JST Chee Aun 🤔 Chee Aun 🤔

    Been active here since Nov 2022. Seeing new followers past few weeks, so here’s my 1st (late) #introduction

    I’ve built a bunch of projects since 2002-ish https://cheeaun.com/projects/ . I also wrote some (very) long-form & super-detailed blog posts https://cheeaun.com/blog/

    I’m a #FrontEnd dev professionally since 2006, now based in Singapore. My 1st involvement in #OpenSource was with Mozilla/Firefox/Firebird/Phoenix when I created a 3rd-party (full) theme called #Phoenity

    In conversation about 9 months ago from mastodon.social permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: cheeaun.com
      Projects – Lim Chee Aun

  11. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Saturday, 27-Sep-2025 10:28:43 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    For grouped notifications, can test this for now: "[ACCOUNT] quoted Y of your posts."

    Another one would be: "X people quoted your post/reply."

    The ones where I'm starting to question my sanity 🫠🤪:
    - X people boosted & quoted your post/reply.
    - X people quoted & liked your post/reply.
    - X people boosted, quoted & liked your post/reply.
    - [ACCOUNT] boosted & quoted Y of your posts.
    - [ACCOUNT] quoted & liked Y of your posts.
    - [ACCOUNT] boosted, quoted & liked Y of your posts.

    In conversation about 9 months ago from mastodon.social permalink

    Attachments


    1. https://files.mastodon.social/media_attachments/files/115/264/448/696/652/024/original/b608c4ca322f4bb7.png
  12. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Saturday, 27-Sep-2025 10:28:43 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    Slowly integrating into other elements.

    Some issues need thinking:
    - Account's posts don't have `exclude_quotes` filter? Should it have such filter? https://docs.joinmastodon.org/methods/accounts/#statuses
    - Should searches have `has:quote` operator? Probably should add as feature request on #mastodon 🤔
    - Grouped notifications for quotes? https://docs.joinmastodon.org/methods/grouped_notifications/ — I could probably try this on client-side first
    - "Quotes" filter on Phanpy's Catch-up?

    In conversation about 9 months ago from mastodon.social permalink

    Attachments


    1. https://files.mastodon.social/media_attachments/files/115/264/238/978/597/465/original/480ff93abceaa46b.png
    2. No result found on File_thumbnail lookup.
      accounts API methods - Mastodon documentation
      Methods concerning accounts and profiles.
    3. No result found on File_thumbnail lookup.
      Grouped notifications API methods - Mastodon documentation
      Receive grouped notifications for activity on your account or statuses.
  13. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Saturday, 27-Sep-2025 10:28:43 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    RE: https://mastodon.social/@cheeaun/115253090886835774

    Testing if this works. #PhanpySocialDev

    In conversation about 9 months ago from mastodon.social permalink

    Attachments

    1. Domain not in remote thumbnail source whitelist: files.mastodon.social
      Chee Aun 🤔 (@cheeaun@mastodon.social)
      from Chee Aun 🤔
      Attached: 1 image Handle pasting post links 😮💨 Prompt to turn them into quotes only show if: - Native quote post is supported - They "look like" post links (same logic as non-native QP link unfurling) - Still respecting the quote policy of the post (same logic as enabling/disabling the Quote menu) - There's no media attachment(s) or poll
  14. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Saturday, 27-Sep-2025 10:28:42 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    Cool, works.

    In conversation about 9 months ago from mastodon.social permalink

    Attachments


    1. https://files.mastodon.social/media_attachments/files/115/273/261/264/769/430/original/6df9b4b4b7ab59f7.png
  15. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Saturday, 27-Sep-2025 10:28:42 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    A post with a native quote and a non-native quote that contains a nested native quote that contains another nested native quote 😮💨

    Non-native quotes on Phanpy shows a domain at the top, giving it a "link card/preview"-like appearance.

    In conversation about 9 months ago from mastodon.social permalink

    Attachments


    1. https://files.mastodon.social/media_attachments/files/115/268/092/497/510/969/original/520308d57bd428c4.png
  16. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Tuesday, 23-Sep-2025 20:36:20 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    Handling `quoted_update`-type notification.

    In conversation about 9 months ago from mastodon.social permalink

    Attachments


    1. https://files.mastodon.social/media_attachments/files/115/230/881/377/886/021/original/2f44acbde932a92b.png
  17. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Tuesday, 23-Sep-2025 20:36:20 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    Handling `quote`-type notification. #PhanpySocialDev

    In conversation about 9 months ago from mastodon.social permalink

    Attachments


    1. https://files.mastodon.social/media_attachments/files/115/230/448/974/640/058/original/f38eaa07c66cfb93.png
  18. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Tuesday, 23-Sep-2025 20:36:19 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    ✅ Change quote settings on a published post
    ✅ Removing your post from someone’s quote post

    The dev site #PhanpySocialDev will be quite unstable for now 🙇♂️

    Note to translators: don't need to hurry & translate everything now, copy could be added, changed or removed later 🙏

    In conversation about 9 months ago from mastodon.social permalink

    Attachments



  19. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Tuesday, 23-Sep-2025 20:36:19 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    ✅ Default quote policy settings
    ✅ Set quote policy while composing

    In conversation about 9 months ago from mastodon.social permalink

    Attachments


    1. https://files.mastodon.social/media_attachments/files/115/236/726/753/613/981/original/dab7e787e89a1755.png

  20. Embed this notice
    Chee Aun 🤔 (cheeaun@mastodon.social)'s status on Tuesday, 23-Sep-2025 20:36:19 JST Chee Aun 🤔 Chee Aun 🤔
    in reply to

    Not sure if this would make sense, or if other 3rd-party clients would do this.

    "Quote with link" = non-native quote. Copy is not finalised.

    The right way is probably use native quote if supported else fallback to non-native, instead of showing both at the same time. But would users still want to use non-native quote if native quote is not allowed? 🤔

    In conversation about 9 months ago from mastodon.social permalink

    Attachments


    1. https://files.mastodon.social/media_attachments/files/115/235/385/229/445/236/original/9e3194cef7ccf6d8.png

    2. https://files.mastodon.social/media_attachments/files/115/235/385/225/576/277/original/4d076bde111ccb7a.png
  • After
  • Before

User actions

    Chee Aun 🤔

    Chee Aun 🤔

    Product-1st Front-end Engineer, based in Singapore. On a (long) career break since July 2022. Working on a Mastodon web client https://phanpy.social @phanpyWhy follow me: I have interests in #WebDev, #design, #DataViz, #Maps, #PublicTransport, #stickers & #anime. I usually post about my side projects, tech events, weird discoveries, and sometimes local news.#fedi22 tfr #tech #JavaScript

    Tags
    • (None)

    Following 0

      Followers 0

        Groups 0

          Statistics

          User ID
          101551
          Member since
          25 Feb 2023
          Notices
          307
          Daily average
          0

          Feeds

          • Atom
          • Help
          • About
          • FAQ
          • TOS
          • Privacy
          • Source
          • Version
          • Contact

          GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

          Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.