110

Voting is now open for the new sh.itjust.works sidebar banner.

There are eight entries below. To vote, leave a top-level reply containing the number of your choice (1–8). Please vote only once. If you change your mind, edit your original reply instead of posting another vote.

The original submission thread is here: https://sh.itjust.works/post/65782570

Rules for this vote

  • Only sh.itjust.works accounts may cast a vote
  • The votes will be tallied on Friday, September 18th.
  • Any further discussion should be posted in the thread linked above

1 — Gullible

Entry 1 — Gullible

View the original submission

2 — cantstopthesignal

Entry 2 — cantstopthesignal

View the original submission

3 — Sinopa

Entry 3 — Sinopa

View the original submission

4 — Eyekaytee

Entry 4 — Eyekaytee

View the original submission

5 — Susaga

Entry 5 — Susaga

View the original submission

6 — loam

Entry 6 — loam

View the original submission

7 — Sinopa

Entry 7 — Sinopa

View the original submission

8 -- Current

Entry 8 - Current

Reply with the number of your choice. For example: 3

57

cross-posted from: https://sh.itjust.works/post/66524166

Good day SJW community,

I wanted to provide everyone with an update regarding the stability issues we experienced over the past 24 hours.

Beginning Wednesday, September 9, we observed a significant spike in incoming requests originating from a large number of IP addresses associated with networks operated by Baidu, Tencent and OneCable Network LLC.

The traffic patterns pointed to coordinated web scraping activity distributed across large IP ranges. This approach allowed the scrapers to circumvent the per-IP rate limits we have in place by spreading requests across many different addresses. The requests were primarily targeting comments and post content, suggesting the activity was focused on large-scale data collection, potentially for AI model-related purposes.

We identified this activity by analyzing traffic patterns at the Autonomous System Number (ASN) level and reviewing the average number of requests per minute generated by each network.

At the same time, we identified a separate source of abnormal traffic that appeared to be coming from another actor. These requests were performing expensive search queries that placed significant load on the server and affected its ability to respond to legitimate requests in a timely manner.

This traffic was using the following user agent:

NexusGlobalBot/2.0 (SupabaseEdgeRuntime/1.76.0)

After blocking this agent and its associated request patterns, we observed a significant reduction in server load, bringing utilization much closer to normal operating levels.

This is not the first time we have encountered this type of activity over the past several months and unfortunately, it is unlikely to be the last. We will continue improving our monitoring, rate limiting, and mitigation measures to reduce the impact of abusive or excessive automated traffic while maintaining reliable access for legitimate users.

Thank you for your continued support and trust.

71

Good day SJW community,

I wanted to provide everyone with an update regarding the stability issues we experienced over the past 24 hours.

Beginning Wednesday, September 9, we observed a significant spike in incoming requests originating from a large number of IP addresses associated with networks operated by Baidu, Tencent and OneCable Network LLC.

The traffic patterns pointed to coordinated web scraping activity distributed across large IP ranges. This approach allowed the scrapers to circumvent the per-IP rate limits we have in place by spreading requests across many different addresses. The requests were primarily targeting comments and post content, suggesting the activity was focused on large-scale data collection, potentially for AI model-related purposes.

We identified this activity by analyzing traffic patterns at the Autonomous System Number (ASN) level and reviewing the average number of requests per minute generated by each network.

At the same time, we identified a separate source of abnormal traffic that appeared to be coming from another actor. These requests were performing expensive search queries that placed significant load on the server and affected its ability to respond to legitimate requests in a timely manner.

This traffic was using the following user agent:

NexusGlobalBot/2.0 (SupabaseEdgeRuntime/1.76.0)

After blocking this agent and its associated request patterns, we observed a significant reduction in server load, bringing utilization much closer to normal operating levels.

This is not the first time we have encountered this type of activity over the past several months and unfortunately, it is unlikely to be the last. We will continue improving our monitoring, rate limiting, and mitigation measures to reduce the impact of abusive or excessive automated traffic while maintaining reliable access for legitimate users.

Thank you for your continued support and trust.

15

cross-posted from: https://sh.itjust.works/post/64240582

To the members of SJW, our friends across the Fediverse, and the curious passersby, this update is for you.

Now that we are well into 2026, I wanted to look back at how 2025 unfolded and share some insight into SJW’s finances, infrastructure, traffic trends, and priorities for the year ahead.

2025 Finances

One of the biggest changes in 2025 was the introduction of member-supported funding.

In January of 2025, I opened donations to help cover the cost of operating SJW. The goal was to begin moving away from a model funded entirely by me and toward a community-supported model that can remain financially sustainable over the long term.

Throughout 2025, we received $3,239.41 in net donations and spent $1,396.14 on operational expenses.

During the year, we also experienced a few hardware failures, most notably a failed power supply and hard drive. Thanks to the redundancy built into our servers, neither failure resulted in a service disruption.

I was able to repurpose a compatible power supply from a decommissioned server at no cost. I also personally covered the replacement hard drive before prices went through the roof. While donation funds could have covered these expenses, I wanted to preserve as much of the balance as possible for a larger hardware upgrade.

All amounts below are in Canadian dollars.

Category Amount Additional information
Net donations received $3,239.41 January through December 2025
S3-compatible storage $69.62 Paid through July 2026
Email service $70.60 Paid through July 2026
Colocation $1,200.00 2025 infrastructure hosting
Domain name $55.92 Domain registration
Total expenses $1,396.14
Remaining balance $1,843.27 Reserved for operations and future infrastructure

This year, I hope we can raise enough to help purchase newer hardware. Unfortunately, as many of you are probably aware, the rapid growth of AI infrastructure has significantly increased the price and demand for many server components.

Traffic Trends

This is where things become particularly interesting and, at first glance, a little puzzling.

Based on our traffic logs and Cloudflare data, overall traffic approximately doubled during 2025, despite SJW adding only around 4,000 active accounts during the same period.

As of January 2026, when I first began preparing this update, Cloudflare was reporting:

  • More than 300 million pages served per month
  • Approximately 6 million unique visitors over a 30-day period

These are enormous numbers, but they almost certainly do not represent six million individual people.

I suspect that at least 50 to 60 percent of this activity, and possibly more, comes from bots, scrapers, automated crawlers, vulnerability scanners, archival services, and other automated systems. Some of this activity may also come from services gathering public information for traditional search engines and newer AI-powered search tools.

I recently implemented Anubis to help reduce abusive automated traffic. While it cannot prevent every bot or scraper from accessing the site, it makes large-scale automated collection more difficult and has helped us begin addressing the problem.

Hardware and Infrastructure

Given these traffic trends and some of the performance issues we have encountered, our current hardware is reaching the point where I need to seriously consider replacing or upgrading it.

I recently changed our Lemmy deployment to use horizontal scaling. In simpler terms, we now run multiple Lemmy service instances in parallel and distribute incoming traffic between them. This has helped improve the instance’s ability to handle periods of heavier activity.

However, software improvements can only take us so far. Newer hardware would give us more capacity, better performance, and additional room to build resilience into the platform.

I would also like to explore bringing our primary S3-compatible object storage in-house while maintaining an appropriate off-site backup strategy. This would reduce our reliance on third-party storage providers while giving us more control over privacy, performance, and redundancy.

2026 Priorities

Our main infrastructure priorities for 2026 are:

  • Upgrade or replace aging server hardware
  • Add further redundancy to critical services
  • Continue improving horizontal scaling
  • Reduce the impact of abusive automated traffic
  • Explore self-hosted object storage
  • Deepen our collaboration with Fedecan

Fedecan

As some of you may remember, we previously shared our intention to join Fedecan, an organization with which we share common values and a similar vision for the Canadian Fediverse.

That transition has now been finalized. SJW is associated with a registered Canadian nonprofit organization and can benefit from its banking, administrative, and nonprofit structure.

The initial banking and legal integration is complete, but our collaboration will continue to deepen as we work toward a larger shared vision and develop common guidelines.

Donations are now processed through Fedecan, but funds donated specifically to SJW are tracked separately and remain reserved for SJW’s operating costs, infrastructure improvements, and future service expansion.

Donations

As outlined above, one of our main goals this year is to upgrade our existing hardware and improve the resilience of the services supporting SJW.

I am still evaluating the available hardware options and will share more specific information once the upgrade plan and expected costs have been finalized.

If you have the means and would like to support SJW, donations of any size are greatly appreciated. Every contribution helps us maintain the instance, prepare for future growth, and reduce how much of the operating cost must be covered personally.

Regardless of how much we raise, I'm committed to keeping SJW running. I will continue looking for suitable replacement hardware and am prepared to personally contribute toward any shortfall required to support the next generation of our infrastructure.

If you'd like you can contribute through either of the following platforms:

Thank You

In closing, I want to thank our admins and mods, who continue to volunteer their time to help make SJW a safe and welcoming place.

I also want to thank our members who have chosen to make the Fediverse, and SJW in particular, their home. Whether you donate, contribute to discussions, report problems, help other members, or simply spend time here, you are part of what keeps this community alive.

Thank you for being you.

And if nobody has reminded you lately: you are great, you are loved, and most importantly, you are enough.

TheDude ✌️

345

To the members of SJW, our friends across the Fediverse, and the curious passersby, this update is for you.

Now that we are well into 2026, I wanted to look back at how 2025 unfolded and share some insight into SJW’s finances, infrastructure, traffic trends, and priorities for the year ahead.

2025 Finances

One of the biggest changes in 2025 was the introduction of member-supported funding.

In January of 2025, I opened donations to help cover the cost of operating SJW. The goal was to begin moving away from a model funded entirely by me and toward a community-supported model that can remain financially sustainable over the long term.

Throughout 2025, we received $3,239.41 in net donations and spent $1,396.14 on operational expenses.

During the year, we also experienced a few hardware failures, most notably a failed power supply and hard drive. Thanks to the redundancy built into our servers, neither failure resulted in a service disruption.

I was able to repurpose a compatible power supply from a decommissioned server at no cost. I also personally covered the replacement hard drive before prices went through the roof. While donation funds could have covered these expenses, I wanted to preserve as much of the balance as possible for a larger hardware upgrade.

All amounts below are in Canadian dollars.

Category Amount Additional information
Net donations received $3,239.41 January through December 2025
S3-compatible storage $69.62 Paid through July 2026
Email service $70.60 Paid through July 2026
Colocation $1,200.00 2025 infrastructure hosting
Domain name $55.92 Domain registration
Total expenses $1,396.14
Remaining balance $1,843.27 Reserved for operations and future infrastructure

This year, I hope we can raise enough to help purchase newer hardware. Unfortunately, as many of you are probably aware, the rapid growth of AI infrastructure has significantly increased the price and demand for many server components.

Traffic Trends

This is where things become particularly interesting and, at first glance, a little puzzling.

Based on our traffic logs and Cloudflare data, overall traffic approximately doubled during 2025, despite SJW adding only around 4,000 active accounts during the same period.

As of January 2026, when I first began preparing this update, Cloudflare was reporting:

  • More than 300 million pages served per month
  • Approximately 6 million unique visitors over a 30-day period

These are enormous numbers, but they almost certainly do not represent six million individual people.

I suspect that at least 50 to 60 percent of this activity, and possibly more, comes from bots, scrapers, automated crawlers, vulnerability scanners, archival services, and other automated systems. Some of this activity may also come from services gathering public information for traditional search engines and newer AI-powered search tools.

I recently implemented Anubis to help reduce abusive automated traffic. While it cannot prevent every bot or scraper from accessing the site, it makes large-scale automated collection more difficult and has helped us begin addressing the problem.

Hardware and Infrastructure

Given these traffic trends and some of the performance issues we have encountered, our current hardware is reaching the point where I need to seriously consider replacing or upgrading it.

I recently changed our Lemmy deployment to use horizontal scaling. In simpler terms, we now run multiple Lemmy service instances in parallel and distribute incoming traffic between them. This has helped improve the instance’s ability to handle periods of heavier activity.

However, software improvements can only take us so far. Newer hardware would give us more capacity, better performance, and additional room to build resilience into the platform.

I would also like to explore bringing our primary S3-compatible object storage in-house while maintaining an appropriate off-site backup strategy. This would reduce our reliance on third-party storage providers while giving us more control over privacy, performance, and redundancy.

2026 Priorities

Our main infrastructure priorities for 2026 are:

  • Upgrade or replace aging server hardware
  • Add further redundancy to critical services
  • Continue improving horizontal scaling
  • Reduce the impact of abusive automated traffic
  • Explore self-hosted object storage
  • Deepen our collaboration with Fedecan

Fedecan

As some of you may remember, we previously shared our intention to join Fedecan, an organization with which we share common values and a similar vision for the Canadian Fediverse.

That transition has now been finalized. SJW is associated with a registered Canadian nonprofit organization and can benefit from its banking, administrative, and nonprofit structure.

The initial banking and legal integration is complete, but our collaboration will continue to deepen as we work toward a larger shared vision and develop common guidelines.

Donations are now processed through Fedecan, but funds donated specifically to SJW are tracked separately and remain reserved for SJW’s operating costs, infrastructure improvements, and future service expansion.

Donations

As outlined above, one of our main goals this year is to upgrade our existing hardware and improve the resilience of the services supporting SJW.

I am still evaluating the available hardware options and will share more specific information once the upgrade plan and expected costs have been finalized.

If you have the means and would like to support SJW, donations of any size are greatly appreciated. Every contribution helps us maintain the instance, prepare for future growth, and reduce how much of the operating cost must be covered personally.

Regardless of how much we raise, I'm committed to keeping SJW running. I will continue looking for suitable replacement hardware and am prepared to personally contribute toward any shortfall required to support the next generation of our infrastructure.

If you'd like you can contribute through either of the following platforms:

Thank You

In closing, I want to thank our admins and mods, who continue to volunteer their time to help make SJW a safe and welcoming place.

I also want to thank our members who have chosen to make the Fediverse, and SJW in particular, their home. Whether you donate, contribute to discussions, report problems, help other members, or simply spend time here, you are part of what keeps this community alive.

Thank you for being you.

And if nobody has reminded you lately: you are great, you are loved, and most importantly, you are enough.

TheDude ✌️

129

Since there has not yet been an official announcement regarding this matter, I wanted to provide some clarity to the community.

Last week, it was discovered that the Tesseract frontend included an undisclosed and unsanctioned blocklist that prevented users from seeing certain people and communities across the fedivese. This led to significant controversy across the Fediverse, after which the original developer withdrew the project and left the Fediverse.

Everyone is entitled to their own views and to make their own choices about the content they wish to see. However, when those choices are built into an open-source project, they must be disclosed publicly and presented transparently to users. Quietly imposing a blocklist without their knowledge is a serious breach of trust and, in my view, raises legitimate concerns about the security and integrity of the software.

As a result, we have disabled the Tesseract frontend on sh.itjust.works indefinitely.

We are open to offering other alternative frontends. If there is one you would like us to consider, please share your suggestion in !main@sh.itjust.works or !agora@sh.itjust.works.

Thank you

122

cross-posted from: https://lemmy.ca/post/67952523

This is the first big step in the process to develop comprehensive guidelines for the Fedecan non-profit and the various platforms.

While this will mostly involve converting tacit knowledge and experience into an explicit written form, we expect that this process will inevitably bring up some points of disagreement on the best way to deal with different issues. We ask everyone participating in these discussions to please contribute constructively and in good faith. We encourage you to bring up any concerns or issues you have with the proposed structure and drafted guidelines, so that we can work together to fix them early on. However, in order to keep a productive environment for those discussions, we will be pruning any comment chains that devolve into personal attacks, slap fights, etc.

To help ground your feedback, consider these thought experiments when evaluating a potential guideline:

  • Veil of ignorance: Would it still feel fair to you if you switched places with someone else on the platform (ex. a new user, a moderator, an admin, a member of a vulnerable group, etc.)?
  • Equal Applicability: These rules will be enforced uniformly on everyone. A poorly written rule that helps "your side" today, can easily harm "your side" in the future as circumstances change.

The full guidelines, including governance details like the annual review cycle, can be found on the website: https://fedecan.ca/en/guidelines/

We plan to structure the guidelines as follows:

diagram of the tiers that are described below

Tier 1: Fedecan Rules

Internal Conduct

These rules apply to Fedecan team members (directors, officers, admins, and anyone with elevated access). They set expectations for how team members should act.

Universal Rules

These are the baseline rules that apply to every user on every Fedecan platform. They cover the things that are prohibited by Canadian law (threats, hate speech, CSAM, non-consensual intimate imagery) as well as universal policy rules (privacy/doxxing, harassment, fraud, content that could cause harm, labelling of sensitive content, etc.).

Tier 2: Platform-Specific

Each platform has different functionality and norms, so this is where we can be more specific with the rules. The threadiverse platforms (lemmy.ca, piefed.ca, sh.itjust.works) share similar rules around community creation, moderation, vote manipulation, and content labelling. Pixelfed has its own rules tailored to its platform.

Tier 3: Community-Level Rule Templates

These are optional templates that communities can link to, or use as a starting point for their own rules. The idea is that moderators can point users to a clearly written explanation of why a rule exists, and any relevant exceptions, rather than trying to fit everything into the sidebar. Additionally, if many communities are enforcing a particular rule in the same way, then users will have an easier time understanding and following them.

The post title standards template has been drafted, and we plan to add more as the need arises. I have a few others that are in the works, but they have some overlap with the other sections, so I thought that it would be better to let people discuss first.

8

Hey all,

Quick bump up to 0.19.19 was applied this afternoon.

Enjoy!

14

Upgrade was done to the instance to v0.19.18.

Enjoy!

14

Quick impulsive upgrade to 0.19.16 this morning. Not much downtime was experienced (less than 10 minutes).

Continue being great to one another!

14
Upgrade to 0.19.15 (sh.itjust.works)

Good evening SJW community!

I had some extra some last minute and decided to upgrade this instance to 0.19.15

Change logs can be found here

Thank you

36
submitted 1 year ago* (last edited 1 year ago) by TheDude@sh.itjust.works to c/announcements@sh.itjust.works

Hello all,

I hope everyone has been enjoying their summer and has had the chance to check a few new items off their bucket list!

I will be upgrading this lemmy instance to version 0.19.12 tomorrow at 8PM EDT. This should be a quick update.

As always I will provide an update once the upgrade has been completed.

You may experience up to 30 minutes of downtime as the upgrade completes.

I apologize for the short notice.

Thank you for the continuing to support to SJW and the Fediverse

UPDATE: The upgrade was successful. Took about 10 minutes to complete. Thank you

[-] TheDude@sh.itjust.works 88 points 2 years ago

I want to say that I've been blown away by the amount of support that's I've received in the last 24 hours. You all have left me speechless. Thank you everyone who have donated and those who couldn't, know that being a good member of this community already more than I could ask for. Thank you!

[-] TheDude@sh.itjust.works 61 points 2 years ago

Hey,

I'm due to make a post about the instances finances soon. I'll get one posted in the next bit.

I'm still covering costs out of pocket but my goal has been to have this instance fully funded by its members. I want this instance to stay true to its members, the fediverse and be put in a position where it can continue to thrive transparently without me. The admin team has been doing an outstanding job keeping this instance safe and moderated for everyone. I don't thank them enough but they are the true heroes of this instance.

As some may know, I've been working with a local non profit for the past 6 months to have them leveraged in accepting accepting donations for this instance. They have been slow to get things done but its progressing. I may end up doing what I was trying to avoid and create my own non-profit instead if that's what it takes. That direction does have its own challenges and would add additional responsibilities to my plate.

In the meanwhile, while some of the costs of the services have gone up slightly, I get joy knowing that I can continue providing this instance to all of you. I'm OK paying the costs to keeping the lights on until we can transition to donations.

[-] TheDude@sh.itjust.works 60 points 3 years ago

Hey all, I’m always excited to upgrade to the latest versions that become available. Unless the upgrade is related to security I will tend to wait a few days to give other instances a chance to share their experiences. Before upgrading I usually go over the issues that have been submitted to help understand the risks and solutions to mitigate them.

That being said the new version does bring in a whole bunch of performance gains (mostly related to the database) that i’m looking forward to.

Lemmy.world is due to upgrade later today and I plan on upgrading shortly after them (either Monday or Tuesday).

I will put up a notification up prior to the upgrade.

Thanks

[-] TheDude@sh.itjust.works 78 points 3 years ago

Hey all,

There has been a few issues over the last couple of weeks. Here's a rundown of some of the issues we've had.

  • Broken Images: A few weeks ago we had issues with broken images. This was due to me migrating our local image storage to object storage (like AWS S3). When I did the switch it broke all old images as they needed to be migrated. Pictrs at that time did not support concurrent uploads which means the migration would have taken days or weeks to complete during which time the image service would be offline. Instead I waiting for a newer version to be released that supported concurrent connections and did the migration in about 30-40 minutes one evening.

  • 5xx server errors: Some of you may have experience a lemmy page with an error code on it. This was due to me trying to implement an additional proxy to shield and mitigate future risks. While rolling this out I hit a few blockers that caused downtime as we worked to rectify it. I'm glad to say that as of Today this has since been implemented.

In the addition to the above, the lemmyverse and especially this instance has been under bot attack almost daily. These bot attacks are eating resources and causing a query floods.

Lemmy is still very young and in its early phases. In time these issues will slowly go away.

P.S you don't have to worry about me leaving you guys hanging.

[-] TheDude@sh.itjust.works 125 points 3 years ago

Honestly these type of scat spamming has been really discouraging on me. I spend time and money so that the community can have a reliable and nice instance to call home, only to have a few (not sure what to call them) people try to ruin it for everyone. If these people are reading this comment, just know that every time you make these kinds of unwanted posts you are taking my time away from my family and young kids to address the reports.

My nights lately have been mostly used for coding some extra moderation tools that will moderate these in the future.

I sincerely apologize for all of you who have been exposed to literal shit images over the last week. I’m working as fast as I can and will implement something soon.

In the meanwhile i’ve added a few new admins to help with this moderation.

[-] TheDude@sh.itjust.works 77 points 3 years ago

Hey all,

As others mentioned we did not have custom emojis so we were not affected by this particular attack. I have since upgraded our UI to 0.18.2-rc.1 which mitigates this XSS vulnerability.

[-] TheDude@sh.itjust.works 56 points 3 years ago

The vulnerability appeared to be from a custom emoji that they were running. SJW does not use any custom emoji so we should not be affected. In either case lemmy.world has now been restored and is back online. I’ll keep an extra eye on this instance until the patch gets released shortly.

[-] TheDude@sh.itjust.works 97 points 3 years ago

If I were to do some rough math I'd say it would cost about $300/CAD per month.

My goal is once we are approved to start accepting donations that I can purchase dedicated hardware for this instance. I'd get a used server at about $2300 which would be sufficient a good amount of extra users and through it into its own dedicated shared colo at about $100/month. Factor in about $300-400 a year for drive replacements and we are left with $2300 / 12 month= 191.66 + 100/month for the shared 1u colo + a budget of $400 for drive failures throughout the year $33/month. 191.66 + 100 + 33 = $324.66/month for the first year dropping to about $133 per month after the first 12 months. It's worth noting that this method would give us double the amount of resources and quite a bit of extra storage.

Ideally we don't keep this instance on a single server forever and start to think about spreading it over multiple hosts at or after around 100K users (or less if the number of active users is high).

If someone wanted to host an instance they would not need to allocate as much resources as I have to this instance and depending on how active the instance gets could run off something a lot less powerful.

[-] TheDude@sh.itjust.works 73 points 3 years ago

Hi Nahvi.

Thanks for posting this well put together post. I can tell that you put some time and thought into this and I want you to know that I recognize that.

Regarding your concern, this is a topic that has been brought up numerous times over the past month. I've since moved towards being more community driven, letting users discuss and debate on topics that are important to them. These discussion move forward towards a vote over a 7 day period. This process will change over time as we come across flaws and look for ways solve them together.

One more thing I want to make clear regarding your tl;dr question Will I be blocking other instances for personal reasons? Short answer is no, I believe the community should determine what should or should not be blocked.

That being said I want to make myself clear that there are limitations, I will continue to defederate instances that openly promote or spreads hate speech, terrorism, CP, loli, trolling and instances that become bot instances. These shouldn't be things that need to be justified, I think they fall under the "be a good human" category.

I hope this clarifies your concerns and you continue to make sh.itjust.works your home.

[-] TheDude@sh.itjust.works 70 points 3 years ago* (last edited 3 years ago)

Hey everyone, woke up this morning with this news. This news really comes at a surprise as I have not seen or heard of any trolling coming from members of this community. I also have not been approached by their admins to see how we could collaborate. In either case, I'll be attempting to reach out to their admins and discuss a path forward together.

I'll post an update with the details in the coming days.

[-] TheDude@sh.itjust.works 61 points 3 years ago* (last edited 3 years ago)

Hey all,

I just posted an update here https://sh.itjust.works/post/49787

I probably should have listened to my gut and not have went to bed last night.

Should be fixed now, it was related to an nginx setting that needed to be tuned.

[-] TheDude@sh.itjust.works 166 points 3 years ago* (last edited 3 years ago)

Any government or governing body should be open to criticism. They are suppose to be working for the people they serve. How is anyone going to know better if no one tells them what they are doing wrong? @wriggly3171@sh.itjust.works you have my support

view more: next ›

TheDude

0 post score
0 comment score
joined 3 years ago
MODERATOR OF