**** BEGIN LOGGING AT Mon Jun 03 02:59:57 2019
Jun 03 03:35:06 <ubptgbot> <powderedtoastman9000> I got LXC running with Android in a container on my S9 using lineage 16.0, but the hybris patches aren't working so it's broken AF, I am working on reverse engineering the driver blobs for the S9 and the Pixel XL 3 so those devices should work when I get hardware working, then I'll patch stuff as I go. I have the thing runnin
Jun 03 03:35:06 <ubptgbot> g on 15.1 and 16.0 both... But my lineage ports are ugly and hackish because I just override stuff and force config options with comments saying FIXME and my zerorax nick to tell me where I need to do things properly later. i got kmesg dmesg and logcat running on 16.0, and I am working on hardware support, I'm calling the new HAL hal-hal because it
Jun 03 03:35:06 <ubptgbot> 's a HAL for halium
Jun 03 03:35:55 <ubptgbot> <powderedtoastman9000> Also, I have aarch64 rootfs running and my GPU support works and I have mir running with no DE, but that's all I've accomplished
Jun 03 03:37:55 <ubptgbot> <powderedtoastman9000> I would say in 1 year from now halium 15.1 and 16.0 will be usable, and you can expect much easier porting because I'm working on like 13 phones that all different in driver structure, but I don't know anything about GSM, so either I will need help with modem binary support or I will have to spend a lot of time learning it
Jun 03 03:39:57 <ubptgbot> <powderedtoastman9000> I am supporting Galaxy S series, Pixel series, and OnePluse 7, as my initial devices, any recommendations for other devices I should focus on initial support for?
Jun 03 03:42:24 <ubptgbot> <powderedtoastman9000> By supporting I mean I am using their driver blobs as blueprints for my HAL, so those devices will all work, and I am planning to make a custom recovery that can boot Android or Halium from same device without reflashing, but I haven't started that yet, and I am using a rolling release model for updates, apt will update the d
Jun 03 03:42:24 <ubptgbot> evices with PPA for halium and UT components that aren't in the system image or rootfs
Jun 03 05:31:48 <ubptgbot> <Fuseteam> that sounds like a lot of devices already o.o
Jun 03 05:40:38 <ubptgbot> <Fuseteam> would be nice if you could show what you got, even if its a work in progress
Jun 03 06:54:34 <ubptgbot> Cryptomikes was added by: Cryptomikes
Jun 03 06:55:09 <ubptgbot> <Flohack> @Cryptomikes [Cryptomikes was added by: Flohack], Botcheck: What is 2 + 2 ?
Jun 03 06:56:40 <ubptgbot> <AkshitGarg> @Flohack [Botcheck: What is 2 + 2 ?], Better ask 0.1 + 0.2
Jun 03 06:56:46 <ubptgbot> <Flohack> lol
Jun 03 06:56:52 <ubptgbot> <Flohack> Botcheck failed nevertheless 😆
Jun 03 07:17:57 <ubptgbot> <tshering1980> @powderedtoastman9000 [I am supporting Galaxy S series, Pixel series, and OnePluse 7, as my initial dev …], Any chances for Nokia Android One series ?
Jun 03 10:22:33 <ubptgbot> <powderedtoastman9000> @Fuseteam [would be nice if you could show what you got, even if its a work in progress], I'm not happy enough with it to post it, but I'm working on it, it's really a bad mess of poorly put together stuff, I will post it when there's no more FIXME comments in like every damn file... I'm probably going to start it over again
Jun 03 10:22:33 <ubptgbot> with a proper android_build repo that isn't a mess of forced options, also it doesn't do anything yet. I'll probably post within a couple weeks
Jun 03 10:41:49 <ubptgbot> <powderedtoastman9000> I'm probably going to start over again anyways, because I usually redo projects like 4 or 5 times before I get it in a way I'm happy with... I never use my first attempt because it's always below my standards for myself
Jun 03 11:16:04 <ubptgbot> <NotKit> @powderedtoastman9000 how did you get Mir working though?
Jun 03 11:16:22 <ubptgbot> <NotKit> would be good to see the code even if it is ugly
Jun 03 13:03:04 <ubptgbot> <powderedtoastman9000> TheKit, I reverse engineered the GPU driver blobs and compiled it static link... I have a empty screen with a cursor that doesn't move with touch screen
Jun 03 13:04:06 <ubptgbot> <powderedtoastman9000> But it's just loading, I have no way to test usability or stability at this point... It probably doesn't actually work
Jun 03 13:04:38 <ubptgbot> <powderedtoastman9000> It does load and display a little cursor arrow, which isn't even a character it's just drawn at a static spot
Jun 03 13:05:31 <ubptgbot> <powderedtoastman9000> I am ditching hybris because after years of trying no one can get a 100% hardware support 100% functional UT with it, and I tried the patches for hybris to work on 9.0 with no luck
Jun 03 13:05:45 <ubptgbot> <powderedtoastman9000> Basically I've spent a month or 2 doing like 3 days of work lol
Jun 03 13:06:32 <ubptgbot> <powderedtoastman9000> I been busy with life, and I don't have the same time to code as I did 2 months ago, so expect progress to be slow
Jun 03 13:07:39 <ubptgbot> <powderedtoastman9000> I just want a perfect platform with everything perfect, I stayed up all night reverse engineering the modem binary to figure out how to interface with it, I have about 200 lines of notes and that's not even close to what I need to do this
Jun 03 13:08:55 <ubptgbot> <powderedtoastman9000> Like, to me, UT having most stuff working and being usable for most cases isn't acceptable, it has to be perfect, and I'm having trouble finding qualified devs to help me, which I need, not because I lack the skills but because it's a major undertaking
Jun 03 13:09:36 <ubptgbot> <UniversalSuperBox> It'd help if any of those qualified devs could see what you were doing
Jun 03 13:12:21 <ubptgbot> <Fuseteam> basically let devs help you reduce the number of fixmes :3
Jun 03 13:12:26 <ubptgbot> <powderedtoastman9000> Wait till I fix the build system and device trees and I just hacked the hell out of lineage to get it ported and it was totally improper, also I don't know anyone who can read aarch64 assembly. I'm trying to convince 2 devs I know to work on it with me. If anyone knows how to reverse engineer and knows aarch64 assembly I can
Jun 03 13:12:26 <ubptgbot> link them my Google drive backup
Jun 03 13:13:54 <ubptgbot> <powderedtoastman9000> Yeah, I know I Should, I'll work on getting it up to my standards and post it, right now it's just a 48gb tar file in Google drive with aes256 encryption
Jun 03 13:14:33 <ubptgbot> <powderedtoastman9000> I'll try to get it ASAP in a condition where I'm proud enough to post it, and also I need to learn to use Gerrit repo servers because dealing with git is a pita
Jun 03 13:14:48 <ubptgbot> <UniversalSuperBox> Show, don't tell. If you're going to do something that we've all recommended you don't do, make it work before hyping it up
Jun 03 13:15:04 <ubptgbot> <UniversalSuperBox> Publicly make it work
Jun 03 13:15:58 <ubptgbot> <powderedtoastman9000> Okay, I'll just shut up about it till it's done
Jun 03 13:16:25 <ubptgbot> <powderedtoastman9000> Or at least usable to a certain extent
Jun 03 13:17:26 <ubptgbot> <powderedtoastman9000> No more progress reports until the report is "it's ready for alpha builds"
Jun 03 16:02:42 <ubptgbot> <jamesisaweeb> is recovery in the docs the same as fastboot? hybris-install is saying please make sure the device is attched via USB in recovery mode
Jun 03 17:24:35 <ubptgbot> <jamesisaweeb> How do I force CONFIG_DUMMY in defconfig to be false, whenever I put 'n' it doesn't work
Jun 03 17:29:34 <ubptgbot> <powderedtoastman9000> Is it in both the default and device specific defconfigs? Because one may override the other
Jun 03 17:30:17 <ubptgbot> <jamesisaweeb> it's set as 'n' in the device's defconfig but i'm not sure about the default ones
Jun 03 17:30:21 <ubptgbot> <powderedtoastman9000> Also, you can disable the make mrproper call in the build system and switch from defconfig to . config file and that's what I have been doing
Jun 03 17:31:10 <ubptgbot> <jamesisaweeb> How would I do that?
Jun 03 17:31:12 <ubptgbot> <powderedtoastman9000> I don't use defconfig because it always caused me problems and I didn't care to do the research when my approach is simple and easy and works perfect
Jun 03 17:31:47 <ubptgbot> <powderedtoastman9000> You need to edit some config files in the build directory, I forget which one, change make mrproper to make clean, so you clean but don't purge the config
Jun 03 17:32:26 <ubptgbot> <powderedtoastman9000> It's not something I remember how to do, just grep your build folder for "mrproper" and you should find where to change it
Jun 03 17:34:06 <ubptgbot> <jamesisaweeb> Okay, just out of interest where is the default defconfig
Jun 03 17:49:59 <ubptgbot> <powderedtoastman9000> In the same folder as the device specific one, arch/arm/configs or arch/arm64/configs
Jun 03 17:51:01 <ubptgbot> <powderedtoastman9000> But if I know the system as I think I do, the device specific one SHOULD override the default, but I don't know really, I just know that defconfigs were annoying so I stopped using them and used .config and Kconfig
Jun 03 17:51:27 <ubptgbot> <powderedtoastman9000> I fixed Bluetooth and wifi by switching to a manual config instead of defconfig
Jun 03 17:53:35 <ubptgbot> <powderedtoastman9000> Like the kernel modules were not set up to run or be compiled and wifi wouldn't see 5ghZ networks, and using a .config I was able to override the defconfig settings and like magic stuff started working like it was supposed to according to the defconfig
Jun 03 17:55:37 <ubptgbot> <jamesisaweeb> thanks for the help!
Jun 03 17:56:44 <ubptgbot> <jamesisaweeb> i think i've fixed it now
Jun 03 17:56:55 <ubptgbot> <jamesisaweeb> but now the phone just bootloops
Jun 03 17:57:36 <ubptgbot> <jamesisaweeb> and i can't get any logs becuase telnet doesn't open in time
Jun 03 17:59:28 <ubptgbot> <powderedtoastman9000> You can get logs from custom recovery with adb or just read them in terminal, but if your boot looping due to filesystems not mounting there will be no logs, the way I fixed this was disabling ext2 and ext3 drivers and enabling the option in ext4 drivers to support the 2/3 ones
Jun 03 17:59:40 <ubptgbot> <powderedtoastman9000> If you have TWRP installed grab the logs that way
Jun 03 18:00:16 <ubptgbot> <jamesisaweeb> i'll take a look, thanks!
Jun 03 18:01:34 <ubptgbot> <powderedtoastman9000> No problem, hopefully that works for you
Jun 03 18:03:41 <ubptgbot> <jamesisaweeb> so i've got the logs from twrp
Jun 03 18:04:14 <ubptgbot> <jamesisaweeb> and at the very end it says this https://pastebin.com/F6DnChTV
Jun 03 18:04:31 <ubptgbot> <jamesisaweeb> is that normal?
Jun 03 18:12:55 <ubptgbot> <jamesisaweeb> ok it no longer bootloops but now it just freezes and doesn't do anything
Jun 03 19:15:46 <ubptgbot> Chris Wyatt was added by: Chris Wyatt
Jun 03 19:17:37 <ubptgbot> <powderedtoastman9000> Is SeLinux enabled?
Jun 03 19:18:55 <ubptgbot> <powderedtoastman9000> You want to set in kernel config to enable it but allow boot line arguments and in the kernel command line specify SeLinux=0 … You also want an empty file called .writable_image in your.partitions, and audit=0
Jun 03 19:19:02 <ubptgbot> <jamesisaweeb> does config_audit=y mean it's disabled or not?
Jun 03 19:19:25 <ubptgbot> <powderedtoastman9000> You want it enabled in the kernel but disabled with the kernel command line arguments
Jun 03 19:19:49 <ubptgbot> <powderedtoastman9000> I am not sure why they would make that do it that way, seems ridiculous to me
Jun 03 19:20:17 <ubptgbot> <powderedtoastman9000> My kernel command line is console=tty0 selinux=0 audit=0
Jun 03 19:21:19 <ubptgbot> <powderedtoastman9000> You should use the halium-boot kernel config checker script in halium/halium-boot to check that you have the right kernel options selected, it will check for missing or wrongly set options
Jun 03 19:22:05 <ubptgbot> <jamesisaweeb> so i want config audit on in defconfig?
Jun 03 19:22:10 <ubptgbot> <powderedtoastman9000> If you append -w to the end of the command it will fix them automatically but you should disable apparmor until you get all your hardware working or so I was told
Jun 03 19:23:48 <ubptgbot> <jamesisaweeb> alright, all fixed
Jun 03 19:23:55 <ubptgbot> <jamesisaweeb> so I rebuild now, right?
Jun 03 19:24:13 <ubptgbot> <powderedtoastman9000> Do ARCH=arm64 make defconfig device_name-defconfig then do ARCH=arm64 make menuconfig and set up your kernel, then run the kernel config checker on the .config file in the kernels main directory. Once you're done, replace both defconfigs with copies of the .config file, that's what I did a couple times
Jun 03 19:24:29 <ubptgbot> <powderedtoastman9000> Yeah, yay for excessive compiling of stuff you don't need haha
Jun 03 19:24:46 <ubptgbot> <powderedtoastman9000> What device are you working on anyways?
Jun 03 19:24:54 <ubptgbot> <jamesisaweeb> scale (huawei y6)
Jun 03 19:27:06 <ubptgbot> <powderedtoastman9000> Ewww huawei
Jun 03 19:27:53 <ubptgbot> <powderedtoastman9000> They are banned from using Google products, no more updates, no Play store, no nothing unless you count Chinese back doors and spyware
Jun 03 19:29:03 <ubptgbot> <powderedtoastman9000> Tech from China always has privacy I invasive back doors and such because China is a big brother state... When Nexus phones switched to huawei I started buying Samsung
Jun 03 19:38:26 <ubptgbot> <jamesisaweeb> yeah i was trying to install ubuntu touch so i didn't have the nasty huawei stuff on there or the rather buggy build of los 14 for it
Jun 03 19:40:12 <ubptgbot> <NotKit> @powderedtoastman9000 [Ewww huawei], honestly if they didn't do things like locked bootloaders, I would attempt to port on Huawei phone, since as Russian I don't like single country to monopolize on tech
Jun 03 19:40:41 <ubptgbot> <powderedtoastman9000> For mother Russia!
Jun 03 19:40:51 <ubptgbot> <powderedtoastman9000> I'm not Russian but all my friends are
Jun 03 19:41:09 <ubptgbot> <powderedtoastman9000> Like I have 7 IRL friends and they all are born in Russia
Jun 03 19:42:00 <ubptgbot> <powderedtoastman9000> I live in a area where everyone is Russian Persian or Chinese... I'm a minority as a white Canadian who was born here
Jun 03 19:42:01 <ubptgbot> <ankaos> @powderedtoastman9000 [Is SeLinux enabled?], No
Jun 03 19:43:05 <ubptgbot> <powderedtoastman9000> Enable selinux so your selinux contexts get processed and don't cause errors, then disable it with the kernel command line argument, otherwise some parts of the kernel will choke and gag on the contexts, especially if they are in fstab
Jun 03 19:45:37 <ubptgbot> <powderedtoastman9000> Ideally the selinux contexts could be removed and filed containing them formatted to work without them, but that's a large task and would have to be done for every port that people make
Jun 03 19:46:31 <ubptgbot> <powderedtoastman9000> Wait, is your /system partition not existing or is it just empty? If it's not there you might need to run fix-up mountpoints and edit your fstab file, it's handy to have a nice big partition to use
Jun 03 19:47:01 <ubptgbot> <jamesisaweeb> does it not run in make?
Jun 03 19:47:28 <ubptgbot> <powderedtoastman9000> I don't know honestly, but fstab being missing that partition wouldn't get checked in make
Jun 03 19:47:49 <ubptgbot> <jamesisaweeb> should i run it on the host or on the phone?
Jun 03 19:48:02 <ubptgbot> <powderedtoastman9000> Host
Jun 03 19:48:14 <ubptgbot> <jamesisaweeb> do i need to rebuild afterwards?
Jun 03 19:48:14 <ubptgbot> <powderedtoastman9000> Before building the halium-boot and system images
Jun 03 19:49:55 <ubptgbot> <jamesisaweeb> it's saying ```sed: no input files```
Jun 03 19:50:53 <ubptgbot> <powderedtoastman9000> Yes, you always need to rebuild. if you don't have ccache enabled, consider enabling it, you do "export USE_CCACHE=1" and you should put that line in ~/.bashrc so it's always set
Jun 03 19:51:15 <ubptgbot> <UniversalSuperBox> @jamesisaweeb [it's saying sed: no input files], Sounds like your fixup-mountpoints file is wrong
Jun 03 19:51:24 <ubptgbot> <jamesisaweeb> heck
Jun 03 19:51:39 <ubptgbot> <powderedtoastman9000> There we go, Dalton is the wizard of this stuff
Jun 03 19:52:56 <ubptgbot> <jamesisaweeb> @UniversalSuperBox shall i send mine over?
Jun 03 19:53:02 <ubptgbot> <powderedtoastman9000> Maybe you can elaborate @UniversalSuperBox  so he knows how to fix it?
Jun 03 19:53:26 <ubptgbot> <UniversalSuperBox> I'm not sure exactly what the problem is, but the formatting and syntax must exactly match the one in the documentation
Jun 03 19:53:29 <ubptgbot> <UniversalSuperBox> And all the other entries
Jun 03 19:54:34 <ubptgbot> <powderedtoastman9000> Makes sense, I just copied my mount points from linesgeos using terminal and looking in /dev but it sounds like you are past the point of using lineage
Jun 03 19:54:41 <ubptgbot> <jamesisaweeb> hmm, i think mine looks okay https://pastebin.com/aCN3vSme
Jun 03 19:54:54 <ubptgbot> <jamesisaweeb> or at least compared to the other entries
Jun 03 19:55:40 <ubptgbot> <powderedtoastman9000> I would recommend not using block devices by name, it leaves more margin for errors or issues, I put mine as the actual block device of the partitions and it worked great.
Jun 03 19:56:28 <ubptgbot> <UniversalSuperBox> You are running it through the build system, right?
Jun 03 19:56:33 <ubptgbot> <jamesisaweeb> yes
Jun 03 19:56:35 <ubptgbot> <UniversalSuperBox> `make hybris-boot`?
Jun 03 19:56:59 <ubptgbot> <powderedtoastman9000> Isn't the recommended way to use halium-boot now?
Jun 03 19:57:13 <ubptgbot> <UniversalSuperBox> Yes, but the docs say hybris-boot for getting the initial booting done
Jun 03 19:57:27 <ubptgbot> <UniversalSuperBox> And PM may not use that
Jun 03 19:58:31 <ubptgbot> <powderedtoastman9000> Oh okay then... I had issues with hybris boot on all my Galaxy S devices... Halium-boot worked great, so I didn't bother figuring out why hybris-boot wasn't working since I didn't need it
Jun 03 20:00:44 <ubptgbot> <powderedtoastman9000> PM is postmarketos?
Jun 03 20:00:50 <ubptgbot> <UniversalSuperBox> Plasma Mobile
Jun 03 20:01:26 <ubptgbot> <powderedtoastman9000> Oh, okay. Plasma is halium based?
Jun 03 20:01:35 <ubptgbot> <UniversalSuperBox> The Neon images are
Jun 03 20:01:39 <ubptgbot> <powderedtoastman9000> You can tell I haven't kept up with non Android ROM options lol
Jun 03 20:01:53 <ubptgbot> <powderedtoastman9000> Oh okay, cool thanks for the info Dalton
Jun 03 20:02:26 <ubptgbot> <jamesisaweeb> how well does plasma mobile work anyways?
Jun 03 20:02:53 <ubptgbot> <jamesisaweeb> i haven't seen anything other than that prototype video about it
Jun 03 20:02:56 <ubptgbot> <NotKit> not ready for daily usage
Jun 03 20:03:06 <ubptgbot> <NotKit> only for developers for the moment
Jun 03 20:03:14 <ubptgbot> <jamesisaweeb> i see
Jun 03 20:10:07 <ubptgbot> <powderedtoastman9000> So there is no builds available for download?
Jun 03 20:10:54 <ubptgbot> <NotKit> there are for Nexus 5X
Jun 03 20:11:19 <ubptgbot> <powderedtoastman9000> I would love to check out some alt ROMs, just to see what I'm trying to complete with, maybe get some ideas for things I should consider... I want a pine phone really, they said all the dev kits were allocated so I gotta wait until they make a batch to play with them
Jun 03 20:11:51 <ubptgbot> <powderedtoastman9000> I have 2 Nexus 5X but both bricked during normal usage with stock ROMs and I hear they are really common to brick for no good reason
Jun 03 20:16:14 <ubptgbot> <powderedtoastman9000> I think the halium 5x kernel is really bad though, like I think it needs to be redone from start, I think that kernel is the reason no one can port UT to the device, I investigation some of the compile warnings and they were a mess of bad coding
Jun 03 21:00:16 <ubptgbot> <Flohack> @powderedtoastman9000 [I think the halium 5x kernel is really bad though, like I think it needs to be r …], Well we take all kernels from Lineage, I cant believe all of them would be that bad. And for 5X you need to disable CPU 4-5, and then try again to unbrick. There is a special recovery for that already for Android. Same problem as on
Jun 03 21:00:16 <ubptgbot>  6 and 6P, you can google this probably
Jun 03 21:00:27 <ubptgbot> <Flohack> So there is no "Halium kernel". We dont do kernels
Jun 03 22:05:56 <ubptgbot> <powderedtoastman9000> I know, I'm reinventing the whole thing
Jun 03 22:06:42 <ubptgbot> <aurnytoraink> @Flohack [So there is no "Halium kernel". We dont do kernels], https://github.com/openkirin
Jun 03 22:10:27 <ubptgbot> <Fuseteam> @powderedtoastman9000 [I know, I'm reinventing the whole thing], iirc you're trying to make a 'halium kernel'
Jun 03 22:23:21 <ubptgbot> <powderedtoastman9000> I'm making kernel that will do what hybris does for hardware, and I'm making a new boot system and custom recovery, and I'm just having a lot of fun working on it... I'm not even sure I should call it Halium, because it doesn't conform to what halium is as it stands now
Jun 03 22:25:13 <ubptgbot> <powderedtoastman9000> But I think this is the most logical way to approach the issue of hardware support using blobs, honestly the attitude I've gotten from team members has made me stop caring about whether or not you use it... I would like to see you use it, hopefully it's as awesome as I think it will be, but if you don't want to I'll just roll
Jun 03 22:25:13 <ubptgbot>  my own platform on it and promote it so others do the same
Jun 03 22:27:32 <ubptgbot> <powderedtoastman9000> I can't just write code the way halium is as it stands, because I would not be happy with my work, and I'm in this to do work I'm happy with... The kernel is Linux 5.1, it's not a halium kernel but it will have the HAL inside the kernel as a module, instead of in userspace, and a lot of other things. I can leave if you guys d
Jun 03 22:27:32 <ubptgbot> on't want me to do it, I'll still do it and I'll leave you all alone
Jun 03 22:28:27 <ubptgbot> <powderedtoastman9000> I have about 20% of the modem binary analyzed on my first device to make GSM support, I need to sleep now though I've been coding over 3 days straight
Jun 03 23:54:12 <ubptgbot> <powderedtoastman9000> Re halium not having a kernel, that's part of the problem I think, like why should every device need a kernel that is bugged and needs lots of work and doesn't configure properly or behave as expected... The kernel is the key to universal device support, my work will make porting to a new device almost no work needed, I'm goi
Jun 03 23:54:12 <ubptgbot> ng to merge every device hardware kernel module for every phone into the kernel, and use them as loadable modules, I'll probably make a script to configure the kernel for devices or something so porting is dead simple, right now I have Pixel XL 3 and S10+ running on the same kernel but very little functionality... I'm trying to decide if I port Way
Jun 03 23:54:12 <ubptgbot> land to Mir or drop Mir in favor of xorg
Jun 03 23:55:15 <ubptgbot> <powderedtoastman9000> I'm gonna make it it's own project, cause you all seem to not like what I'm doing and I don't like criticism of my work which is the same reason it's on private repos on git.rocks.i2p
Jun 03 23:58:08 <ubptgbot> <TheSolenya> It will be FOSS, so you guys can use it, but talking about it here makes very little sense
Jun 03 23:59:10 <ubptgbot> <TheSolenya> I just modified the kernel to load kernel modules from system partition so that the kernel can fit into boot partition with all the crap that's in it, using loadable modules, signed with verification for security obviously
Jun 04 00:15:53 <ubptgbot> <Fuseteam> hmmm
Jun 04 00:17:05 <ubptgbot> <Fuseteam> well i'm sure that once you go foss other will see if they can use it or not
Jun 04 00:17:20 <ubptgbot> <Fuseteam> [Edit] well i'm sure that once you go foss others will see if they can use it or not
Jun 04 00:22:20 <ubptgbot> <TheSolenya> Thanks for the confidence
Jun 04 00:28:46 <ubptgbot> <TheSolenya> I just hope I can pull it off as I am intending, I think I can but this has never been done so I can't Google for hints or read documentation... Which is why I think it will be a year for an unstable alpha, and 3 more for stable, if I fail, you can all make fun of me and say I was full of shit
Jun 04 00:29:15 <ubptgbot> <TheSolenya> And I hope UT and Plasma use it when it's done and more projects yet to arise
Jun 04 00:30:11 <ubptgbot> <TheSolenya> Because UT is a damn good project just I want to make it better and have more users that run my code and enjoy it
**** ENDING LOGGING AT Tue Jun 04 03:00:18 2019