Hmm just tried it & it doesn’t load either. The last official onion link I found published on https://proxygalaxy.me (via archive.org) was in May 2024 at http://galaxy3yrfbwlwo72q3v2wlyjinqr2vejgpkxb22ll5pcpuaxlnqjiid.onion but it doesn’t seem to load for me in Tor Browser.
I tried creating my own torrent and was able to dl it on another device, but on her machine it stayed at 0% and wouldn’t let me connect to seed
At least one of the torrent clients needs to be fully connectable (port forwarded) for torrents to transfer data. You need to test that e.g. test your torrent client’s incoming connection port with a port test website like https://www.canyouseeme.org, https://www.yougetsignal.com/tools/open-ports, etc. & make sure those port test websites can successfully test connect to your torrent client’s incoming connection port. If the test fails then you need to look at opening the port via your OS firewall and/or router firewall.
Is FTP a good option? I set up a proxmox server last night but I don’t really know what I’m doing yet
Probably best to avoid FTP if you don’t know what you’re doing, it’s not all that secure… you’d want to at least configure SFTP or FTPS which is just going to be more complicated vs fixing your torrent issues. And technically you still need to make those connectable (port forwarded) too, just like your torrent client.
All that aside it’s probably easier to use Syncthing if you can’t get the torrent working.
You could also try one of those file transfer websites that use WebRTC to transfer data peer to peer e.g. https://file.pizza or similar. Not sure how well they work for huge amounts of data but their github page mentions that Firefox is better for that, apparently Chrome starts to choke with data 500+ MB.
Wow, time sure flies by! A whole bunch of people here (including me) were in that wave exiting Reddit at the time, we’re all hitting that 1 year mark around this time.
The instance has been going great thanks to all the admins & mods keeping things running. Looking forward to more years here :)
Nowadays I buy digital music (mostly via Bandcamp but there’s also HDTracks, Qobuz, etc.) & play the music that way. Can also stream my own music library if I want via Jellyfin or other applications.
re: physical CDs, yes I’ve got a ton of those too from before you could buy digital music but have already ripped them. Haven’t had a need to touch the physical discs in years but still keep them in CD binders just in case.
Also not sure if it matters but for me I’m always living in small apartments/rooms so I absolutely avoid collecting physical items, there’s just no space for that.
You might be confusing public IP addresses with ports? If your torrent client doesn’t have a public IP address that just means it’s offline / no internet. Maybe your internet is down or the VPN is disconnected. You’re won’t torrent anything at all in that state.
One side of the connection needs a
public addressopen port, not both. When both parties don’t have apublicly addressable IPopen port,the status is firewalled. I guessthey can “see” each other but are unable to exchange any torrent data.
For what it’s worth in the situation where both peers don’t have open ports (meaning they are both firewalled) they end up having to wait for another peer to join that torrent swarm that happens to have a open port, that’s the only way any data will exchange in that swarm. Until that happens those two peers will sit there waiting and not exchanging data.
So your saying it should have never worked even if I was not using docker?
Correct.
Also it’s now working… I have no idea
Yeah that’s weird, I don’t know if you accidentally found a way to hack Windscribe into temporarily giving you a port forward on their free plan. But otherwise you do need to be a paid member on their Pro account for that feature.
Or it’s just going to randomly stop working again.
Is there a way to actually test your port forward within Docker? I’m not familiar enough with that configuration to suggest anything but maybe someone else knows about that. Usually without Docker I’d just start up the torrent client & then use a web browser with any port test website (https://www.canyouseeme.org, https://www.yougetsignal.com/tools/open-ports, etc.). But for Docker not too sure how to go about that.
Mullvad does not have port forwarding so it would be normal for your torrent client to be firewalled.
I’m not too sure why you & OP sometimes see it as temporarily connectable when changing/randomizing the incoming port when the VPN service never provided you an open port forward.
I have never done any kind of manual port forwarding my current VPN provider does not do that at the price I have it for right now.
If the VPN provider does not support port forwarding then it is normal and expected to always be firewalled. Toggling random ports doesn’t change that fact.
Not sure why you would sometimes see your status as fully connectable, guessing either it’s a Windscribe misconfiguration when you initially connect (?) or qBittorrent gets confused during the intitial connect. Or there’s some other misconfiguration.
You might want to see if other people using that VPN provider have more insight, maybe they are doing something strange with the ports when you initially connect & eventually close them on you.
That’s pretty cool, thanks for sharing! Been a while since I tried it out but last I looked Tribler’s own automation features were quite lacking so something like this helps a lot.
I was not able to download anything with more than 1 hops in between - ie it does hide your real IP address, but only uses one relay in between.
Hmm I don’t think there’s any relays at all in that configuration, unless you’re counting the exit node itself?
https://github.com/Tribler/tribler/issues/3067#issuecomment-325367047
One thing to keep in mind is that to download torrents from outside Tribler’s own network you would need to download through an exit node… not sure on the exact stats but last I tested exit nodes were only like 5-10% of the Tribler user base. For a while I tried volunteering my own VPN connection as an exit node for Tribler just to see how it went but the Tribler client kept locking up/crashing after a few days so the experiment did not go well… hopefully works better nowadays.
But, regardless, blocking any registrars that size the way you’re describing would break way more businesses and hurt the recipient provider’s own reputation.
Yeah I thought that too but when speaking with the email admin that was blocking Namecheap while figuring this out they had already decided it wasn’t worth trying to allow the 1% of valid emails vs the 99% spam emails they felt they received via Namecheap domains.
This honestly starting to sound more and more like a smear campaign
Smear against whom? I’m a Namecheap customer, just relaying my own experiences using them. Besides that quirk I like them fine as a registrar… I know it sounds dumb but I even renewed my domains there even after those email issues.
It’s fine, you don’t need to believe me as I said it’s just my own experience using Namecheap domains for emails. But you could just google around, you’ll see plenty of people discussing Namecheap & looking for solutions to block them (or solutions to successfully send emails with hem)… it’s not something I randomly made up if that’s what you’re implying.
e.g.
https://community.spiceworks.com/t/blocking-emails-based-on-registrar/816565
https://tacit.livejournal.com/608386.html
https://shkspr.mobi/blog/2021/05/why-do-scammers-love-namecheap/
https://www.reddit.com/r/NameCheap/comments/13t6fvm/namecheaps_private_email_is_blacklisted_by/
https://www.reddit.com/r/NameCheap/comments/wlb6vp/namecheap_making_it_too_easy_to_register_domains/
https://www.reddit.com/r/NameCheap/comments/tz4mkb/my_emails_are_always_going_in_the_spam_folder_of/
https://www.reddit.com/r/NameCheap/comments/ye358x/i_am_getting_a_ton_of_spam_scams_from_namecheap/
etc.
If you’re using Google Workspace, Google will give you the appropriate DMARC, DKIM and SPF records to add to your DNS. The NS themselves should resolve the records and provide the recipient server with the values you’ve entered, thereby ensuring delivery.
Sure. But why would that matter when you’re dealing with hostile 3rd party email providers that intentionally want to blackhole all email domains at Namecheap? But yes, just to clarify I do configure DMARC/DKIM/SPF and that works great for most cases.
I’m just describing what worked for me though in truth I don’t know exactly how these hostile email providers actually determine the domain is hosted at Namecheap. My hunch is that they are using a lookup & finding the nameserver for the domain & have already blacklisted Namecheap’s default free nameserver IP addresses. For whatever reason those same hostile email providers don’t seem to be blacklisting Namecheap’s paid nameserver but I think that sort of makes sense…
The larger issue is that Namecheap is known for cheap domains that scammers/spammers tend to buy in bulk & then use to spam with. Those same scammers/spammers aren’t trying to spend extra money so they only ever use the default free Namecheap nameservers.
If you use Namecheap for email domain(s) you may want to consider also splurging for their PremiumDNS to keep your domain(s) off spam blocks at other email providers.
I help maintain some emails at Gmail/Google Workspace but the domains themselves are at Namecheap. For a while there were complaints that some emails never landed in other people’s inboxes… this led me to talk about the issue with one of the email provider recipients based in the UK & apparently they were null routing anything coming from Namecheap since they felt a lot of spam came from them. But after some experimenting I figured out their system (& probably others) were figuring out they were Namecheap domains via the default FreeDNS they use. On a hunch I switched those domains over to PremiumDNS and after that all our emails were landing in other inboxes correctly. I guess maybe it makes sense, a typical spammer buying a cheap domain at Namecheap isn’t going to splurge for the higher end DNS service for it.
I’m not saying all email providers treat Namecheap domains as spam but just be warned there definitely ones out there that do.
Nice, I was pretty sure my Pixel 7 already had hardware AV1 decoding and this app seems to confirm it.
It’s not, whatever you’re looking at is just some site re-using the name.
Futurama also did their own version https://futurama.fandom.com/wiki/V-Chip
Tried it, Too heavy for my usecase
That’s fair, Kodi is way more feature rich. I love it personally but realistically don’t need to use everything Kodi is capable of.
Also I cannot use MPV to watch my videos.
Been happy with Kodi’s internal player but they do have configurations for external players including MPV https://kodi.wiki/view/External_players
BTW you should also look at Jellyfin, slightly different use case but it too is designed to manage local media including TV/Movies.
And since you mentioned MPV that also exists with Jellyfin https://github.com/jellyfin/jellyfin-mpv-shim
Kodi (https://kodi.tv) does the same thing & more. People think of it as a sort of streamer but its original/main purpose is to manage local media downloads including movie/tv series.
If you make a community don’t do it on lemmy.world, the admins at this instance have taken a hard stance against piracy related communities.
I don’t have an 8 but I’ll say the 7 is probably the best phone I’ve owned so far. That aside I was also happy with the 3 and 4.
FYI all the official domains and .onion link are on their proxygalaxy page
https://proxygalaxy.me
For what it’s worth .to does not forward me to .mx, each of those domains seem to work fine on their own. Not sure what exactly is happening with your browser, maybe try clearing the cache / doing a hard reload.