Cast out the Heretic! When gaming goes OpenSource! #GamingOpenSource #Gaming #MovimGamingOpenSource #AltTech #RaspberryPi #Kodi #GamingOpenSourceMovim #Heretic

In 1998 the game Heretic was shareware but its EULA was incompatible with GPL. However, on 8 September 2008 the game's code was rereleased but, this time, under GNU GPLv2. So now it qualifies as OpenSource.

Originally most people expected to play the game under Microsoft DOS (although yes some could play it on Mac). This make the game Heretic an interesting case (although not unique), setting it aside from other OpenSourced game engines such as that for Doom3 which went on to be used in the Thief3 style game "Dark Project" (which cannot run on DOS 16bit). Even though Heretic could be played on an opens-source operating system such as linux, Heretic is one of those games that is in the position of being able to be played on an Open Source Operating system such as Linux but also on the retroactively open-sourced Operating system DOS.

While it maybe seem like just an interesting redundancy, there is something useful about that fact. DosBox is an avenue for softwares to be released in locked down operating systems that can run DOSbox (like some Android devices), sometimes even with GPU passthrough (although not always). With it, 63MB of RAM can be accessed which is enough to play some media codecs in software, such as some XVid.

In reverse, the fact that a person can run the game in a DOS emulator or natively on linux means that bit by bit, people who use RetroPie gaming systems can move from using DosBox or an emulator to play the game (such as heretic), into using the native Linux operating system (such as on there Raspberry-PiZero or Pi3b, both of which can run on batteries as handheld with a small screen). Not only does this unleash the power of a retropie RaspberryPi device to utilise more of its full potential, but also it means modern mods and patches can be written to exploit RAM and other resources (more CPU power to integrate comms/chat features like XMPP including webcams which would use the ProtectionRings of the pi3b CPU in a VM). An example of a game, were it to be opensourced one day, that has had modern features added from both patches an mods is ut2004 (for linux or MSWindows) which uses dual core since patch v3369 but also RayTracing. It also uses dx11 but the OpenGL equivalent is yet to catch up to be rereleased.

Such games become scalable and modern features like adding xmpp chat in Movim or video-conferencing (such as in linux using a ps2 eye-toy camera or something more modern) are the upgrades that require the extra RAM, cpu power, and features such as protection-rings, thereby keeping open source communites engaged and able to organise multiplayer games or highscore rankings of single player gaming.

Breaking away from locked down android and zealous private company policing of "acceptable vocabulary" in Discord or Twitch style chat functionality, games such as Heretic can be on self-hosting Movim XMPP RetroPies like a pi3b as a handheld and using more of the 1GB RAM for added functionality as well as improved graphics and level design.

But why mention all this now? GTK4 is now out (using Glade, and can also run on MacOS) and with it, not only does the software allow for the design of Widget-Toolkit GUI software (which its GTK1 old DOS release had also done) but it can allow for movement of tiles (drag-and-drop), file-transfer, playback of video and 3D using software rendering or OpenGL, thereby meaning entire games resembling ut2004 (similar to xonotic or Dark-Project) like Heretic could be rewritten and compiled within a GTK4 app linking to Movim XMPP or even an IM, and using the video-conferencing with the protection-rings of a pi3b. The BSD to linux compatibility layer could also make efficient use of running BSD as the native OS on a Pi3b and then running linux in a BSD jail in a similar way to a linux VM, so you could run three PiZeros when each is in a VM as if three retropies are used. Then, self-hosting, all three can be tied together so their video-conferencing becomes three way (and thereby potentially infinite), not just one-to-one peer to peer movim video conferencing. The BSD to linux compatibility layer for a VM is far more efficient than running DOS or MSWIndows in each VM, and you can use more than one core per VM whereas you cannot on say Win98. You also have security updates.

IPFS could add more AltTech but through its distributed network rather than solely using decentralised like movim.

Features such as the drawing widgets in GTK4 can allow for sports-gaming, like a football match on TV, to have strategies drawn on the screen with an arrow or circle, etc.

Until now, many people have been relying on software such as Kodi to tie together all their audio/video media playback with their Emulated retro games software. With the potential for file-transfer and comms in GTK4, all this could change (or at least for video of 1080p and below such as 720p), especially as the pi3bplus is capable of running on battery as portable and it is a known quantity. People can then write their own software in GTK4, sometimes even with little coding knowledge (in simple applications). The PinePhone is another interesting device that might use some of this potential, running linux.

Now that Saudi Arabia has allowed women to drive just as cars are becoming A.I. driverless (Nelson Muntz, "Ha Ha"), its time to put Movim into a carputer. One of the uses for this is to have the XMPP video conferencing streaming your dashcam footage to your home (or other remote location), probably to be captured in a stream to a remote home-computer maybe via FOSS software similar to OBS or miracast (even though the local carputer might be set up to be a video-recording 'blackbox' in the car itself too).

It basically doesn't matter if Movim video-conferencing only does a video-call via just two computers linked in peer-to-peer at the moment. The carputer could have several cameras "mixed" into say 4 way split screen (like diddykong-racing or goldeneye 4-player on the N64 resembles). The 4 cameras could point out the windows in a Front, Back, Left and Right configuration (or something similar).

Of course, Movim in an HTPC could also have similar functionality. To build the carputer, it would be perfectly possible to choose either a MITX mainboard or to gut-out a laptop. The processing should be fine, as long as a computer is capable of playing Blu-Ray (usually dual-core 1.6Ghz with zacate or AMD graphics APU is fine, but double it to a rasperry-pi3bplus quad core of a 3GHz dual-core to be on the safe side and a little virtualisation ability might help, and future 3D collada support could capture physics from cameras acting as stereoscopic). Having opengl4.4 is nice but if you need opencl, something like a a6-6400k APU gives opencl 1.2 but an AMD 7400k gives opencl2.0 on the apu. Power efficient equivalents would need to be considered as alternatives. A 12volt car stereo can be powered from a modified xbox360 psu at home, if you want an htpc to match the carputer.

Fitting the carputer into a car-stereo bay so a DVDRW is included would be tidy and it also means, if a network fails, you could burn two 1GB DVD-R 8cm discs and pop them in a standard-letter-size (110 x 220 mm) envelope with a first class stamp to friends or family at a nearby postbox, so that within a day or three, at least some footage can get to them (and maybe have a folded Return Address SAE inside the envelope too). Or have the computer installed somewhere in the car it won't get stolen, and the DVDRW drive could simply be connected by a long cable to the car-stereo bay. If the carputer is running Kodi many touchscreen options exist and so can voice-activation.

There is a myth that women drivers are safer drivers. The truth is, men drive more. The self-heating tin of all-day-breakfast exists because of men drivers. Necessity is the mother of invention, and hunger is the brother of indigestion. It is part of men in careers involving driving, as business not just residential. The majority of accidents happen 2 minutes from home. The flooding of women onto the roads as drivers is really just a quantitative easing, creating a hyperinflation of drivers. It is a way to launder funny money. Like alcohol-prohibition era America, more rules paves the way for more corruption. All roads lead to Rome, and when in Rome, the fall of Rome is by driving drunk on girl-powah. That'll put lead in your pencil. When women hold up half the sky, they take up your braking-distance. Women destroyed the environment in creating more roads by exceeding the capacity of those roads already existing. Carpooling spreads diseases. Arguing against it gets car companies and insurers calling you a male chauffeurnist. So with the abundance of falsehoods pre-emptively trying to find men autoguilty, don't get caught out by the social-distancing cameras that only put A.I. red-boxes around the chosen few, and don't get caught out by the establishment's electronic-line-judge or their equivalents to "HawkEye Cyclops" where corruption in sport is in court, found to be rigged. Driving is a sport, and could we be surprised if they'd employ their same tactics there on the main road? Speed cameras have been questioned in the past. Create your own data and have your own specialists, friends and back-ups at hand.

Movim RSS could keep you abreast of new changes on a road before the mainstream media or traffic reports get the information.

An automatic message over the XMPP chatroom or conferencing could send a message and a hash file of the video file you make such as a magnet link to a torrent. When the airbag goes off, a torrent is seeded, and an (atom) RSS published. War-driving with your IPFS could also be used, and could be a mobile Movim Pod. With that, finding driving routes via a route-finder can be done in a way that finds today's best war-driving route if the journey is tweaked, so maybe even coverage is mapped when microwave or other wireless comms are affected by weather or impaired communications masts.

And if all else fails, make your carputer's A.I. brain one of them #MGTOW wuvbots and you can just call anybody who disagrees with you sexist. If she crashes, she is the primary victim of wardriving for she is the one left behind.

People love PC case building competions and get to strut their stuff.

It also means they get to write a post with an animated GIF in it (of their design) and possibly a collada file from sketchup of their design. It would be so cool in Movm to be able to view a collada file of a 3D model, especially an interactive one you can click to see the lid open in an animation, or for the DVDRW drive to slide open too.

The old UK digital TV "Red Button" switch-over sucked and should have had an rj45 port and a small CPU and xvid h.264 instead of mpeg2. A mobile phone 25MHz cpu would have been something they could have added as a minimum so two-way interaction could have been had. Or even the RISC 68040 found in printers would do (and it would have provided decent IEEE for serial since the 68030, and parallel for the IEEE1284 in the 68040, such as the MC68040FE25V). Even blu-ray players with their ethernet port were better and had java (although frankly the non-foss nature of java is also bollocks and you had to write your own keyboard input back in the day, which was such bullshit).

Fortunately, it is very commonplace for people to build an HTPC these days. It usually leans towards XBMC which is kodi, and that at least means the hardware of an xbox (basically a 733MHz geforce3 akin to radeon 9200le underclocked, not far off an old raspberry-pi or gamecube/wii hardware spec), and this is good because it gives a known quantity hardware spec. At least 4GB of RAM is fair to expect these days, but what with DDR3 in AMD APU systems being so cheap, it would not be unrealistic to expect people to get optimal performance in a 16GB RAM set up. A real HDD should be assumed and that is because the xbox had one (and ideally a sata HDD is used and a sata DVDRW but booting from a USB-HDD is acceptable and a usb-DVDRW is acceptable however linux can complain about usb sometimes). It means swap space can be managed without worry about wearing out a NAND SSD (even if you also have one). Of course it also means files can be stored. It would be nice to also assume that users would have at least 6 or even 8 sata ports (either on the motherboard or added via HBA in a pci-e) to allow one sata-port to be for a DVDRW, another SATA port to be for that bootable Xbox HDD (which has a partition for files and another for swap space), but also, another 6 laptop HDDs of 1TB (4 for the array and 2 for index, thereby giving about 3TB storage) to be BTRFS solely for files (or games) and not the OS. However that would be optional extra, and the existence of all that RAM means files can be used in that (or "partitioned" into a fake HDD like a LiveCD ever since knoppix has done that, or even just debian). So I'd be happy with the assumption that there is always the DVDRW drive and 1 HDD, and so any other drives (like those btrfs) are optional extras but still a known-quantity. When kodi boxes came out on boxes lower in specification than an original xbox it really did defy the point of the known-quantity hardware. I cannot stand that. Somebody always has to mar a nice thing, don't they? Well the spec is now raised again, thankfully so those days are over.

This hyperlink has Movim mentioned with Kodi, so I figured it would make good information as an aside. https://homehack.nl/page/2/

Movim in Kodi is needed, and (especially when a kodi HTPC has 3D capability which usually at least as good as an AMD HD3000 SMA graphics, or an APU such as on a 6400k CPU with APU, or a caicos hd6450) it needs some sort of WebGl 3D interaction (and using SimpleSAMLphp for OAuth2 with OIDC user registration is worthwhile too, possibly also using OpenCL in SciLab) so low bandwidth interaction can be had (such as 3D games with audio, or powerpoint style presentations with 3D similar in graphics quality to CS4 adobe-flash with papervision). A wii-remote should be the assumed controller because the driver is in the linux kernel and has been for about a decade, and a chatpad (e.g. qwerty) could be added. The above hardware spec (if the btrfs is there) blatantly allows for IPFS to be added so people can actually have a decent video network in Standard-Definition (about bitchute quality as DVD quality like an old XBOX, or at most 720p). But really 3D assets would be the great thing. https://neverwintervault.org/cep In the game NeverWinterNights, there was a "community expansion pack". A known quantity expansion pack of sound samples, textures and 3D models about the quality of a gamecube graphics would mean it would be possible for small collada file animations and games like a blender3D or sketchup would be able to be made for everybody even on a low-bandwidth (1 megabit) connection because everybody would already have the "CEP" community expansion pack (presumably released in an ISO file the size of a 4GB DVD, so that if you cannot download it, you can just copy a DVD from your friends, and a hashfile or magnet link checks it is legit). Actually the Movim CEP ISO should be merely 3.5GB so that it could also go on a crap SDCard where they skimp and don't give you the full 4GB. It would be cool if (when the user chooses the "yes/no" tickbox option) the torrent file of this MovimCEP.iso (full of approved public-domain 480p video clips, 3D model collada files, textures, sounds etc.) could be grabbed during installation like wubi.exe used to do, and then the HTPC could serve it to others who need it. In the apocalypse, you'd always get your movim htpc setup.

To be honest, even a dual-ISDN connection would probably be usable as a bandwidth, but 1megabit is a nice easy number and is also the upload speed of a ADSL connection (not ADSL2) in the UK, and after all a HTPC tends to sit under the TV set and can be plugged into a home internet connection. At worst a 3G simcard in a router (as a contingency) would be providing about a third of a megabit (300Kbps), and even that is enough, but 1 megabit is safe to assume in general because the cable comes out the wall.

So I think a (half-height matx) HTPC BOX for Movim should be designed by the community (public domain style) sort of like a competition (except you don't win anything - lol). It would of course be able to take the sata 3.5 inch HDD in the style of an XBOX, and a sata 5.25 inch bay DVDRW drive, standard tray loader, and space for 6 sata laptop HDD drives in case people want the BTRFS. It should take a standard ATX PSU, because a PSU is a pain in the arse if it blows. A minimum 300watt bronze rated PSU could be assumed. I think that is a fairly humble PSU Wattage standard. The HTPC case should also have the ability to be seen (by the human standing or sitting infront of it) as an oblong box with 4 InfraRed recievers (one on each corner) so that the wii remote can work (and bluetooth would be assumed, and that could be bluetooth 2.1 with A2DP). A wifi of both 802.11g and 802.11n should be assumed (but you must be able to turn it off if security is a worry, and so the ethernet can be used instead as default). If the HTPC has additional hardware ability such as better bluetooth or wifi (such as bluetooth4 or 802.11ac then that is fine and I don't care or mind but it must have the aforementioned minimum). It should also have two rj45 ethernet connections at 1GBPS each and I don't care how they are implemented. You could use the onboard rj45 and a usb rj45 dongle combined for all I care. I don't think assuming a person has a ethernet dell i350-t2 is fair (and btw those get faked too often), but it could be an optional extra. Likewise a 8core CPU (Ryzen 7 4700U) could be an optional extra for those who want blake2sp with their btrfs array of 6 sata 2.5 inch HDDs. But realistically, it cannot be assumed as a spec people will own and that is because it is just too expensive and we do not want this to be a "toy for the rich". Having a cheap (at most £10) dual-core A6-6400k using the onboard APU and not dual-channel RAM is reasonable (and people can discover the CPU is very overclockable to 4GHz or even 5GHz if they are truly bothered, and the APU uses little power). But really, the dual-core performance of 3.9GHz is a lot of CPU power, and you could even run docker on one core (even if it is inefficient). This low-spec is enough to get a decent opengl4.4 standard, and can allow for "dual-graphics" (if Microsoft Windows is perhaps chosen and not just Linux) if somebody wants to use a HD6450 with it, or even two in crossfire if they have a motherboard that can do that. The assumption that is that the HD 8460D APU is used (with a minimum 256 megabytes of RAM dedicated to graphics in the BIOS) and without dual-channel RAM. And so that is slow by modern standards but you can still do a lot with it (but if a person has lots of RAM like say between 6GB and 16GB they may wish to dedicate 2GB RAM to the onboard graphics APU as some DirectX11 games or OpenGL games need that, like FarCry2, if a person uses the HTPC also for 3D of that standard even just on low settings when using 3D beyond gaming, although they might also wish to do some humble gaming on the PC too with it). The point is to avoid making it difficult for people. Allow them to have unoptimised systems so at least that have something that works good-enough. The spec is so low that, not only can people often buy it, some people would even give such things away as gifts. The other useful thing about this is that, even if a person has a motherboard with poor expansion options for PCI slots, such as the ASUS a68HM-plus, they still have the PCIe x16 Gen2 slot and a PCI-e x1 Gen2 slot and one PCI-legacy slot. So perhaps one day fast network adaptors in the PCI-e x16 slot (such as an infiniband) become more abundant and they can use that. Or maybe a HBA becomes more abundant so as to put in a great many HDDs. Meanwhile the PCI-e x1 gen2 slot can be used to add two more sata ports so a total of 6 HDDs can be added since the motherboard has 4 sata ports. The legacy PCI slot could be used for IDE pata or sata to add a couple of ports to make 8 sata ports available. It should be assumed that, if the PCI-e x1 slot is used to add two sata ports, this chipset of HBA is used (and this video by Mark Furneaux shows how other chipsets on HBA such as marvell might otherwise fail):

Mark Furneaux video of ASM1061 HBA

Detailed Look At A $6 ASM1061 SATA HBA From eBay

https://www.youtube.com/watch?v=yqQPh8KZhp4

There should be an option for people to boot the Operating System off the parallel port (although it would not be the standard). This also means a parallel port dongle (such as a SDCard reader-writer parallel port adaptor) could be used. It would be acceptable for a Raspberry-Pi GPIO to be used to connect to the parallel port if needed, or just a usb-parallel port adaptor plugged into some other raspberry-pi such as a pi-zero. An extra design for an arduino based (atmega32) chip could be made (vaguely like a lallafa plipbox, but not ethernet) to plug into the parallel port, allowing an SDCard of say 8GB to 32GB to be read to and written to (but preferably a real HDD could be plugged in via sata or IDE in the parallel port dongle so swap space could be used albiet very very slow). It just means the maximum can be squeezed out of the other sata ports (such as 6 sata if the 2port ASM1061 HBA is added) for btrfs without the OS interfering. That optional extra is only for people who want it though. I've always had a thing for booting from a IEEE1284 port ever since 6x speed CDROM (CDRW) drives were a thing as ECP. I cannot resist adding it as an optional extra. You can boot off a parallel zipdisk drive for all I care (in "emergency mode").

People should be able to make their own Movim-HTPC-KODI-PC-Case with tools no more exotic than A4 Paper black-and-white printer templates (pdf), a reciprocating saw (sawzall), a pair of tin-snips, and very humble dremel (or clone rotary tool) and an electric drill and a cheap carbon-steel tap-and-die set. So it would seem likely that Aluminium and thin sheet metal would be materials used, and motherboard stand-offs. No 3D-Printer should be "required". This HTPC must be able to be made poor-man style. Try to keep adhesives simple such as commonly available 2part epoxy-resin and gorilla-glue and contact-adhesive and maybe silicon adhesive if heat is a worry. I think also 2part metacrylate adhesive (while a bit exotic) would be just about "fair" as an adhesive to use because the use of acrylic panels is fairly commonplace in a PC case (if needed). The case could include commonplace sheet metal but even occassional cheap metal (for pic-e blanking plates and) could be made from old tuna tins (cleaned of course). It would make sense to try to use mild steel where possible because paint is cheap. Paint for aluminium can be pricey and that is not so desirable a factor. Extremely cheap parts can be used where possible, but a nice paint job from a spray can can make it look smart. Yes I honestly would use tuna tin metal for PCI blanks.

So yeah, there is no prize. Just use the hashtag #KodiMovimCase so people know what your movim post is about. Mind you, one "prize" is that people would be able to use their Movim Kodi boxes to access content at least as good as my amazing post I have written here (and with 3D graphics somehow). I might make a proper list of criteria but frankly, this post has all the information needed. I am assuming vanilla debian would be a default Operating system even though I'd like slackware and OpenIndiana options to exist, but basically, it would be down to the nature of KODI's most commonly chosen kernels (rather than me getting what I want). I really like the idea of the legacy PCI slot having a terratec ews88mt sound card being plugged in to people can start to use the box for good content creation, in a full-height version. It would mean decent linux drivers get written for that old card in slackware (or even OpenIndiana), but that will need to be another "optional extra" and it would require a full height case (which I am trying to avoid so as to keep the HTPC slim). The PC case being slim also increases the chance of a person putting it in their living room (lounge) where it can be seen, and so the four InfraRed (probably usb IR) recievers can be seen on the 4 corners and used with the wii-remote. Also two playstation3 (720 pixel) usb web-cameras should be able to be plugged in with one on each corner. This means that a 3D stereoscopic image could one day be made in software. So even if just one camera gets used (and after all both can be unplugged if privacy is a concern), it means the PC case has potential for usage with the Movim XMPP video conferencing in future. I imagine what people would do is decide that, even though their own MovimKodiCase must conform to fit the asus a68hm-plus motherboard (which is FM2), that they will have their own desired hardware spec so that they, for example, have a matx motherboard taking something similar in speed such as an am3 socket Athlon II x2 220 Chip and a HD6450 (or r5 230), and then one day they decide to upgrade the CPU to a fx8350 and the GPU to a rx570. That is fine to do, just as long as the previous motherboard FM2 asus a68hm-plus can fit in for everybody else. It probably will mean that people submitting designs will choose two designs whereby one is a half-height and the other is a full height (so they can put their new graphics cards in). In that situation, mark your movim post with the additional hashtags #MovimKodiCaseFull and #MovimKodiCaseHalf also.

One last thing, the movim KODI HTPC should expect the user to be able to plug in a Realtek RTL2832U for digital TV. They are £10. If SDR Software Defined Radio is used through such a dongle, well that might be a thing too. Apocalypse reasons. The MovimHTPC would of course be able to be used worldwide. So yeah those are my specs. You may suggest other spec but the chances are this comment will be the final word on the bare-minimum specification because a line has to be drawn somewhere. And yes I know, I too would love 8core minimum for btrfs and better instruction sets and a Radeon rx570 but we have to be realistic. This should be something easy enough that people make them for cheap and give them to a friend or three as gifts. Until the battle of vulkan and OpenGL4.5 and Directx12 is won (with at least 3 versions coming out), this old OpenGL4.4 (if the HD6450 is added, and it probably would be that matx Asus a68hm-plus motherboard that gets used, but you may squeeze in a different motherboard model as long as the case also works with the a68hm-plus) should be used for many years. You do after all get the ability to have two monitors. That could mean one is for the TV screen and the other is a kiosk touch-panel or handheld touchscreen. It would be nice to imagine people would one day have the option to use their a6-6400k machine as a movim "pod" in addition to it running Movim as standard and Kodi (because eventually people would expand from 4GB and stick the 16GB RAM in). Maybe even some sort of IPFS gets flung in to use that 2TB of that btrfs array of HDDs. Digitally communicating over that SDR might be a nice thought experiment. Link to a HTPC by a Movim user