# We're back! for now

**URL:** <https://cog.discourse.group/t/were-back-for-now/1919>\
**Category:** meta\
**Created:** [June 2, 2022, 11:30am UTC](https://cog.discourse.group/t/were-back-for-now/1919 "2022-06-02T11:30:15Z")\
**Posts on this page:** 19\
**Page:** 2

<div class="post-metadata">

**Author:** ![balance](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/balance/32/1888_2.png) [@balance](https://cog.discourse.group/u/balance)\
**Post date:** [June 25, 2022, 12:22am UTC](https://cog.discourse.group/t/were-back-for-now/1919/21 "2022-06-25T00:22:06Z")

</div>

I’ll chip in a bit too.

---

<div class="post-metadata">

**Author:** ![RRabbit42](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/rrabbit42/32/79_2.png) [@RRabbit42](https://cog.discourse.group/u/RRabbit42)\
**Post date:** [June 25, 2022, 9:23pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/22 "2022-06-25T21:23:17Z")

</div>

I think I can match what TechnoMistress is proposing. My finances have been looking a lot better recently.

---

<div class="post-metadata">

**Author:** ![Lee\_Ars](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/lee_ars/32/2338_2.png) [@Lee\_Ars](https://cog.discourse.group/u/Lee_Ars)\
**Post date:** [June 26, 2022, 4:18pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/23 "2022-06-26T16:18:07Z")

</div>

(Apologies for this morning’s downtime. I did a dumb thing. The dumb thing has been un-done.)

---

<div class="post-metadata">

**Author:** ![Force10](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/force10/32/1550_2.png) [@Force10](https://cog.discourse.group/u/Force10)\
**Post date:** [July 14, 2022, 4:26pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/24 "2022-07-14T16:26:27Z")

</div>

> [@Lee\_Ars](#):
>
> I did a dumb thing. The dumb thing has been un-done.

Happens to the best of us.

---

<div class="post-metadata">

**Author:** ![Ook](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/ook/32/72_2.png) [@Ook](https://cog.discourse.group/u/Ook)\
**Post date:** [July 15, 2022, 12:33pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/25 "2022-07-15T12:33:34Z")

</div>

As long as dumb things lessons can be used in order to avoid more dumb things in future.

---

<div class="post-metadata">

**Author:** ![Ook](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/ook/32/72_2.png) [@Ook](https://cog.discourse.group/u/Ook)\
**Post date:** [September 17, 2022, 8:38am UTC](https://cog.discourse.group/t/were-back-for-now/1919/26 "2022-09-17T08:38:47Z")

</div>

An update on The Register :

> **[Appeals court upholds Texas social media moderation law](https://www.theregister.com/2022/09/16/texas_social_media_law_appeal/)**
>
> Big Tech forbidden from taking down 'viewpoint-based' posts no matter how awful but lawful

---

<div class="post-metadata">

**Author:** ![Lee\_Ars](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/lee_ars/32/2338_2.png) [@Lee\_Ars](https://cog.discourse.group/u/Lee_Ars)\
**Post date:** [September 18, 2022, 12:16am UTC](https://cog.discourse.group/t/were-back-for-now/1919/27 "2022-09-18T00:16:58Z")

</div>

Yeah. Pondering, but will likely take things down again pretty soon.

---

<div class="post-metadata">

**Author:** ![Nabiki](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/nabiki/32/935_2.png) [@Nabiki](https://cog.discourse.group/u/Nabiki)\
**Post date:** [September 18, 2022, 12:45am UTC](https://cog.discourse.group/t/were-back-for-now/1919/28 "2022-09-18T00:45:28Z")

</div>

I’m going to have basic internet after next weekend. I don’t have a computer right now, but one thing at a time.

---

<div class="post-metadata">

**Author:** ![Ook](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/ook/32/72_2.png) [@Ook](https://cog.discourse.group/u/Ook)\
**Post date:** [September 18, 2022, 7:11am UTC](https://cog.discourse.group/t/were-back-for-now/1919/29 "2022-09-18T07:11:20Z")

</div>

It is understood. No problems from my side.

You gotta do what you gotta do.

---

<div class="post-metadata">

**Author:** ![e4tmyl33t](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/e4tmyl33t/32/1122_2.png) [@e4tmyl33t](https://cog.discourse.group/u/e4tmyl33t)\
**Post date:** [September 18, 2022, 2:17pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/30 "2022-09-18T14:17:01Z")

</div>

To those about to disappear into the void, I salute you.

---

<div class="post-metadata">

**Author:** ![Nabiki](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/nabiki/32/935_2.png) [@Nabiki](https://cog.discourse.group/u/Nabiki)\
**Post date:** [September 18, 2022, 2:25pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/31 "2022-09-18T14:25:02Z")

</div>

There is a CoG Discord server. [Chronicles of George](https://discord.gg/KkuY68rT)

---

<div class="post-metadata">

**Author:** ![Rizak](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/rizak/32/4190_2.png) [@Rizak](https://cog.discourse.group/u/Rizak)\
**Post date:** [October 8, 2022, 11:14am UTC](https://cog.discourse.group/t/were-back-for-now/1919/32 "2022-10-08T11:14:44Z")

</div>

Discord is irritating me. It recognizes that I’m logging in from a new location and wants to send me an email to verify. The link in the email is time limited and I don’t get the email until long after that period has elapsed. It’s a 30 minute delay, at least.  
I’m sure I’ll get it worked out eventually.  
Still, grrrr.

---

<div class="post-metadata">

**Author:** ![Lee\_Ars](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/lee_ars/32/2338_2.png) [@Lee\_Ars](https://cog.discourse.group/u/Lee_Ars)\
**Post date:** [October 14, 2022, 1:25pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/33 "2022-10-14T13:25:33Z")

</div>

[Texas law back on hold for the Supreme Court to consider it](https://www.techdirt.com/2022/10/13/texas-ridiculous-content-moderation-bill-put-on-hold-until-the-supreme-court-can-consider-it/), along with a similar but different Florida law. Techdirt’s take is dead-on accurate:

> Normally, this wouldn’t be surprising, and normally, this wouldn’t even require a blog post, but because nothing in the 5th Circuit makes sense these days, it is a little surprising and it is worth a post to note that despite the insanity of Judge Andy Oldham’s ruling putting Texas’ content moderation law back on the books, he has now agreed to put that ruling on hold while the parties ask the Supreme Court to hear the case.
> 
> Again, such a thing is pretty standard in lots of cases, but this is the case where, back in May, Oldham decided to say that the law should go into effect immediately without any explanation at all. That necessitated a rush to the Supreme Court’s shadow docket, where the justices put the law on hold, in order to allow the regular, normal procedure to take place. As you’re well aware, months later, Oldham finally came out with his batshit crazy decision that required Oldham to ignore a century’s worth of precedent, as well as decades worth of conservative 1st Amendment orthodoxy in order to argue that the 1st Amendment’s association rights no longer apply to social media.

I have absolutely zero faith that this activist supreme court will do the right thing, because leaning into the bullshit lie of “conservatives are censored for their beliefs!!!oneoneeleventy!!!” resonates with people too stupid to understand how the 1A actually works, and those people vote (R). Constitutionality is something that lately the right only pays lip service to when it furthers their agenda of consolidating power and destroying democratic norms.

Still planning on divesting the forums onto a volunteer at some point at or around the end of the year, though. With the judicial landscape looking like this for the foreseeable future, it’s only a matter of time before moderating disinformation on the internet becomes criminalized by the people whose positions depend on that disinformation. (That’s folks like Ken Paxton and Greg Abbott.) And I’m not getting sued by some fucking mouthbreather who’s angry I deleted his lie-posts about the 2020 election being “stolen.”

---

<div class="post-metadata">

**Author:** ![Road\_Rash](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/road_rash/32/147_2.png) [@Road\_Rash](https://cog.discourse.group/u/Road_Rash)\
**Post date:** [October 14, 2022, 4:11pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/34 "2022-10-14T16:11:54Z")

</div>

I can’t blame you for feeling that way. This country is headed down a dangerous path. I’ve been dealing with quite a bit of right-wing extremism taking over the small community I live in recently. And they are using the current GOP playbook used by Trump.

---

<div class="post-metadata">

**Author:** ![Ook](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/ook/32/72_2.png) [@Ook](https://cog.discourse.group/u/Ook)\
**Post date:** [October 14, 2022, 6:46pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/35 "2022-10-14T18:46:14Z")

</div>

Look, I’m FOR moderation, as I believe that the health of ANY forum is also dependent on its contents.

Should I post something, which I deem to be inoffensive, but somebody else take offense against it, then I will not be upset if it is deleted.

There’s thousands of other forums out there, and offenders who are unhappy about their posts getting deleted, can jolly well go find some other place to offload their posts and be happy about it.

This forum’s just right as it is, and we most definitely do not want somebody to “rock the boat”…

---

<div class="post-metadata">

**Author:** ![Ook](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/ook/32/72_2.png) [@Ook](https://cog.discourse.group/u/Ook)\
**Post date:** [October 14, 2022, 6:48pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/36 "2022-10-14T18:48:06Z")

</div>

I do hope that we can avoid shitty laws, as I am also not in the mood for a fun day in court…

For now, let’s enjoy it while it lasts.

---

<div class="post-metadata">

**Author:** ![RRabbit42](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/rrabbit42/32/79_2.png) [@RRabbit42](https://cog.discourse.group/u/RRabbit42)\
**Post date:** [October 15, 2022, 4:19pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/37 "2022-10-15T16:19:44Z")

</div>

Lee, it’s a safe bet for planning on the law going back into effect. There’s been a lot decisions made in the last two years under the guise of fixing problems by adding restrictions that can be traced, in my opinion, to making one particular person happy.

I’m still in for helping with costs of running the site on the new host. Hopefully, we can keep what’s currently available.

---

<div class="post-metadata">

**Author:** ![TechnoMistress](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/technomistress/32/3981_2.png) [@TechnoMistress](https://cog.discourse.group/u/TechnoMistress)\
**Post date:** [October 15, 2022, 5:42pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/38 "2022-10-15T17:42:48Z")

</div>

> [@RRabbit42](#):
>
> I’m still in for helping with costs of running the site on the new host.

Ditto on this.

---

<div class="post-metadata">

**Author:** ![Lee\_Ars](https://sea1.discourse-cdn.com/flex001/user_avatar/cog.discourse.group/lee_ars/32/2338_2.png) [@Lee\_Ars](https://cog.discourse.group/u/Lee_Ars)\
**Post date:** [October 15, 2022, 5:57pm UTC](https://cog.discourse.group/t/were-back-for-now/1919/39 "2022-10-15T17:57:39Z")

</div>

Here is the cost breakdown with what I’m doing right now. This isn’t necessarily the best/cheapest/smartest way to host Discord, no warranty is expressed or implied, etc etc.

The forums run on an AWS EC2 [t3a.medium](https://aws.amazon.com/ec2/instance-types/t3/) instance. The instance size is driven primarily by Discourse’s RAM requirements, since Discourse itself is a Docker application that bundles together [a whole bunch of stuff](https://i.imgur.com/UPLcpCb.jpg). I am not using a separate RDS host or anything like that—Discourse and all its dependencies, including postgres, run locally on the EC2 instance.

Taking advantage of [reserved pricing](https://aws.amazon.com/ec2/pricing/reserved-instances/pricing/)—i.e., pre-paying for the server for 1- or 3-year terms—means the cost is pretty not-awful. Specifically, a t3a.med instance costs a couple hundred bucks per year, or $380-ish for a three year reservation. The current year reservation is up in November 2022.

AWS hosting is only one option, but it’s the one I’m currently using and the one I’m most familiar with from a perspective of costing. Realistically, Discourse can be hosted pretty much anywhere where you get a Docker-capable VPS with 4GB or more of RAM, and I can chuck a current forum state backup at whomever wants to take over hosting so the entire thing comes across as-is.

(Bandwidth costs are negligible with the current level of traffic—maybe $1-2/month on AWS. Storage costs are $5-ish per month for the server’s two EBS volumes plus 2 weeks of EBS snapshots for backup.)

[Previous page](https://cog.discourse.group/t/were-back-for-now/1919.md?page=1)
