Selfhosted

55931 readers

663 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Self-hosting paradox: Windows for specifically MS word (lemmy.world)

submitted 3 days ago by TropicalDingdong@lemmy.world to c/selfhosted@lemmy.world

38 comments fedilink hide all child comments

Hey Home-labbers/ self hosters.

This weekend my 10 year old processing machine finally bit the dust (RIP 🗿 💀 ; old system76 laptop, won't even post, not the topic of this thread but if you've got ideas, I'm all ears), and as part of figuring out what happened and coming to the realization its time for a new machine. And as part of getting/ pricing a new machine (not looking forward to the consequences of the RAM-pocalypse), I've been reviewing/ thinking about the "structure" of what we as a household currently use our self-hosted/ home-labbed system for.

Myself and my partner are researchers, and as such, we regularly collaborate/ work together on manuscripts, and the reality is, we rely on windows because we're also collaborating with other authors who also rely on MS word to write in. Now I'm a 100% FOSS advocate, but this is a sticking point my partner has had, and I agree with them, at least in practice that realistically, we need a windows machine laying around specifically for this one, particular use case.

Now my thinking here is to use proxmox to spin up a windows machine as a VM, something we can remote into. Is there any best practice for something like this? How would this work with licensing? I personally haven't installed windows on something since like windows 7, and I know they've enshittified beyond recognition.

I personally don't want windows on my machines. But realistically, I recognize its necessity for this one particular use case. Thoughts?

you are viewing a single comment's thread
view the rest of the comments

[–] non_burglar@lemmy.world 5 points 3 days ago (1 children)

They likely need to track changes, which look and act weird when using LO on ms docs.

[–] BestBouclettes@jlai.lu 1 points 3 days ago (1 children)

Fair, markdown, git and pandoc could work but, it might be a big jump for someone used to Word

[–] non_burglar@lemmy.world 4 points 3 days ago

This isn't an option for op, they're collaborating with others for work, so they can't change the involvement of MS.