@Humpleupagus @tyler @cowanon @curiousthinker @dem @m0xee I prefer vim. I have the same problem in nano that nano users have in vim: Save and exit will often lead to new characters being appended while I adjust my pea brain to the command syntax.
@thatguyoverthere @tyler @Humpleupagus @cowanon @curiousthinker @m0xee lol same happens but with emacs binds
@dem @tyler @Humpleupagus @cowanon @curiousthinker @m0xee I think at the end of the day all the $EDITOR wars discussion is interesting but really what matters is whether you can use the software. I am completely lost in emacs, but I hear the same complaints about vim and I'm completely happy with my own ability to use it.
@thatguyoverthere @tyler @Humpleupagus @cowanon @curiousthinker @m0xee lol both are complicated. vim i can get away with no config, emacs need some config from me like chaning the M button from alt to super key
Follow
@dem Same here, vim just has saner defaults — mostly works for me. Of course, you can build upon it and turn it into something more versatile.
But emacs has me completely lost. Mastering some tools feels rewarding, but emacs to me is "oh no, not this… thing again!" I feel like I don't get it's core principle that would make things more fluent. Matter of habits as usual 🤷
@tyler @Humpleupagus @cowanon @curiousthinker @thatguyoverthere
@m0xee @tyler @Humpleupagus @cowanon @curiousthinker @thatguyoverthere for emacs i just need to sit down look at the keybinds and find out what commands i need to know at i would be all set
@dem @tyler @Humpleupagus @cowanon @curiousthinker @m0xee it's a matter of commitment at this point. I learned vim out of necessity, but unless I had some problem I couldn't solve in vim or was prevented from installing it for some reason, but emacs was installed, I'm not likely to go learning it at this point, even if it can do all kinds of non editing things. It would be interesting I guess, but that time could be spent focusing on better problems to solve poorly.
@thatguyoverthere @tyler @Humpleupagus @cowanon @curiousthinker @m0xee only thing i need to really do atm is see why node js gives me a error when i webpack for masodont (3.5 glitch)
@dem @tyler @Humpleupagus @cowanon @curiousthinker @m0xee 
could be a node version mismatch or something. If so there is nvm.sh which makes installing alternative node environments easy. I've not run masto in a while myself. My last instance was pleroma/soapbox
could be a node version mismatch or something. If so there is nvm.sh which makes installing alternative node environments easy. I've not run masto in a while myself. My last instance was pleroma/soapbox
@thatguyoverthere @tyler @Humpleupagus @cowanon @curiousthinker @m0xee i dont think so its that openssl error bs
@thatguyoverthere @tyler @Humpleupagus @cowanon @curiousthinker @m0xee error:0308010C:digital envelope routines::unsupported
@dem @tyler @Humpleupagus @cowanon @curiousthinker @m0xee A sloppy search of the interwebs says could be node version
at this time i am working with node js v17 which not LTS and this version is not compatible with some of webpack, and my previous Node version was v16 which is LTS. in here everything is okey. there is no any error.
@thatguyoverthere @tyler @Humpleupagus @cowanon @curiousthinker @m0xee i should go try 17 lol, i atm dont care to also change my yarn verison
@dem @Humpleupagus @cowanon @curiousthinker @m0xee @tyler looks like the presented solution may be fixable in package.json
> trust me this is every simple and magical. please see below what it should be.
> Go to In your package.json: and change this line
```
"start": "react-scripts start"
```
> to
```
"start": "react-scripts --openssl-legacy-provider start"
```
> trust me this is every simple and magical. please see below what it should be.
> Go to In your package.json: and change this line
```
"start": "react-scripts start"
```
> to
```
"start": "react-scripts --openssl-legacy-provider start"
```
@thatguyoverthere @tyler @Humpleupagus @cowanon @curiousthinker @m0xee webpack-cli does not have that option
@dem @tyler @Humpleupagus @cowanon @curiousthinker @m0xee potential workaround (mileage may vary)
https://github.com/webpack/webpack/issues/14532#issuecomment-947012063
```
export NODE_OPTIONS=--openssl-legacy-provider
```
https://github.com/webpack/webpack/issues/14532#issuecomment-947012063
```
export NODE_OPTIONS=--openssl-legacy-provider
```
@dem @Humpleupagus @cowanon @curiousthinker @m0xee @tyler I get the impression that react-scripts in the previous example would just pass that option off to node anyway
@thatguyoverthere @tyler @Humpleupagus @cowanon @curiousthinker @m0xee https://maso.logografos.com/about looks like this thou kek, better than nothing
@thatguyoverthere @tyler @Humpleupagus @cowanon @curiousthinker @m0xee [4253f72f-dde5-4dde-8703-631b6e4a1380] method=GET path=/packs/media/images/preview-1f18effa56ea793e2897339774674ac2.png format=png controller=ApplicationController action=raise_not_found status=404 duration=1.85 view=0.79 db=0.00
hmmm i wonder what the probelm is, idk how ssv has set this up lol
hmmm i wonder what the probelm is, idk how ssv has set this up lol
@dem @tyler @Humpleupagus @cowanon @curiousthinker @m0xee yeah it looks like 404 across the board for a bunch of css files 
maybe there is a separate step for compiling css? I've never used it so I don't really know, but it's definitely not working as expected even if you didn't hit the same error lol
maybe there is a separate step for compiling css? I've never used it so I don't really know, but it's definitely not working as expected even if you didn't hit the same error lol
@dem @Humpleupagus @cowanon @curiousthinker @m0xee @tyler actually looks like your missing your javascript too. maybe the built files are not in a location where they can be served by your web server
