you to see new comments throught STD community . Under each comment is context button , which shows you the context of the comment . You can also set RES to highlight new comments , so you dont need to search them complicatedly . <| sep |> I feel like we could be friends <| sep |> God damn she is annoying <| sep |> Submission Reize is a jerkGame Shovel KnightDescription Yay for bad RNG during a speedrun . Intro <| sep |> Oh wow , I had no ideaI also didn ' t know about the finger cutting thing , that ' s ridiculous <| sep |> And we ' ve always been at war with Eastasia . <| sep |> We know who Dave is <| sep |> That assumes you have a fair amount of control over how Gitlab serves data . The mechanism I gave works with anything you have , so long as you can select the port it uses . Naturally , if you can select a device for it to listen to , you don ' t have to bother with iptables . The HSTS header is clientside only . You must depend on the client honoring it . If you have a user who uses IE 10 which is only four years old , their browser won ' t do anything with the header . Checking the docs , though , gitlab already uses nginx as a proxy , and they have a tutorial for using letsencrypt with i t s e c u r i n g y o u r g i t l a b p ageswithtlsandletsencrypt . Still , if you have an application that you don ' t want to be accessible over HTTP , iptables plus reverse proxy will always work .