| 14 Dec 2021 |
 Jef | In reply to @rnhmjoj:maxwell.ydns.eu
you can delete the [auth] section in nheko.conf This one doesn't really work, where is the message data and everything stored? | 07:45:35 |
 rnhmjoj | In reply to @jef:rustybever.be
This one doesn't really work, where is the message data and everything stored? it should be $XDG_DATA_HOME/nheko/nheko/<some-hash> | 07:46:12 |
| Jef | Ah right found it, I'm guessing that'll work | 07:46:34 |
| Jef | Yup that worked, thx | 07:47:12 |
 nobody | In reply to @seirdy:seirdy.one
it'd make more sense to just launch your preferred image viewer i disagree because i don't want to launch other software just to see one image for what is usually a few seconds | 12:16:55 |
| Jef | In reply to @e:lu.gl
i disagree because i don't want to launch other software just to see one image for what is usually a few seconds well it should be an option that's disabled by default, I doubt many people expect their messaging app to open up another app just for a pic | 12:57:34 |
|  🎅 leipreachán na Nollag joined the room. | 13:44:25 |
| 🎅 leipreachán na Nollag | Noticed a fun thing with Element where if it can't decode the video you're sending, it gives up and sends it with the event type m.file
And even though nheko is capable of playing it inline, it doesn't try because the message sent through Element is m.file | 14:04:40 |
 Nico|dev | Well, yeah, Element should send that as a video :D | 14:05:06 |
| Nico|dev | You can right click, open externally though | 14:05:22 |
| 🎅 leipreachán na Nollag | Could it be so if nheko sees m.file event but can see it's a video, it would display it inline? | 14:06:29 |
| Nico|dev | I'd rather just have the sending client fixed, because that is clearly a bug | 14:18:22 |
| Nico|dev | We already have enough workarounds for Element bugs | 14:18:34 |
| 🎅 leipreachán na Nollag | I think it makes sense from Element's side because it can't display the same video sent through nheko properly | 14:23:45 |
| 🎅 leipreachán na Nollag | So it doesn't see a difference between a video it can't decode and random noise | 14:24:25 |
| Nico|dev | If they know it is a video, they should send it as such. There are valid usecases to send something explicitly as a file, i.e. when it is sensitive content and you don't want anyone to view it, just forward it. I can see why Element sends it as a file, but I really don't want to start interpreting events as something other than they are. | 14:25:21 |
| Nico|dev | Element randomly sends images, videos, audio, etc as files. We don't need different event types, if we need to interpret every file as something else anyway... ._. | 14:26:11 |
 cadence [they] | Element's behaviour of m.file was actually pretty helpful when another client I was using decided to upload my GameCube memory card dump as an image. | 14:52:30 |
| Nico|dev | Sure, but then it won't help, if we start displaying m.file as images | 14:53:15 |
| cadence [they] | exactly :D I was agreeing with you | 14:53:35 |
| cadence [they] | reuploading in element saved the day | 14:53:53 |
| Nico|dev | :3 | 14:54:09 |
| Jef | oke this might be a dumb question but how exactly do i start a dm using nheko | 16:32:58 |
| Jef | do I just create a new room & invite the user? | 16:33:57 |
 FelixActually | Click their name in a room and there's a "start private message" button | 16:34:26 |
| Jef | I'm not in any rooms with them, it's a bot account I gotta send for registration | 16:34:56 |
| Jef | I only know their ID | 16:35:01 |
| FelixActually | Then what you said | 16:35:31 |
| Jef | right, that did indeed work | 16:35:46 |
 Twily | 
Download 2021-12-14 20-27-33.png | 18:28:45 |
