flipace

[
  { "name": "Amazon", "url": "https://www.amazon.de/gp/help/customer/contact-us?", "note": "Select, in this order: 'Digitale Dienste' -> 'Datenauskunft beantragen' -> 'Datenauskunft für eine spätere Zusendung beantragen' -> 'Daten aus allen Kategorien anfordern' -> Namen eingeben und Nachricht vervollständigen. -- Amazon Support Staff will review your request and send you an email, asking about a postal address. If you don't answer to their mail, your request won't be fulfilled." },
  { "name": "McDonalds", "url": "https://corporate.mcdonalds.com/corpmcd/gdpr-rights-center.html" },
  { "name": "willhaben.at", "url": "https://datenschutz.willhaben.at/" },
  { "name": "Spotify", "url": "https://www.spotify.com/account/privacy/" },
  { "name": "Google", "url": "https://takeout.google.com" },
  { "name": "PlayStation", "email": "[email protected]" },
  { "name": "Humble Bundle", "email": "[email protected]" },
  { "name": "REWE Group AT", "email": "[email protected]" },
  { "name": "BILLA", "url": "https:

punitsoni

How to use gpg to securely store your api keys

When you are using a third-party api in your application code. it usually requires you to supply some secret client information when making requests. if your code is opensource or accessible by a lot of people, putting these keys directly in code in plaintext can be a security issue.

One approach that i have seen in the wild is to use os environment variables to store the secrets and your app code can query the environment when starting up. this still requires someone to set up the environment in your server when

lf-araujo

Lunarvim R-IDE

Lunarvim settings for R statistics with neovim as an IDE.

--[[
lvim is the global options object

Linters should be

oca159

[
	// Terminal
	{
		"context": "Workspace",
		"bindings": {
			"ctrl-/": "workspace::ToggleBottomDock"
		}
	},
	// Window's navigation
	{