this post was submitted on 23 Aug 2022
66 points (91.2% liked)

Asklemmy

43916 readers
927 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

  1. Open-ended question
  2. Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
  3. Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
  4. Not ad nauseam inducing: please make sure it is a question that would be new to most members
  5. An actual topic of discussion

Looking for support?

Looking for a community?

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago
MODERATORS
 

I am looking for a fediverse solution for a blog and I tried it with writefreely, but it has some disadvantages I can't live with.

The most important one is, that it should be possible to communicate with people within the fediverse. People should be able to comment on every article with a fediverse account, like it is already possible between Mastodon, Pleroma, PeerTube and others. But comments aren't a thing with writefreely and this is sad.

After using Lemmy for a few days I just thought if it is possible to use it as a blog and ask on lemmys github if it is possible to restrict a group so only one person could post new articles, but all others can comment. And the answer is yes!

But would it be possible to use it as a blog?

Imagine I would have a group called "utopify.org - Research & Development" and would post current progress about a blog series and you can only comment on it. Would it be possible and would it be something you want to see on Lemmy or would this just be an abuse of the software.

If all of this is just a no-go, are there other ways in the fediverse to have a blog article, which can be shared on the fediverse and be commented on?

you are viewing a single comment's thread
view the rest of the comments
[–] ojmcelderry@lemmy.one 1 points 1 year ago (1 children)

To be honest, I think whichever approach you take is unlikely to have a significant effect on how much energy your website uses overall.

For example, servers in datacentres are very powerful and are able to run more than one thing at once. So if you were hosting your own Lemmy/Mastodon instance, there'd be no reason why you couldn't also host a standalone website on that same server. The difference in energy usage would be negligible.

In contrast, you could argue that Lemmy is less efficient than a straightforward static website because the content of your blog posts will inevitably end up being federated to many other instances. That means multiple copies of your blog will be transferred between multiple servers and stored on multiple hard drives, etc. Whereas a static website lives in one place and doesn't end up using so many resources.

At the end of the day, whichever you choose will likely have very little impact. So I wouldn't worry too much about your blog's green credentials.

I'm saying this as somebody who is pro protecting the environment, but also pro prioritising our efforts in the places they'll have greatest impact. You'll probably have a bigger impact by walking to the store instead of driving.

[–] utopify_org@lemmy.ml 1 points 1 year ago

I’m saying this as somebody who is pro protecting the environment, but also pro prioritising our efforts in the places they’ll have greatest impact. You’ll probably have a bigger impact by walking to the store instead of driving.

Whataboutism isn't really helpful, because you can believe me, that I have already optimized every other field in my life and people even call me extreme.

I really want to put the focus on this specific topic.

But you might be somehow right, that IF a server is already used for an energy consuming tool (like a fediverse tool [Mastodon, Lemmy, Kbin, FireFish, etc.]), the energy consumption is pretty low in comparison of the fediverse tool, if there is a static website running on the same server. What IF there isn't this energy consuming tool?

Actually, I am really worried that this could be used as an excuse and the rebound effect takes effect, using a lot of tools on the same server.