Talk:Introduction to a Self Managed Life: a 13 hour & 28 minute presentation by FUTO software

Question About The Wiki

At about 10 minutes to the end of the video "Volkswagen car locations and identities revealed due to security fail" (not allowed to post link due to spam filter), Louis mentions making a consumer protection MediaWiki instance. Is this wiki supposed to be that instance? If so, do we get to start making pages on this wiki about how XYZ company has forced arbitration and/or other "rape" messages in their terms of service? Shall we start making pages that define terms like "EULA Roofying"? Or is that going to be a different project on a different wiki?

- TorBowser

The consumer protection wiki (now named the Consumer Action Taskforce) can be found at wiki.rossmangroup.com. --raidarr (💬) 21:10, 29 January 2025 (UTC)

Question About PfSense Router

[quote]

    Instead of risking your project with unknown mini PCs, consider using an old desktop computer:
    Reliability: A 10-12 year old desktop is likely more reliable than no-name mini PCs.

[/quote]

If we do this, wouldn't the 10-12 year old desktop likely have security vulnerabilities in the firmware? The firmware may not be patched or patchable because it is so old and possibly no longer supported by the manufacturer. The CPU microcode might not be updated. It might be vulnerable to Spectre or Meltdown or Retbleed. Maybe its Intel Management Engine is old and vulnerable. Are these things not a concern if we are using the old desktop computer just for pfSense? Or, if they are a concern, how do we patch our old desktop computer to make sure it is not vulnerable to these sorts of things?

- TorBowser

It is true that older devices will not get firmware updates and that can present a security issue. On the other hand newer boxes are built in with effective backdoors such as the Intel Management Engine and it is increasingly plausible other chips might be added to random branded boxes that you know nothing about (especially of concern with 'no-name mini PCs'). It is a tradeoff in risk that people need to decide for themselves. --raidarr (💬) 21:10, 29 January 2025 (UTC)

Difficulty in Downloading PDF of Guide

In tor browser, on the safest security level (which disables javascript), there is no option to download a PDF of the guide. This is in contrast to wikipedia, which does have a button to do this for their articles. How do we add this feature to the guide, in order to accommodate users who disable javascript for security and fingerprinting reasons?

Also, even when enabling javascript in tor browser, it seems to take an unreasonably long time for the browser to preview and save a PDF version of the guide for some reason. This may or may not be an issue in other browsers.

- TorBowser

Proposal: Option to "git clone" Entire Guide

For users who have trouble downloading a PDF of this guide, it would be useful to "git clone" the material and read it offline. This is especially useful for Whonix users who want to use the tor network but disable javascript in their tor browser. However, no such option appears to be available. It might be good to add such an option.

- TorBowser

Keeping the content accessible and editable in the FUTO Wiki would require a sync to a Git repo, right? That's a lot of effort for such a limited use case IMHO. However, I'd also like to see the various (e.g. backup and disk monitor) scripts in a Git repo. Louis freely admits he's not a programmer, and I've noticed some potential improvements and refactorings, but don't feel comfortable just editing the scripts in the Wiki, especially as I'm currently not doing such a setup myself, and therefore wouldn't be able to test any of those changes. A pull request on GitHub would be much more appropriate (although it remains to be seen whether a sufficient community of users would develop around this guide).

-- Ingo Karkat (talk) 10:57, 4 February 2025 (UTC)

Linux vs. GNU/Linux Naming Controversy

This guide always refers to GNU/Linux as "Linux." While that is the common naming convention, Linux is actually the name of the kernel. Not only is "GNU/Linux" generally more accurate, but also, much more importantly, the name "GNU/Linux" helps spread the values of free/libre software. The name "Linux" does not do that, since Linus Torvalds does not believe in the values of free/libre software. Therefore, I propose that instances of "Linux" in this guide should generally be changed to instances of "GNU/Linux", as God intended.

- TorBowser edit January 12, 2025- Due to not receiving a response from anyone in the discussion, I have decided to go ahead with this change. Several instances are not replaced, for example web URLs, quotes, names of products, and code blocks. I tried to be conservative here, in order to avoid accidentally breaking something. See https://wiki.futo.org/index.php?title=Introduction_to_a_Self_Managed_Life:_a_13_hour_%26_28_minute_presentation_by_FUTO_software&curid=4&diff=1166&oldid=1164

This guide does not seek to take a deeper stance in free/libre software argument, and is written to draw the casual user who wishes to be introduced to better ways of doing things. Pedantic use of GNU/Linux does not add to this mission, but all in all it's not a big deal either way. --raidarr (💬) 21:10, 29 January 2025 (UTC)

Recaptcha makes it very difficult for tor users to do any edits

Recaptcha requires javascript, so it requires the tor browser user to weaken their security by setting the browser below the safest security level. Furthermore, after enabling javascript within tor browser, recaptcha often does not allow a captcha to even be performed. For many exit nodes, it gives the message. "Your computer or network may be sending automated queries. To protect our users, we can't process your request right now. For more details visit our help page."

Therefore, editing the wiki while protecting oneself from mass surveillance is very difficult. See Edward Snowden revelations 2013-2014. Please investigate alternative solutions.

- TorBowser

edit January 12, 2025- editing is significantly easier now, however javascript is still required.

I do empathize with this, however the wiki also requires effective methods to contravene abuse, and hcaptcha (the tech in use here) is one of the only reliable tools for this. I'm open to forwarding any truly effective alternatives. That said, autoconfirmed should be kicked in for you by now; please reply if it has not. --raidarr (💬) 21:10, 29 January 2025 (UTC)

nondescript "Linux" versioning

If by "24 .10" you mean "Ubuntu 24.10", it is not a stable/long term support (LTS) release. LTS releases are the .04 (April) releases, and only every other year in even years (20, 22, 24, etc.). Also, if you mean Ubuntu, you should be specifying Ubuntu, not just Linux 24.10 or similar. They aren't the same thing.

CAPTCHA broken for new sections

All the form says is CAPTCHA with a text blank below it on the next line. There is no clue what to type into the blank. In order to add a new section, one must edit either a section, or the whole page.

Clonezilla as alternative to DDRescue

Cp. 25.7.2 6.2 DDRescue Guide from Ubuntu Server Live Environment: I can recommend Clonezilla for disk imaging. You boot it just like Ubuntu Live, but it's a dedicated tool for disk cloning, with a wizard to select drives / partitions that reduces the risk of mistakes, and offering neat features like compression and network destinations on top.

-- Ingo Karkat (talk) 11:04, 4 February 2025 (UTC)

[Suggestion] New Section About Media PC Build Alternative - CoreELEC + Ugoos AM6b+

By the 'chinese TV box' of it all I would totally understand dismissing this off the bat, but hear me out and please do read on.

As an open source alternative to the Elegant Media PC section (or perhaps as a small section alongside it) I humbly submit the below for consideration.

---

I have "titled" the below purposely omitting the branded hardware in the title as it didn't feel like it fit the 'vibe' of this wiki. However, if I am honest, the branded hardware is the only widely available choice, so it's perhaps more fitting to use that instead of the SOC, a la:

Open Source Media Player - CoreELEC + Ugoos AM6b+ ( AMLogic S922X-J SOC )

Within all second and third level titles I think that I've made sure to include a bespoke anchor, in case the titles are too generic by themselves. Plus it enables others to alter the actual titles for any of the usual "wiki bikeshedding" and leave the anchors in place for existing links.

If you're up for this suggestion, then there's no real need for this to hang around here ... the suggestion formatting is in the blockquote between the horizontal lines.

---

Open Source Media Player - CoreELEC + S922X-J

For an open source media player, instead of a media PC, use *CoreELEC* on a *UGOOS AM6B+* TV box.

This will play back pretty much anything anything that you throw at it (crucially including your Dolby Vision ripped discs) and will not break the bank at ~£130/$150.

Plus, it can sit alongside other devices to handle dedicated, decent, streaming and even those which would ostensibly offer similar functionality just by firing up Kodi.

What Is CoreELEC?

CoreELEC is a ( more? ) open source fork of LibreELEC, pointed at AMLogic SOC devices and it runs just enough linux to run KODI as a front end. CoreELEC describe it in their own words as:

CoreELEC is a ‘Just enough OS’ Linux distribution based on Kodi¹ technology for popular Amlogic hardware.

It is a very strong community project, and they are slowly building up CoreELEC for the next generation S928X-J SOC devices that have long since outgrown the S922X-J in the AM6B+. But you do not need to get "spec envy" as there is literally nothing that you would need that power for, and won't be for a long while ... until 8K media is on the scene.

The CoreELEC Site / Wiki / Forums

The CoreELEC community has a few facets you'll easily find on their site, but the most useful part of it is the forum. Which has dedicated sections for specific hardware, and more ... by contributing even just your issues you will potentially help improve the OS!

• The CoreELEC Site is available at: coreelec.org
• Their Wiki is available here: wiki.coreelec.org
• Their (discourse based) forums are here: discourse.coreelec.org

Community Advice

If I can offer one nugget of advice, that would be to make sure that if / when you raise an issue, that you try to 'prove' it on your system using legally available content. Don't mug yourself off, eh?

Hardware

Some information around the hardware, for more visit the CoreELEC site.

The SOC & Dolby Vision

The SOC is a rather old one, at this point, which most prominently made its debut with the ODROID N2+, but that was a vanilla S922X SOC. What is key about the "-J" and "-K" (and perhaps -Z) is that the hardware is shipped with a Dolby Vision licence.

This usually exists within the Android operating system that the devices ship with. So, the advisable path for installation is to ensure that the Android OS is kept alive on the EMMC storage, whether or not you push CoreELEC next to it, there, or not.

Manufacturers

Other TV box hardware is available that also runs on the S922X-J or S922X-K SOC.

If you are going to try other manufacturers, just make sure that it is at least mentioned on the CoreELEC forums by the willing users who have ridden the roads less traveled, for you, in testing these devices.

I do believe that one of the generation of the (cube) Fire TV Box is built on this platform.

As it is, the Ugoos AM6b+ is the only device that still being sold in any real quantities.

Next Gen S928X-J / K / Z

The wise ones at CoreELEC are taking their time at the start of the development of the next generation S928X-J ( and S928X-K - maybe S928X-Z ... cite! ) SOC that have long since outgrown the S922X-J at the heart of the AM6B+ TV box.

Many of these newer boxes boast a lot of great features, but you really do not need to get ' _spec envy_ ' of them.

This is because, as of right now, there is literally nothing that you would need that power for, especially with the OS in its current state. Proper 8K media isn't going to be a thing for a long while, so take it easy.

Purchasing Advice

If you are extremely wary, then you might want to spend the extra money to purchase one of these on Amazon, they are easily enough found. But it will increase your costs.

However, they are also available (I believe officially - cite?) on Aliexpress.

Finally, whilst you should always be hip to dodgy looking sites, I have bought two from Ugoos.store, without troubles. Whilst it does not appear to officially be a Ugoos affiliated site, I've been served OK by them.

Limitations

This section will endeavour to list some drawbacks and potential workarounds (not fixes ... hi, ITIL) that you may wish to consider.

1. Single HDMI Output

Single HDMI

This may not be an obvious one, but if you have ever tried to get both high bandwidth video AND audio out of a single HDMI through ageing equipment? You'll be reading this paragraph right here.

Put simply, let's imagine the following scenario, where you have (for example):

• An old, but good, Oled which can display a pristine Dolby Vision picture, but cannot output high-definition audio via the standard ARC HDMI socket to an audio device
• An old but HD Audio and Dolby Atmos / DTS-X capable AV Receiver that cannot passthrough Dolby Vision to a display device

The workaround is to use one of many HDMI Splitters or Audio Extractors. These can range in price, to some extreme highs for some amazing technology (I believe that some HDFury stuff can push different HDR Formats on the fly!) to cheap and obviously mass-produced/rebadged tech.

I have tested (by accident!) a few HDMI splitters and found that not all are made equal. This could be down to my sample size of ONE, when testing them out ... but ... yeah. Turned out that the cheapest one that I found was the best ... and pushed full-fat DV to my display, whilst sending full-fat HD audio to my older AV amp. That device was:

• EZCOO HDMI Splitter 4K* ( Amazon UK code: B083JVPXDY ) ( _should be OK on com, but shows not in stock_ )

Secondary Devices

With regards to second devices for streaming, that gets a mention this for compartmentalisation reasons.

With CoreELEC you have an open source method of playing back your media which has no 'phone home' ... but it is still not geared toward your Prime Flix+ and other streaming services.

So it stands to reason that you should still keep your TV dumb (or at least put it on a VLAN and/or restrict its routes!) and run a secondary device that still better at doing what your TV is trying to anyway.

Something like an Apple TV or Nvidia Shield should only "phone home" OS level data ( cite! ) ... rather than the exact filename, size, length, and more, of that baby video that you just played on your LG TV. Plus they'll give you a bit more freedom of choice for playing back that baby video ... should you really wish to.

Why Not The NVidia Shield?

You might ask why you cannot not just use an NVidia Shield / Apple TV to play back your files?

It's a good question with a few answers, and (at the end of the day) you will make the choices that you feel most comfortable with. Either way, those key reasons to keep separate devices might be:

1. Playback Issues - Despite knowing for YEARS there are still issues with colour reproduction for Dolby VIsion content on the NVidia Shield
2. Consumer Trust - Whilst we can never truly trust anything to keep to its core principles, both of the examples in use in this section have repeatedly screwed over their consumers, whether that be via:
   1. Pricing / Hidden Costs - Seriously, I wouldn't by an NVidia GPU ever again after what they've done to the prices
   2. Lack Of Development - NVidia hasn't updated their impossible driver setup (in Windows) whilst the competition have innovated and ensured that features are not hidden behind problematically antiquated interfaces, or worse ...
   3. Exploitation - Apple are no saints in this area, but NVidia takes the cake having put many settings behind online logins in the past ... I would not trust them to do it again, despite their new 'app' currently emerging from its cocoon
3. Android / iOS Based - These are inherently semi-walled or walled gardens owned by two of the largest corporations in the history of man, and that alone should be a factor
4. Phone Home - Phoning home can never be completely eliminated with something that is almost completely made by Google, or is closed source like iOS
5. Bloat - Even Android TV has a surface level of bloat (even on the powerful shield)
6. Securing Effort - The work that you would have to do to put yourself at ease with these OS' (like VLANs, routing, DNS, and more) just to ensure they only permeate where you'd like is a pain just to think about ... let alone fall down said rabbit hole to setup

---

-- User:Eliot (Talk to Eliot) 23:37, 4 February 2025 (UTC)

Is there a possiblity for more about domain registering

Excuse me, this is a superb guide, Thank you. I'd just like to ask though, whilst you warn against going through the route of running one's own email server... might there still be some validity in writing up an easy guide to registering a domain which one can then use with an online email provider? Like how you get your own domain name to then use with a service like protonmail or equivalent. I know this guide is heavily focused on one's media consumption experience and (seemingly, I think I followed it properly) one's ability to remote in to one's home network so as to access files stored at home whilst on the move, but the general spirit of reducing dependence on big tech might be worth expanding in to, particularly for email as being able to truly own one's email address (even if not the email servers which are handling your emails at the present time) gives one a truly permanent centre for one's online existence. Thank you (a long term linux user with plenty of local system tinkering experience but negligible network experience)