Awesome, thanks for doing this!
You can just have a Credits/Licenses page in your legal section that lists these packages. If you’re using npm packages, you could use an npm package like nlf or license-checker to compile a list of all licenses in your dependencies
Welcome! 🎉
Oh wow, thanks for sharing. Hadn’t heard of that yet, it definitely makes it possible but that syntax will take some getting used to
What doesn’t line up is that most other operating systems including macOS support PWAs with different browser engines. That along with the fact that Apple announced this at the bottom of an article hidden under a collapsed menu, it really makes it seem like they’re trying to find an excuse to get rid of them without damaging their brand reputation. It’s no secret how profitable the App Store ecosystem is, and this is one more way they can pressure developers into it while shifting the blame to the EU
Yeah of course, I’m a web dev so prepare for a partial rant :)
PWAs have kinda felt like that thing Apple has reluctantly kept around to show the world that they aren’t trying to lock you into their App Store ecosystem. They’ve always been slow to implement new PWA features and address bugs (they just added notifications last year while it’s been supported on other devices for a while now). They drip-feed developers just enough PWA features and fixes to keep their brand image up, but not too much to where it could grow to threaten to their App Store profits.
Now, it feels like they finally have someone else to blame for getting rid of PWAs so they don’t look bad doing it themselves. It’s the moment they’ve been waiting for. They can keep their brand image looking good, and cut something out that has the potential to affect a bit of their profits. I would not be surprised if they start incrementally dropping PWA support the next chance they get.
Now, the only way to release an app-like experience for EU customers (one with notifications and other native features) is by going through their App Store ecosystem in some way. Meanwhile, macOS has PWA support and the ability to use whatever browser engine you’d like.
Granted, I haven’t looked in-depth into what these new policies are requiring of Apple, but for those of us that have spent years wresting with iOS Safari (sometimes called the new Internet Explorer) it sure leaves a bad taste. At the very least, it’d be nice to have some resources and recommendations from them beyond a small announcement/apology inside a collapsed menu at the bottom of a page.
From what I’ve seen It’s mostly been:
- New Lemmy users trying to find an app
- People looking for an app with specific features
- New app announcements
- Bigger releases and changes to existing apps
I think that content all depends on how many users and apps there are—not much you can do about that.
Maybe we could have a monthly post asking people what they want in Lemmy apps (features, ideas, likes and dislikes)? That might be a good way to bring all devs and users together to think of ways to make the ecosystem better
That’s a really important distinction, thanks for clarifying
You can always block those instances for yourself in your settings
Edit: Sorry, sounds like your instance doesn’t have that yet but is getting an upgrade soon that will enable that feature
Thanks for hearing us and continuing to allow all types of apps here. FOSS is an amazing model for some projects, but some of us simply want to protect the rights of what we create or we’re looking at other models to help Lemmy become more sustainable
Keep in mind it can take a few minutes or longer for some votes to come in from other instances due to how federation works. Sometimes a group of votes can get backlogged and all come in at once. Other times they’ll show instantly. It’s just a minor tradeoff to using decentralized social media