But yeah, if you need a predictable way is either APN or safari push notifications.
130 karma · joined March 4, 2017
But yeah, if you need a predictable way is either APN or safari push notifications.
The trade off is that you gain some extra privacy with simpler architecture and accept that some notifications will be delayed as ios decides when to run the bg job for the app.
source: I develop e2e app with self-hostable server (145 lines of zero deps python for the whole server).
The implementation depends on OpenSSH, Python, Docker and age. Highly trusted / audited / scrutinised / maintained code. This fits well with e2e messaging infra.
For the local sync, I needed sqlite and python comes with sqlite client in a standard lib, ruby requires a gem.
I wanted core parts of the infra (relay and sync) to be implemented with zero external language dependencies. I didn't want to have a relay in ruby and sync in python. TUI example uses textual, so everything fits in a single language.
> Communicate with people you trust, away from the eyes of modern surveillance and large corporations.
I hope this answers your question.
They do, some build to rent indefinitely or sell to other who rent out the property.
If I spend $20m on building a house or creating a computer game, why house can be inherited indefinitely and creative work is not? I would have a monopoly on this specific building and on this specific creative work, but anyone is free to build/create anything else.
If J. Rowling created Harry Potter universe, why her family can't own it indefinitely? We somehow accept this notion for other assets, but treat copyright differently.
p.s. creative work is more valuable as it has something that money can't buy (authenticity, taste, sincerity, etc)
> Copyright is a monopoly that the government creates on purpose
Creative work takes a lot of effort and resources (ex: movie production, games, books (hello Knuth)) and can be easily copied/imitated in a digital age.
It you think copyright should be shorter to everyone, then inheriting something valuable shouldn't be a thing as well?
Also, here is what Pavel Durov mentioned recently in interview to Tucker Carlson
> In the US you have a process that allows the government to actually force any engineer in any tech company to implement a backdoor and not tell anyone about it with using this process called the gag order.
It doesn't matter what anyone claims on the landing page. Assume if it's stored somewhere, it'll get leaked eventually and the transitioning/hosting government already has an access and decryption keys.
> The police collected bags of clothes the girl had saved as evidence, but lost them two days later. The family was sent £140 compensation for the clothes and advised to drop the case.
p.s. the pricing section is unreadable under the 840px width
I saw variants of this phrase a lot, but I don't think it's accurate. I wouldn't be surprised if 0.55 would be close to a payment processing fee alone.
My very rough estimate is frappucino costs close to $5 to make. I used Starbucks located in Manhattan, New York to make it even more cliché.
- Ingredients & disposables: $1.03
- Direct labor (including shift supervisor): $1.30
- Occupancy (rent, insurance): $1.54
- Equipment depreciation: $0.14
- Utilities: $0.10
- Supplies, cleaning, waste: $0.10
- Management, marketing, investment: $0.60
- Card processing, other: $0.16
Total: $4.97
When surveying potential users I discovered that most are happy with the web gmail interface and don't really care. It sounds like a very niche requirement and it'll be very challenging to find enough customers (1k+) who would care about using a very nice email client.
The problem you're trying to solve is not that features get more prioritisation, but your estimations doesn't reflect the reality and your code-review process is broken as engineers are not spotting growing technical debt and refactoring opportunities and think that someone should give them a permission or create a ticket to work on that.
This is engineering culture 101 (look up the boyscout rule in software engineering).