Nostr

mleku 2y ago

just want to share some notes about my experience with simplex desktop.

go here to download the appimage: https://simplex.chat/downloads/#desktop-app

you can then:

chmod u+x ~/Downloads/simplex-desktop-x86_64.AppImage

assuming you use standard download location.

and run it:

~/Downloads/simplex-desktop-x86_64.AppImage

then magically, back in your terminal (open another session), check your mounts, and you will see a new entry at the end of the list, something like this:

simplex-desktop-x86_64_594d9f9f940c843946e86def816d28d1.AppImage on /tmp/.mount_simpleNlnGNH type fuse.simplex-desktop-x86_64_594d9f9f940c843946e86def816d28d1.AppImage (ro,nosuid,nodev,relatime,user_id=1000,group_id=1000)

the important part is the second bit:

/tmp/.mount_simpleNlnGNH

cd to it:

and you'll see this:

AppRun chat.simplex.app.desktop simplex.png usr

you want to copy the .desktop and .png files to your profile:

cp chat.simplex.app.desktop ~/.local/share/applications/

cp simplex.png ~/.local/share/icons/

then the last step, to make it all stick:

cd ~/Downloads

cp simplex-desktop-x86_64.AppImage ~/.local/bin/simplex

and voila, you will now have a desktop icon that can launch it, and from terminal `simplex` will also launch it.

Reply to this note

Please Login to reply.

Discussion

mleku 2y ago

nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9rhwden5te0wfjkcctev93xcefwdaexwtcpr3mhxue69uhkx6rjd9ehgurfd3kzumn0wd68yvfwvdhk6tctty609 wen markdown?

hodlbod 2y ago

never, but it is supported for long form content

mleku 2y ago

wen button for 'long form post' ?

Ademan 2y ago

On the fediverse markdown is very common even for microblogging, it's incredibly handy. Heck I just saw a screenshot of json on here a second ago, that would be perfect in a markdown code block.

hodlbod 2y ago

I also feel the pain, but for interoperability purposes notes need to be plaintext, this revelation comes down from on high by our revered master fiatjaf

arkinox 2y ago

*the

mleku 2y ago

the fiatjaf, esquire! Laird of the NOSTR

mleku 2y ago

i think that you could easily write a script that scans a post for signs of being markdown and renders it as such if it finds more than a few instances of `\n## something` and ` some quoted shell command' sorta things.

the way that my post got utterly mangled using 4 space prefixed references to filesystems the thing is unreadable on coracle.

mleku 2y ago

at least to have a checkmark at the bottom of the input to tag it as long form type note so the interface doesn't turn it into a giant poo like that one here.

hodlbod 2y ago

We should probably add a new event kind that is markdown, that's probably the best way to handle it. Or clients could support "rich text" mode and publish 30023's, but that would cause other problems.

Ademan 2y ago

What's the problem with 30023 that wouldn't affect a new event kind?

hodlbod 2y ago

They're assumed to be blog posts, so to start publishing short notes with that kind would screw up long-form clients

mleku 2y ago

and coracle assumes that all posts are what exactly? and why can't i write long form in this?

should i be moving to use another client?

Ademan 2y ago

I assume Coracle would handle this correctly, but the implication is that "blog reader" type clients would start seeing people's short social media posts in their feeds which is not the sort of content they want, even though it's the same nostr kind. Separating it into its own kind (even if the contents are compatible) would prevent this bleed over.

mleku 2y ago

i see, so the spec doesn't have an opinion about short form having markup and i'm just having trouble trying to understand why rendering if found would be a problem.

i've been writing every length of form in markdown for a long time and have been wishing since at least 2016 that it was just a standard thing to *italicise* and **bold** and _underline_ and

- make

- lists

and quote things

that are probably from a terminal

because i am constantly needing all these things.

i don't use headings so much, that's more of a structured long form document, and for those, it's been a really long road to table of contents showing the outline to be normally available somewhere (github now puts them at the top of a markdown document rendering.

i'm keeping my ear open to hear about when markdown formatting comes to short form messages because, it predates even 2015, actually, once upon a time before markdown there was bbcode.

it was the silos that siloed users away from this.