Surely, you're not suggesting invading a nuclear power to seize their natural assets.
As part of an embeddable video player I'm starting to build, I need to have some way of keeping track of viewer behavior.The easy way is to integrate something like Mux (YC Winter 2016). The even easier way is to just use an existing player like video js. But I want to start off by building my own solution.I have the basic player working (still some race conditions to be resolved), so now I am...
Hypothetically, consider a social photo platform - each pic gets its own url, this page contains the image, text about the image, buttons for the user to click, related pics, and some user-specific elements (maybe notifications, etc.).There are different ways of going about the frontend. In each case, elements specific to the logged-in-user and the related images get fetched via api calls and...
Check also the list here https://pixensity.com/list/desktop/
The 5K Apple display has around 215ppi. There are 5-6 displays with higher ppi than the one from Apple.
Now I think lxd is supposed to be a better user experience than lxc. Same backend better frontend. Like ezjail or iocage for FreeBSD makes the management easier than doing it all directly.
All of the 8K displays have a higher ppi than the Apple 5K display (215 ppi).
The point of a retina display is to have a higher pixel density than the human eye can distinguish (at a certain distance).
There are many displays that have far higher pixel density than the iPhone.
According to the list here https://pixensity.com/list/phone/ there are/were at least 40+ non-Apple phones with higher ppi than the iPhone X
I understand the meaning and significance of testing the key assumptions,In order for the idea to be viable, the key assumptions must hold true. These key assumptions need to be validated in initial user research (in my own words).But I am somewhat at a loss in listing out what the key assumptions actually are. For me it is just the solution to a problem that annoys me.Any tips or links to...
Using passwordless (key only) login is a given.
As soon as your server is provisioned, log in with the password, first setup ssh, and disable password login.
You can use fail2ban jails for different services (like nginx). You need to decide how strict you need to be.
On FreeBSD, using blacklistd might also be a better idea than using fail2ban.
To quote from the internet - "fail2ban and sshguard are both log scrapers. Log scrapers are gross hacks. blacklistd as an integrated solution is what should have happened many years ago."
FreeBSD jails also provide excellent protection. It can be a good idea to run each service in its own jail. E.g. a separate jail for nginx, one for your webserver, another for your db servers. This way you can also limit the resources that are allocated/dedicated to each jail.
Also, while running pf (or whatever firewall you have), you can limit the number of requests (rate limiting) to somewhat protect yourself.
Using Cloudflare or something else on the front can help against ddos. Also, some providers like OVH and Hetzner have ddos protection built in for free. Some like Vultr have it as a paid service, iirc.
After hearing/reading about the negative experiences many people have had with upcoming graph databases, I am wary of jumping into a graph db. But almost any modern application has things that will be suited to a graph representation.So I am considering a workaround to use a graph structure, but represent the underlying data in a reliable rdbms, in particular postgres.The approach is: 1. Make...