diff --git a/src/BirdsiteLive/Controllers/AboutController.cs b/src/BirdsiteLive/Controllers/AboutController.cs new file mode 100644 index 0000000..f9a015d --- /dev/null +++ b/src/BirdsiteLive/Controllers/AboutController.cs @@ -0,0 +1,26 @@ +using Microsoft.AspNetCore.Mvc; +using System; +using System.Collections.Generic; +using System.Linq; +using System.Threading.Tasks; + +namespace BirdsiteLive.Controllers +{ + public class AboutController : Controller + { + public IActionResult Index() + { + return View(); + } + + public IActionResult Blacklisting() + { + return View("Blacklisting"); + } + + public IActionResult Whitelisting() + { + return View("Whitelisting"); + } + } +} diff --git a/src/BirdsiteLive/Views/About/Blacklisting.cshtml b/src/BirdsiteLive/Views/About/Blacklisting.cshtml new file mode 100644 index 0000000..bf92930 --- /dev/null +++ b/src/BirdsiteLive/Views/About/Blacklisting.cshtml @@ -0,0 +1,12 @@ +
+ This node is using blacklisting.
+
+
+
TODO
+
+ This node usage is at XX%
+
+
+
BirdsiteLIVE rely on the Twitter API to provide high quality content. This API has limitations and therefore limits node capacity.
+ +When the saturation rate goes above 100% the node will no longer update all accounts every 15 minutes and instead will reduce the pooling rate to stay under the API limits, the more saturated a node is the less efficient it will be.
+ The software doesn't scale, and it's by design.
If you're not on your own node, be reasonable and don't follow too much accounts. And if you can, host your own node. BirdsiteLIVE doesn't require a lot of resources to work and therefore is really cheap to self-host.
+
+ This node is using whitelisting.
+
+
+
TODO
+