renchap

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.

There are a few companies providing this, like https://masto.host and https://federation.spacebear.ee

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.

From the information I gathered, this is an incident in the GlobalSwitch datacenter in Paris.

The cooling system leaked, and this started a fire in an electrical room.

The big issue here is that one Datacenter failure brought the whole region down, this is very abnormal.

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.

[1] https://www.notos.co/

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.

Is this based on knative? It seems very similar :)

Excalidraw (https://excalidraw.com) just implemented collaboration, making it a free, secure and OSS solution for remote whiteboard :)

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.

S-1 (HTML): https://www.sec.gov/Archives/edgar/data/1517413/000119312519...

I really like h2o (https://h2o.examp1e.net) as a nginx replacement, very nice software, lot of features, extensibility using mruby and amazing perf.

libh2o is a library, h2o is a full fledged webserver using libh2o. They are both made by the same people and released together.

Having all the core features in a library allow any developer to use libh2o to easily add a webserver to their program.

note: this is explained in the first part of the link.

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.

[1] https://www.flickr.com/help/terms/api [2] https://developers.google.com/photos/library/guides/acceptab...

Thanks, this is exactly why we started working on Talegraph :)

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.

SmugMug is really bringing back sanity into Flickr, good to see this after the Yahoo fiasco.

I created Talegraph [1] as a platform to tell stories with your pictures, and it has been hard for us to explain to users why paying for the product is the only way to ensure your pictures will stay online and private. Paying for what you use & privacy is not something normal people are used to, but this is the only sustainable way imo.

[1] https://www.talegraph.com

This can happen with any provider, either due to policy, human error, malicious actor, ... The correct answer here is to use multiple providers and establish proper relationship with them.

5% of your worldwide revenue (not benefits) for lack on compliance on one issue? With others pending? I do think this is not something you can ignore very long.

This is the initial fine. Now they have 90 days to comply, otherwise they will get penalties (up to 5% worldwide turnover of Alphabet) until they do. From the link:

Google must now bring the conduct effectively to an end within 90 days or face penalty payments of up to 5% of the average daily worldwide turnover of Alphabet, Google's parent company.

Have you tried Newsblur? Its training feature is very powerful to trim down large feeds to only the topics you are interested into.

Connection pooling is recommended for any non-trivial PG deployment. I can recommend pgbouncer, worked flawlessly for us.

Finally! Nice to see more PG support. Any news about PostgreSQL 10 support?

I was hesitant at first, but it took me less than a week to adopt it and be convinced it makes it much painless and easier to write JS. I missed it when writing Ruby code, until I discovered Rufo [1], a (still young) Prettier-like formatter for Ruby. They are now both part of my toolkit, bot the best!

[1] https://github.com/ruby-formatter/rufo

Seems great! Any plans to include ssh and/or mosh?

It also depends on the platform you are on, the CPU vendor/model, the vulnerability you fix, and the patch you used.

As mentioned in the article, there are 3 different (identified) vulns, each with its own set of patches, and sometimes multiples different ways to patch. Each of those patch will have its own impact, and work is currently in progress to find new ways to patch that will have a lower impact on performance.

Also, this means we will need to be used to patch, as new vulns of this category will definitely be found, and new changes to kernels/cpu/compilers will be designed and will need to be applied.