¡ɹǝpun uʍop ɯoɹɟ ʎɐppᴉפ

  • 9 Posts
  • 69 Comments
Joined 1 year ago
cake
Cake day: July 6th, 2023

help-circle





  • I find Joplin perfect for my needs. Markdown, embedding images, links etc. I sync to my selfhosted nextcloud.

    I like tags, I would like them to add a “directory tree” type of view to help sort “folders” (the thing they call “notebooks”) but only because I am more used to just filesystem type structured filing. But the notebooks and tagging idea works for me too.

    I strictly use it for notes/note keeping, in particular “HOWTO’s” and specific topic notes. So I dont even do a great deal of markdown in my notes, but I love the ability to add screen captures etc to them for clarity.

    And being on nextcloud, I can access those notes anywhere on any device, PC, Android, Raspberry Pi!! Joplin has an app for all of them




  • I know this is not useful for most use cases, but if you login to the desktop on the ‘remote Wayland’, locally first then RD will work as expected. So if you can change the behaviour of the remote desktop to stay unlocked (IE its in a secure place where others cannot just access the device), then and RD will work with Wayland.

    I use NoMachine (since I manage all sorts of devices, and its nice that there is a client and server for everything including phones/arm) and it works for me because many of the machines are actually VM’s and I can keep the desktops unlocked and logged in. NoMachines solution for Wayland - is to disable it and use X11 !!

    But I wish many of the RD developers would just embrace Wayland and add/rewrite code to support it (If it is in their scope, I don’t know) It might not be, since I am aware of Waypipe and Pipewire, but I’d assume that RD devs would still need to include support for that.







  • Thats not how it works.

    You have a LAN and hopefully you have a firewall that shields your LAN from WAN. Your fw is probably handing out DHCP lease IP (like 192.168.x.y)

    When you “bridge” your VM looks like an independant device on you LAN. Nothing at this point has allowed it to the public. Your dhcp can even give it an IP (but its probably better to set a static ip). In bridge mode, a "fake mac is spoofed alongside you nic’s real mac, and only for said VM)

    At that point the VM id accessible likr any other device on the LAN.

    if you then want to use vpn, just connect to your LAN however that works(vpn to computer or vpn to firewall/vpn server) and access.

    if you want to access from WAN without vpn, then you need to understand reverse proxying and youll need a full proper firewall\gateway device at the front of your network (like OPNsense).