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

help-circle


  • Ah I see, that’s unfortunate then. For what its worth, I still think the bot is a great idea for discoverability and bridging the two services together! I hadn’t seen it before since I usually have bot users muted and happened to see this comment chain while logged out.

    I’ve given it a follow from my Mastodon account since I do tend to miss quite a few cool Lemmy posts it seems, and I think it’ll help me find some communities in general that I’ll want to subscribe to from over here.








  • Yes, although like someone else mentioned - I don’t, and ever wouldn’t try to host it at home, but on a server at a data center. The network is operated by a person I know and trust.

    No IP reputation issues that I’ve run into, but even going in I knew that its very rare I send emails so it probably wasn’t going to be an issue either way. I’ve only had it running for about two years now, but in that time frame I’ve sent one email out where I “started the conversation”, and three emails where I was replying back to someone who already had my email in their address book.






  • I do not think that self-hosting necessarily means that you have to host it at home. As others have pointed out, its more about hosting it on hardware you control.

    I do think there is certainly a trust factor involved if you host stuff on hardware that you don’t own, but at the end of the day only you can deem whom you can trust. For example, I rent a couple of dedicated servers from a provider, but I also have a pretty good personal connection with the owner of that provider - so I have no concerns about the safety of my data. In general, I tend to just be pretty conscientious about what data is going to any server, and anything that I wouldn’t want falling into the wrong hands doesn’t leave my house unless I can guarantee its safety (with the likes of encryption and such).

    I do also keep in mind that with the various providers out there, reputation is paramount to them (or at least, the good ones) so it is generally in their best interest to say, let someone walk into their datacenter and just start ripping the drives from your systems.


  • Personally, its a combination of the following reasons:

    • I’m not held to another server, and self-hosting my own makes sure that whomever hosting the server doesn’t just close the doors one day and decide they’re no longer going to do so

    • I find it fun to setup my own services, like Matrix, Lemmy, Mastodon, etc

    • I control what servers are blocked / defederated from, from my knowledge though defederating on Matrix doesn’t happen nearly as often as it does for ActivityPub based platforms however.

    • I created Matrix accounts for some of my family members to communicate with, and if they lose the password I know that I can reset it for them rather than hoping they setup the account recovery info correctly.



  • The Bitwarden clients all keep a cached copy of your password database, which can be viewed even if your server goes offline (you just can’t make edits) - you can even export it when that is the case.

    However, if you log out of Bitwarden, it erases the local cache off that device, which will require your server to be online in order to retrieve again (or export it from a different device that is still signed in).



  • I have a follow-up question if you don’t mind! You mentioned this:

    To combat this, I’ve updated LPP with some additional configuration options to do both direct “purge” of leftover media in Pict-rs not tied to “kept” posts and a forced “remove” of files on the file system that are not properly purged (if using local storage).

    Is there a specific setting to use this? For example, if I don’t want to setup any aging post purging at the moment, but just want to do as you mentioned (removing any media that isn’t tied to a post), which setting(s) would I use to accomplish this?

    It looks like this might be done by just passing in a PICTRS_FOLDER directory, and then setting a high PURGE_OLDER_THAN_DAYS variable would do this if I understand right?