Untitled attachment

Notices where this attachment appears

1. Embed this notice
   Daniel Supernault (dansup@mastodon.social)'s status on Thursday, 13-Feb-2025 18:33:40 JST Daniel Supernault

   The way people want to share posts via DMs in the Pixelfed app is on my todo list.

   It will be much easier to convince your friends and people to join Pixelfed once we have feature parity for Close Friends, Stories, DMs and Group Chats.

   Sup is a strategic play, it's all about the network effect ⚡️

2. Embed this notice
   alcinnz (alcinnz@floss.social)'s status on Thursday, 14-Nov-2024 03:50:54 JST alcinnz

   in reply to

   Meson writing a Ninja buildfile will (whilst generating comments) insert rules to tell Ninja when to reinvoke Meson, iterates over all compilations (within an iteration over all configured machines) to generate their build rules (generating a single extra one for Clang), generates configured-machine static-linking rule, do the same for dynamic linking, & adds a handful of boilerplate rules. A dict is used to deduplicate, as we populate a list.

   It creates an out-of-date "phony" build target.
   2/3

3. Embed this notice
   Hawkwinter (hawkwinter@mementomori.social)'s status on Friday, 28-Jul-2023 01:05:05 JST Hawkwinter

   in reply to

   @SolSoCoG

   As I mentioned though, I do think the idea of a shared blocklist is a good one. And I'm on .art and quite like the people there so far.

   But the implementation... I want to know I'm being reasonable, and that means I need to be able to skim through the entire block list and see the documentation for each block on that list.

   It's possible I would agree with every block on the list. But I would need to read the documentation to know.

   {I spent a good 40h researching instances and fedi-software before I made my first fediprofile. I'm just someone who wants to make sure I'm making the right decisions.}