• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle




  • I would be careful with some of these providers depending on your usage.
    You are potentially sending a ton of info to them…

    I have access to Bing Chat Enterprise through my company, and only because its the Enterprise version i am half confident in using it with more restrictive data.
    Though the frontend of copilot is so heavy and sucks, so i have a proxy for GPT-API to Bing Chat.
    Had hoped GPT4All Bing provider would support login, but sadly not, so essentially had to reimplement it all myself.





  • Copilot is weird and can give out very weird responses that have little to do with your conversations.

    And of course it might just grab context depending on what you do (e.g. clicking the copilot button might already do that).

    I found it works best as GPT model if you disable the fancy stuff like search. It too easily looses track of what happened or completly goes off the rails.
    (i believe disabling search is a beta feature in some regions, but its a hidden flag you can theoretically set, i made a tampermonkey script to add a button).

    I hate the slow UI of Copilot, so i translate requests from a different GPT interface.




  • Better quality releases and more active users with much less leeches as they get thrown out.
    Though there are many site admins with some complex here too… your experience can vary.

    And of course you need to contribute to the community, most trackers will grant you buffer for both uploading and keeping the torrent running. You want something, then you have to give back.
    If the tracker doesnt give possebilities to build your buffer in multiple ways, other than just uploading, its usually a shit tracker.
    And some are just super hard to impossible to get into. Start small, wait for open signups or just go to new trackers, they might get bigger over time.
    Dont publicly beg for invites, you can humiliate yourself in private chats if you are into that.







  • So i understood you just want some local storage system with some fault tolerance.
    ZFS will do that. Nothing fancy, just volumes as either blockdevice or ZFS filesystem.

    If you want something more fancy, maybe even distributed, check out storage cluster systems with erasure coding, less storage wasted than with pure replication, though comes at reconstruction cost if something goes wrong.

    MinIO comes to mind, tough i never used it… my requirements seem to be so rare, these tools only get close :/
    afaik you can add more disks and nodes more or less dynamically with it.



  • afaik, most if not all modern browsers and clients in e.g. apps, use Diffie-Hellman key exchange in TLS.
    Some Apps go even further and implmement certificate pinning, only allowing a set of specific certificates the server is allowed to “present”.

    You can only break it by an active Man in the middle attack, presenting your own Diffie-hellman parameters toeachother and signing them with a certificate the client trusts (we can probably assume US agencies have access to some CA keys and can do this)

    I dont think this is very feaseable on a large scale as you’d need to intercept every interesting connection, break the handshake, risking detection, and further proxy and process the whole traffic.
    Metadata will be more juicy en mass than the content and easier to obtain with less risks.