From: Ihor Radchenko <yantar92@posteo.net>
To: rms@gnu.org
Cc: jporterbugs@gmail.com, ahyatt@gmail.com, emacs-devel@gnu.org
Subject: Re: [NonGNU ELPA] New package: llm
Date: Wed, 06 Sep 2023 12:25:53 +0000 [thread overview]
Message-ID: <87h6o7sd2m.fsf@localhost> (raw)
In-Reply-To: <E1qcyN3-0001al-5t@fencepost.gnu.org>
[ I am not sure if this discussion is still relevant enough for
emacs-devel. Let me know if we need to move to emacs-tangents or other
more suitable place ]
Richard Stallman <rms@gnu.org> writes:
> > > As for LLMs that run on servers, they are a different issue entirely.
> > > They are all SaaSS (Service as a Software Substitute), and SaaSS is
> > > always unjust.
> > >
> > > See https://gnu.org/philosophy/who-does-that-server-really-serve.html
> > > for explanation.
>
> > I do not fully agree here. A number of more powerful LLMs have very
> > limiting hardware requirements. For example, some LLMs require 64+Gbs of
> > RAM to run:
>
> That is true, and it is unfortunate. There may be no practical way
> to run a certain model except for SaaSS.
Clarification: that might still be possible if one runs LLMs on remote
virtual or dedicated server. Such server is technically not what the
user _owns physically_. However, there is a freedom running arbitrary
version (including modified version) of the LLM on such a server.
Also, it looks like hosted servers running libre software are becoming a
rather common thing. For example, I have seen BBB servers offered for
rent: https://owncube.com/bbb_en.html and even LLM servers:
https://ownai.org/ The problem is that the extent users are allowed to
control that running software is more limited compared to what one can
enjoy with full SSH access or in a physically owned machine.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-09-06 12:25 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 23:54 [NonGNU ELPA] New package: llm Andrew Hyatt
2023-08-08 5:42 ` Philip Kaludercic
2023-08-08 15:08 ` Spencer Baugh
2023-08-08 15:09 ` Andrew Hyatt
2023-08-09 3:47 ` Richard Stallman
2023-08-09 4:37 ` Andrew Hyatt
2023-08-13 1:43 ` Richard Stallman
2023-08-13 1:43 ` Richard Stallman
2023-08-13 2:11 ` Emanuel Berg
2023-08-15 5:14 ` Andrew Hyatt
2023-08-15 17:12 ` Jim Porter
2023-08-17 2:02 ` Richard Stallman
2023-08-17 2:48 ` Andrew Hyatt
2023-08-19 1:51 ` Richard Stallman
2023-08-19 9:08 ` Ihor Radchenko
2023-08-21 1:12 ` Richard Stallman
2023-08-21 8:26 ` Ihor Radchenko
2023-08-17 17:08 ` Daniel Fleischer
2023-08-19 1:49 ` Richard Stallman
2023-08-19 8:15 ` Daniel Fleischer
2023-08-21 1:12 ` Richard Stallman
2023-08-21 4:48 ` Jim Porter
2023-08-21 5:12 ` Andrew Hyatt
2023-08-21 6:03 ` Jim Porter
2023-08-21 6:36 ` Daniel Fleischer
2023-08-22 1:06 ` Richard Stallman
2023-08-16 2:30 ` Richard Stallman
2023-08-16 5:11 ` Tomas Hlavaty
2023-08-18 2:10 ` Richard Stallman
2023-08-27 1:07 ` Andrew Hyatt
2023-08-27 13:11 ` Philip Kaludercic
2023-08-28 1:31 ` Richard Stallman
2023-08-28 2:32 ` Andrew Hyatt
2023-08-28 2:59 ` Jim Porter
2023-08-28 4:54 ` Andrew Hyatt
2023-08-31 2:10 ` Richard Stallman
2023-08-31 9:06 ` Ihor Radchenko
2023-09-04 1:27 ` Richard Stallman
2023-09-06 12:25 ` Ihor Radchenko [this message]
2023-09-04 1:27 ` Richard Stallman
2023-08-27 18:36 ` Jim Porter
2023-08-28 0:19 ` Andrew Hyatt
2023-09-04 1:27 ` Richard Stallman
2023-09-04 5:18 ` Andrew Hyatt
2023-09-07 1:21 ` Richard Stallman
2023-09-12 4:54 ` Andrew Hyatt
2023-09-12 9:57 ` Philip Kaludercic
2023-09-12 15:05 ` Stefan Kangas
2023-09-19 16:26 ` Andrew Hyatt
2023-09-19 16:34 ` Philip Kaludercic
2023-09-19 18:19 ` Andrew Hyatt
2023-09-04 1:27 ` Richard Stallman
2023-08-09 3:47 ` Richard Stallman
2023-08-09 4:06 ` Andrew Hyatt
2023-08-12 2:44 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6o7sd2m.fsf@localhost \
--to=yantar92@posteo.net \
--cc=ahyatt@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).