Syncthing Reviews

HTTP Reviews

Syncthing mentions (851)

• Syncthing File Sync for Self-Hosted Knowledge Systems

  Unlike cloud storage platforms, Syncthing uses a peer-to-peer model where each device holds its own copy of synced folders and exchanges changes directly with trusted peers. There is no central server that owns your data, no subscription account, and no vendor lock-in. The project is open-source and community-driven, with more details at syncthing.net. - Source: dev.to / 5 days ago

• The Quiet Renovation at Bitwarden

  Been using this setup for many years and never had any problem at all. I sync between desktop and mobile with Syncthing[0]. And also you can configure Syncthing to do file versioning, and it has many options (Trash Can, Simple, Staggered or External file versioning) so if some weird conflict happens you'll never lose data. But honestly, I have never had any issues, and I have been running this setup for many... - Source: Hacker News / 2 months ago

• Show HN: Stop paying for Dropbox/Google Drive, use your own S3 bucket instead

  Https://syncthing.net/ <- like this :) Free, opensource, works on computers and phones, can in most cases puncture nat, supports local discovery (lan, multicast). No googles, no dropboxes, no clouds, no AI training, no "my kid likes the wrong video on youtube, now our whole family lost access to every google account we had, so we lost everything, including family photos", just sync! (not affiliated, just really... - Source: Hacker News / 3 months ago

• Seafile vs Syncthing: Server vs Peer-to-Peer

  Syncthing is a decentralized, peer-to-peer file sync tool. Devices connect directly to each other — no central server. It does one thing: keep folders in sync across devices. It does this exceptionally well, with block-level delta sync and strong encryption. - Source: dev.to / 4 months ago

• iCloud Photos Downloader

  This will let you download all of your photos that already exist on iCloud Photos. Going forward, you’d want to set up some other way to sync photos you take from your phone to your other devices. I can personally recommend Synology Photos for simplicity[1], or Immich[2] for an open-source (and in my opinion, slightly better) alternative you can run on any hardware, if you’d like to set up an always-on NAS. These... - Source: Hacker News / 6 months ago

HTTP mentions (9)

• The History of HTTP

  HTTP/1.1 was first published as RFC 2068 (The Proposed Standard) in January 1997. HTTP/1.1 protocol was refined over two revisions, RFC 2616 published in June 1999 and RFC 7230-RFC 7235 published in June 2014 before the release of HTTP/2. The HTTP/1.1 standard (RFC 2616) remained stable for over 15 years. In 2022, HTTP/1.1 was updated again with RFC 9110 & RFC 9112. - Source: dev.to / 9 months ago

• State management in Svelte apps

  HTTP was invented as a stateless protocol, which means that each request fully encapsulates all of the information necessary to return a correct response. So historically, web pages never had to worry about managing state - each request to a URL with parameters or with a form submission would receive a response with all of the HTML that the browser needed to render content. - Source: dev.to / about 2 years ago

• Evolving the Web: Discovering the History of HTTP Versions

  HTTP/1.1 was such a game changer for the Internet that it works so well that even through two revisions, RFC 2616 published in June 1999 and RFC 7230– RFC 7235 published in June 2014, HTTP/1.1 was extremely stable until the release of HTTP/2.0 in 2014 — Nearly 18 years later. Before continuing to the next section about HTTP/2.0, let us revisit what journey HTTP/1.1 has been through. - Source: dev.to / almost 3 years ago

• Poll: Are client web requests sent to upstream servers or downstream servers?

  On the one hand, it just seems natural that "upstream" refers to the inbound request being sent from one system to another. It takes effort (connection pooling, throttling, retries, etc.) to make a request to an (upstream) dependency, just as it takes effort to swim upstream. The response is (usually) easy... Just return it... hence, "downstream". Recall the usual meaning of "upload" and "download". Upstream seems... - Source: Hacker News / over 4 years ago

• How to cache TCP, SSL handshake on ALB?

  To me it sounds like you’ve not solved this as the config you’ve mentioned is about preventing “illegal” (none RFC7230 ) requests, it isn’t really related to the problem you posted. Source: over 4 years ago