Gregory's Server
|
Also, just want to point out that @pixelfed has an intuitive Server Directory feature built-in. You can submit your server to https://pixelfed.org/servers from your admin dashboard And I built in the other side into https://pixelfed.org so I can review and approve/reject server directory listings. Currently working on the https://pixelfed.org dashboard, making it easier for me to manage our server directory. Although I'm the only person who ever uses this, I wanted to share this so you can see how I have to balance my time between core dev, app dev and ecosystem dev. I know the app store launch is important, and is my main priority, but at the same time, our ecosystem depends on services/tools like these. It's all about balance 😎
Show previous comments
  @dansup Tooling is HIGHLY underrated. You can build it, but without having tools to maintain it you're pretty much hosed. You'll wind up building them regardless to save your sanity. @dansup doesn’t it go against the fediverse idea that one person controls the more or less central hub of such a part of the system? (The directory/listings) It’s raining, and I don’t feel like coding tonight so imma color this if I can find some pencil crayons. Results will be on my pixelfed @dansup@pixelfed.social #trixieAndKatyaColoringBook There are so many interesting problems to solve with regards to @pixelfed and scaling/performance One example is how I'm debating weather to keep a full redis sorted set of followers for each account or just a hundred and use db for pagination (when appropriate) to reduce RAM and make more room for other features. It's basically a game of whack a CRUD where you're hitting bottlenecks with cache but then cache become bottlenecks 😅 @dansup @pixelfed initially just let your DB handle caching for those situations, it is made for it. Of course that does require proper queries and decent indexes. PostgreSQL is great for that reason as it has the analysis/explains where one can update things. Adding a redis etc, is side cache, allowing your DB to cache more can be more than enough. Less moving parts, less cache inconsistencies. Pixelfed v0.11.9 is out and packs some powerful features! ✨ Import from Instagram And yes, it's only been 2 months since v0.11.8 was released, it's been a productive summer ☀️
Show previous comments
Pixelfed does support disabling comments, and it even federates, but it doesn't prevent comments from Mastodon and other implementations. We're working on better comment controls, and look forward to working with Mastodon and others on compatibility. #activitypub #comments #commentControl
Show previous comments
Comment control is really needed, I should be able to stop these two "passionate" people from arguing in my comments   Don't mean to sound like a broken record, but honesty, integrity and trust are super important to me I probably share too much, and more importantly, I've realized how freeing it is to be vulnerable and open, and to be able to publicly acknowledge your faults I'm not ashamed of my drunken rants about how much I love the fediverse, or how we can improve it Y'all keep me grounded, and I love that. This here, what we're building, can last generations, if built properly.  @dansup Mate I love how open you are with Pixelfed dev. I wish certain other open source project devs would be more like you. @dansup In my book it's a sign of true maturity when a person is confident enough in their strengths that they don't feel the need to cover up or deny their faults and weaknesses. Many people live out their lives being afraid of appearing weak if they ever acknowledge they made a mistake or are simply not that good at something (or anything). Deleted that last post because I don't want to be petty, or use my following in a detrimental way, I won't sink to their level. Anyways, everything is going amazing and I didn't mean to bum anyone out, I just was embarrassed that NLnet has to deal with this on my behalf. I wish I could make everything better between me and my haters, and I admit I'm not perfect and I'm open to feedback and opinions, it's how we grow, but I will remain focused on my goals. This is #pixelfedSzn 😎
Show previous comments
@dansup @pixelfed per-account & instance ranking and build a trust graph and cluster things. Spambots tend to follow spambots, thus they cluster together, normal people tend to follow the same normal people.... this is a method used many times before (pgp web of trust is one example) it does require knowing the full graph for involved accounts, thus that can be harder. I am sure somebody comes up with a trustrank service that can give out a score; then multiple services and if x/y deprio ;)  @dansup @pixelfed i've been very lucky i guess, only saw spam once and it was a mass spam attack that hit eveyone - was over as quickly as it started on #ElmosFolly i was having incessant DM spam for months -- just one more reason i do not miss what its turned into I'm not against adding monetization features in @pixelfed, but only if they work for users and give them 100% of any profit/proceeds. The easiest way for this is to allow and embrace external links to your own store/platform. We don't need crypto or some other form of payment in exchange for impressions because we don't have ads, and we aren't in this for money. A platform for the people, by the people, can thrive this way I think!
Show previous comments
@dansup each instance should have the option to allow or disallow this, but the “easiest” option would be to give the user the option to offer subscription levels to their followers and allow them to classify their post to different subscription levels. The hard part would be the integration of payment providers (flexibility) by the end-user themselves Started working on something only to find a performance issue in a @pixelfed background job that warms redis sets with follower ids, those with many followers cause the job to timeout and stuff like this is hard to catch until you reach a certain scale. Love solving these and I can’t stress enough to other fedi devs, there is no such thing as premature optimization when you build something that will integrate with an ecosystem with millions of users. Plan your database schema with this in mind! Pixelfed's official app will target iOS release first Sup will target Android first, with the ability to build your own APK from source (eventually FDroid) I have my reasons, will explain more later, for now those are my two biggest priorities atm (along with Groupies)  |
User invites, group invites, 2FA + oauth, federated interactions, there are so many related features this will ship along!
Not to mention this will significantly improve the performance of every route as we'll be eliminating two middlewares that are called on every request!
@dansup thank you for all your hard work
@dansup things are coming along nicely!