fenndev

joined 2 years ago
[–] [email protected] 6 points 4 months ago (3 children)

The interface - GUI and website - is straight out of 2008 and documentation could be better, but otherwise it works just fine for torrenting and browsing. No complaints there.

[–] [email protected] 17 points 4 months ago (8 children)

Happily using AirVPN for port forwarding.

[–] [email protected] 8 points 5 months ago (1 children)

Would love some guides on torrenting over I2P.

[–] [email protected] 1 points 6 months ago (1 children)

I appreciate the offer, but unfortunately, I'm an American.

[–] [email protected] 2 points 7 months ago

I just spun up a FreshRSS container and it is working flawlessly for that purpose so far. I appreciate the suggestions.

[–] [email protected] -3 points 7 months ago (5 children)

It's hosted, but not self-hosted.

[–] [email protected] 1 points 7 months ago

Linkwarden doesn't appear to support RSS, which is a massive bummer.

[–] [email protected] 2 points 7 months ago

I was just looking at this, actually. For a moment I thought it was going to be a bust but then I saw there is a preference option to open the readable form of a page by default. I also love PWAs...

[–] [email protected] 30 points 7 months ago (2 children)

"Life is going to continue on just fine" - unless you're a woman (bans on contraceptives, loss of bodily autonomy), queer (rolling back protections for LGBTQ+ people, penalizing even talking about them), non-Christian, a minority...

[–] [email protected] 15 points 11 months ago

I don't think one currently exists, but it would be an interesting project. There are plenty of trackers for CVEs but in terms of project ethics, acquisitions, etc., there's a space for it.

The two main problems I can see are:

  1. How do you define 'negative'? An open source application being acquired is often a bad thing, but not always. An acquisition by FUTO is more likely to be viewed positively than an acquisition by Microsoft, but either can be interpreted positively or negatively depending on the person.

  2. Community involvement is absolutely critical. If I were running a service like this (for example), I would only really be keeping up on the services I use and care about. I would need others to submit info and then verify it.

[–] [email protected] 1 points 1 year ago (1 children)

Sorry, I should clarify. I'm hoping to possibly have a setup like this:

  1. Browser makes a request to an eepsite
  2. The router sees the request is to a domain ending in .i2p and forwards the request to a service running on the router
  3. That service then performs the necessary encryption and establishes connection with the I2P network.

I'd imagine it's a similar process for other protocols and networks. No idea if this is possible or desirable.

[–] [email protected] 4 points 1 year ago (5 children)

Any issues lately with your network? When DNS is down or having issues, Firefox and forks take forever to start up.

 

cross-posted from: https://leminal.space/post/4761745

Shortly before the recent removal of Yuzu and Citra from Github, attempts were made to back up and archive both Github repos; it's my understanding that these backups, forks, etc. are fairly incomplete, either lacking full Git history or lacking Pull Requests, issues, discussions, etc.

I'm wondering if folks here have information on how to perform thorough backups of public, hosted git repos (e.g. Github, Gitlab, Codeberg, etc.). I'd also like to automate this process if I can.

git clone --mirror is something I've looked into for a baseline, with backup-github-repo looking like a decent place to start for what isn't covered by git clone.

The issues I can foresee:

  • Each platform builds its own tooling atop Git, like Issues and Pull Requests from Github
  • Automating this process might be tricky
  • Not having direct access/contributor permissions for the Git repos might complicate things, not sure

I'd appreciate any help you could provide.

14
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

Shortly before the recent removal of Yuzu and Citra from Github, attempts were made to back up and archive both Github repos; it's my understanding that these backups, forks, etc. are fairly incomplete, either lacking full Git history or lacking Pull Requests, issues, discussions, etc.

I'm wondering if folks here have information on how to perform thorough backups of public, hosted git repos (e.g. Github, Gitlab, Codeberg, etc.). I'd also like to automate this process if I can.

git clone --mirror is something I've looked into for a baseline, with backup-github-repo looking like a decent place to start for what isn't covered by git clone.

The issues I can foresee:

  • Each platform builds its own tooling atop Git, like Issues and Pull Requests from Github
  • Automating this process might be tricky
  • Not having direct access/contributor permissions for the Git repos might complicate things, not sure

I'd appreciate any help you could provide.

view more: ‹ prev next ›