@pixelfed Will be limited to the official mobile app until we have full WebPush support (that will work with 3rd party apps)
As much as I'd love to ship initial support for 3rd party apps, the way that Laravel handles WebPush would limit it to one per user instead of one per auth token so it would only work with one app at a time (unlike Mastodon which supports multiple, which I want to emulate, but it will take add'l time)
@pixelfed Will be limited to the official mobile app until we have full WebPush support (that will work with 3rd party apps)
As much as I'd love to ship initial support for 3rd party apps, the way that Laravel handles WebPush would limit it to one per user instead of one per auth token so it would only work with one app at a time (unlike Mastodon which supports multiple, which I want to emulate, but it will take add'l time)
@pixelfed Will be limited to the official mobile app until we have full WebPush support (that will work with 3rd party apps)
As much as I'd love to ship initial support for 3rd party apps, the way that Laravel handles WebPush would limit it to one per user instead of one per auth token so it would only work with one app at a time (unlike Mastodon which supports multiple, which I want to emulate, but it will take add'l time)
I think this is a good compromise for now!
➡️ https://github.com/pixelfed/notify
@pixelfed Will be limited to the official mobile app until we have full WebPush support (that will work with 3rd party apps)
As much as I'd love to ship initial support for 3rd party apps, the way that Laravel handles WebPush would limit it to one per user instead of one per auth token so it would only work with one app at a time (unlike Mastodon which supports multiple, which I want to emulate, but it will take add'l time)