I tried it, I really like it but for some reason, there were a few times when the tabs stopped responding to clicks, which forced me to kill the process. I understand that it's still very new, I imagine it will only get better :)
🔍 Looking for recommendations: Multi-gateway payment integration library/package for Laravel or at least for PHP
Building an app where admins can select & configure their preferred payment gateway to process user payments. Need to integrate multiple providers (Stripe, PayPal, Mollie, Moneris, etc.). Laravel Cashier is out since it only handles Stripe/Paddle. Found OmniPay and Payum but they seem outdated/unmaintained.
Seeking a modern, actively maintained solution - either an existing package or guidance on building a custom abstraction layer. Any suggestions from the community? Thank you Pinkary!
Hello Pinkary! Which password manager should I use in 2025? After LastPass's security issues, I'm looking for safer alternatives. What would you recommend?
•
I understand Pinkary isn't meant to replace major social networks, but it has some blind spots that should be addressed.
Recently, we've seen multiple posts from an enthusiastic user, and the newsfeed algorithm prevents this person from freely creating content on their Pinkary page without flooding the global feed.
Since Pinkary also serves as a link repository (similar to Linktree), it would be valuable to let users post content or snippets without overwhelming others when someone simply wants to build their profile.
How could we improve the app to enable free content creation without impacting everyone else, while still preserving user enthusiasm and creativity?
Some ideas:
- Improve feed to show less posts from the same users in a row
- Separating profile posts from feed posts
- Adding content visibility settings
- Letting users customize their feed content
- Creating dedicated spaces for different content types
- Prevent the creation of too many posts in short time
•
I understand it would be possible for someone to adapt Pinkary's code before using it as a foundation for their social network to add their own features. And that's what's great about Laravel - it would indeed be possible to add packages. But for the core, the base system, out-of-the-box perhaps certain features should be there by default?
For example, some personal settings regarding what we want to see on the default page. @nunomaduro suggested potentially changing the default view to display "Following" which would be a good idea except for people who follow few users and newcomers. Maybe a user preference?
And indeed, blocking and/or muting users would certainly be a must, to prevent further episodes of flooding by any hyperactive and ultra-motivated user, or let's hope this never happens, spammers.
It's a delicate balance between keeping the platform lightweight and adding basic features...
Excited to share my first Laravel package - SafeName!
As a Laravel dev, I've often needed to prevent users from registering with reserved usernames like "admin" or "moderator". On platforms like this one, this is crucial to avoid impersonation and maintain trust.
SafeName makes this easy by providing both exact matching ("admin") and partial matching (blocking "admin123", "superadmin", etc.). I've included a curated list of commonly abused terms, but you can easily customize it for your needs.
Check it out on Packagist:
packagist.org/packages/quebecstudio/safename
Let me know what you think! Always open to feedback and contributions 🙌
(Yes, I developed this with in mind exactly the observations we made today...)
•
This is a very good compilation! Though, my package is mostly intended for filtering-out misleading usernames, of course it can be a good idea to implement profanity and brandnames protection as other validation rules. I will think about this :-)