For Mastodon, each mobile app developer needs to have a "webpush relay server" to receive Mastodon's webpush notifications and transmit them to the platform's push service. For Android, Mastodon recently added support for the latest webpush standard which allows the app developer to directly register Google's webpush endpoint with Mastodon, removing the need for a relay.
In all cases, push notifications are encrypted by the Mastodon server, and decrypted by the Mastodon client, so any intermediaries (relay server, push notification service) can not read their content.
The content warning styling may be reverted (its already done in `main`), and we are not aware of any performance issues with 4.3, it's in fact the opposite from all the feedback we got. I am really curious of what is happening here and asked the admin to provide more information.
Our operating structure is still the Germany-based Mastodon gGmbH. The new US non-profit is here to facilitate fundraising in the US and promote Mastodon there (plus maybe one day pay developers directly, if we hire in the US).
We have been a non-profit since Mastodon gGmbH has been founded and our biggest issue is our lack of funding to hire more people full-time, not politics or admin overhead. We do not expect this to change anytime soon.
We (the Mastodon non-profit) do not offer support contracts at the moment, but this is a good idea, thanks :)
But we indeed have sponsorships open, and they really have impact. Having full-time people working on the project is very impactful, but at the moment we only have 1 full-time developer in addition to Eugen (the founder) and a DevOps person on the technical side.
This is why we are building Notos[1], most of the photo sharing websites evolved in social networks (or died).
We chose to not make our user's album public by default, where most competitors are doing so and benefit from the SEO involved, but we want to focus on sharing with family and friends, not the whole world.
Now the elephant in the room is monetisation and getting people to pay for their usage, this is not easy but we firmly believe it can be done but probably not with a trajectory allowing you to raise VC money.
You can have a try at https://www.notos.co/ for the privacy-minded sharing part. This is my main focus for the product.
No mobile app (yet) or sync as backups and sharing require very different products and my focus is on the later for now.
This is quite big for businesses in the EU. You used to require external tools to emit invoices & handle VAT, now everything should be doable from Stripe, with no fees.
I had a look at the API and it seems you still need to assign the correct VAT rate yourself (importing VAT rates from the official websites, and assign the correct rate to your items), where it could be automated: "my customer is in country X, I am selling electronical goods, please apply the correct VAT". But this is a very strong first step!
SCA transition for recurring changes will also be automatically handled, one less hurdle to go through.
Thanks!
I plan to add tracks to the maps feature. I only added maps recently and this is the next logical step. I did not know about OwnTracks but I definitely plan to allow importing external GPS data, in addition to EXIF GPS data.
For the data export, this is definitely planned. I can do it manually right know if you ask for it, but creating a process to do it automatically is not the top priority. But we will not shutdown or be acquired before this is in place. I got screwed too many time by other SaaS who just disappeared so I dont want to repeat this with my users.
Yes this could work, and even if the API terms do not allow it (ie Google Photos API do not allow you to download the pictures for storage) you can use the Data Export feature that most websites have and use this export to upload back your data elsewhere.
I would love to do it, but unfortunately most APIs forbid imports and only allow you to store pictures for caching purposes (Flickr [1], Google Photos [2]) and have restrictions / heavy fees for commercial usage.
Dropbox import is planned, I havent looked at SmugMug API's terms yet but will add it to the todolist.
When you look at the comments on Reddit, you can see that unfortunately it does not make sense for many people who put free as their first priority, versus privacy/sustainability/data concerns.
Very brave for Flickr to make this move and face all those critics, even if this is for the best on the long term.
Co-Founder/CTO @ Notos (notos.co) - Transform your pictures into beautiful stories
Mastodon: https://oisaur.com/@renchap
[ my public key: https://keybase.io/renchap; my proof: https://keybase.io/renchap/sigs/drIcbkhRm9hAT34Xsja9Qh_pzx40k7WsOgTpvo0JICU ]