• 0 Posts
  • 142 Comments
Joined 2 years ago
cake
Cake day: June 20th, 2023

help-circle
  • Sailing7@lemmy.mltoLemmy Shitpost@lemmy.worldAccommodating
    link
    fedilink
    arrow-up
    3
    arrow-down
    7
    ·
    12 days ago

    I know its a absolute wonky workaround but you could use a second phone and enable google speech input – or an FOSS alternative: FUTO Voice Input (Local LLM Model that works pretty great. Better than google imo. Is better finding the correct words and also putting logical punctiation. – as in when should a comma or dot appear.)

    Now you enable speech input on one phone and playback the voice message of the dude on the other end. Now you got all the text.


  • Get what you are trying to say but both are still encrypted. They simply aren’t end to end encrypted. So the messages are private. Until obviously the company servers get hacked or police raided and the keys to the encryption get stolen. You are protected against this in E2E encryption. True.

    Ii guess telegram once was the alternative to whatsapp, then made maany more featutes abailable in fast time paces which led to another bunch of migrators.

    Now noone wants to move away because why? For the usual end user there is no negative to them.

    I am fully on your side and am using signal and matrix and try to migrate as many people as possible but its hard.




  • Be aware though if you use DSL: the frequency of the Powerline devices will most likely match and disturb your (in most cases) unshielded two copper wires over wich your DSL Signal is transmitted

    Though this also depends wich DSL Variant you are using.

    For example Super Vectoring - 250k Down /40k Up will have troubles in most cases to uphold packetloss to a minimum.

    All of this is ment to be a thing with DSL Speeds over 100Mbit (at least in Germany).

    Source: I am an IT dude, had DSL Problems, Telekom Technichian was sent out and I talked to him about the causes and such.





  • Try

    • scenenzbs(dot)com
    • or
    • drunkenslug

    (First one is better.) To get .nzb files. Then use a Usenet Access Provider. Those save all files shared via usenet over a predefined time period. – though some archive different usenet publications than others. Simply differs by what servers they connect to afaik.

    Not entirely sure on the architectural work here but thats the best you’ll get from me in a minuite.

    Search for diffetent providers. Check the link for them. Maybe the available payment methods might be worth a look.

    Eweka supports paypal i think, but not sure on this one.

    For automation you will need an api access to the sites from the bulletpoints above – the free access gives very limited access via api. Which is why automation tools fail on a free account to automatically download new episodes .nzb files from them.






  • Currently I simply dont.

    On Xenn you should be capable with the correct drivers to put a couple of virtual GPU Profiles on your VMs to use.

    On Hyper-V there is a command out there, but I don’t know if its a dedicated access or if you are capable of sharing it across multiple instances.

    On Proxmox though? Not sure but i think it was possible to forward it to a VM but thats all. Just dedicated acces afaik.


  • Just for the sake of testing maybe try it with a oneliner:

    sudo mount -t cifs -o user=testuser,domain=testdomain //192.168.1.100/share /mnt

    Either way using the logs is the best way to check for discepancies. Also check in on the logs on the fileserver. Though idk what to advice to trace the logon stuff and trace whats making it fail.

    Just for the case that you dont know where to look in windows: eventviewer is the place to go. Which predifined filter though - simply google that.

    Wishing ya the best of luck mate!



  • Well not so much the adress of the AD server.

    It should be the domain name of your domain that you have created.

    As in Joh.Doe@CompanyWork.internal

    The part behind the @ is the domain the user is registered to and even though the AD server might be named prod-ad-001 the text should be the domain you are trying to auth towards and the share you are accessing to should obvioisly have a connection the the AD to forward the credentials and ask if Auth is positive.


  • In FSTAB:

    //192.168.188.52/media /home/shareuser/shared/ cifs vers=3.0,credentials=/home/shareuser/.smbcred,uid=1000,gid=1000,iocharset=utf8 0 0
    

    In .smbcred are the credentials. The content of the file:

    username=shareuser
    password=shicjwvfiak                        domain=192.168.188.52
    

    Should work.

    Instead of the IP put the FQDN of your Share holding Server and make sure DNS is properly working.