thelittleblackbird

@thelittleblackbird@lemmy.world

• ⁨Comment⁩ on ⁨[Discussion] What would it take to selfhost some of the backend that Tesla's connect to?⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  Because the modification of that computer is order of magnitudes more difficult than a mechanical modification of a moving part. The humanity / regular human is able to understand much better the interactions of the mechanical parts that usually are always local and well defined.

  This does not exist in the Sw, FW and digital hw, the interactions are not local and are millions timesmore complex to understand and properly modify.

  It would be an utterly irresponsability to modify (blindly) the Sw of an xray machine that could make it unsafe and ultimately it could kill humans, and it is the same concept with the car. It is irresponsable to make a modification that can make the system unsafe.

  For the rest? Regulations, free software foundation and good selfhosting Cheers

• ⁨Comment⁩ on ⁨[Discussion] What would it take to selfhost some of the backend that Tesla's connect to?⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  Then don’t buy tesla, or force legislation about introducing such feature.

  But make yourself a favor and don’t play Russian roulette with something that you can not understandbecause there are not data available.

  And for final tip, if you really cares about that then enforce the fsf (fsf.org)

• ⁨Comment⁩ on ⁨[Discussion] What would it take to selfhost some of the backend that Tesla's connect to?⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  It is not comparable, not even by far.

  Assuming your are not a psycho, to safely drive a car is orders of magnitude (in plural) easier than modifying the Sw in a safe and deterministic way.

  It is not only that bad people exists, it is about that making a small mistake can kill you

• ⁨Comment⁩ on ⁨[Discussion] What would it take to selfhost some of the backend that Tesla's connect to?⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

  First, second and third most important point is : Tesla needs to allow the connection to an alternative server.

  The fourth should be access to the api and data that are exchanged.

  You shouldn’t mess with the FW of your own car even for some innocent feature like this one, you don’t know/understand the interactions that may happen between different Sw components and the hw layer, you can not provide a similar of level of testing, including some worst case scenarios, that can make your car unsafe during some problems or unforeseen conditions. And perhaps also, the car could loose its license for driving…

  If tesla allows that, then we can start speaking about it. But last time I check on that was not possible

• ⁨Comment⁩ on ⁨Low resource, Performant WAF⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  You will need to explain a bit further this statement to mild knowledged internet stranger…

  Because the point of waf is exactly about reducing the exposed surface…

• ⁨Comment⁩ on ⁨What's up, selfhosters? - The Sunday thread⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Dealing with a Ds-lite connection for a fiber optic provider in latest opnsense.

  It is excruciating how difficult is to run it reliable

• ⁨Comment⁩ on ⁨Backups: Am I doing this right?⁩ ⁨⁨1⁩ ⁨month⁩ ago⁩:

  Some clarifications :

  The 3 2 1 rule applies only for the data. Not the backup, in my case I have the real/live data, then a daily snapshot in the same volume /pool and a external off-site backup

  For the databases you got misleading information, you can copy the files as they are BUT you need to be sure that the database is not running (you could copy the data and n the middle of a transaction leading to some future problems) AND when you restore it, you need to restore to the exact same database version.

  Using the export functionality you ensure that the data is not corrupted (the database ensure the correctness of the data) and the possibility to restore to another database version.

  My suggestion, use borgbackup or any other backup system with de duplication, stop the docker to ensure no corruptions and save everything. Having a downtime of a minute every day is usually not a deal breaker for home users

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  Well, I don’t know how many online interactions you have. But has you ever imagined that perhaps the feedback you received here is actually the average of the people?

  In these days is quite difficult to calibrate the crowd feeling for the insane amounts of echo chambers, the mass media crating opinion instead of informing and personal biases.

  Usually, everybody of us is quite biased by our own interactions and knowledge of how the world worked around us. But those interactions are mainly defined by your social status, place of birth or simply where we live. By the specific details of people who debate in internet (probably accommodate urban person) it is possible that those ideas lean into a specific direction. But once again, it could be that you are simple realizing you are not with the majority

• ⁨Comment⁩ on ⁨Digital management post-life⁩ ⁨⁨2⁩ ⁨months⁩ ago⁩:

  Of you already have a will the most secure, proof idiot way I’d to add that key + instructions to the will. Get some lawyers on board for that and it will work.

  If you still have concerns about having the full key on a single place, add a topt or second way of identification and distribute it between your heirs.

  Sometime, the old fahion way is the best one by far.

• ⁨Comment⁩ on ⁨[deleted]⁩ ⁨⁨3⁩ ⁨months⁩ ago⁩:

  I would recommend an LDAP sever for user Auth.

  There you can create/authenticate user with a central repo in a machine independent fashion. Also having the possibility to allow /egate specific services from the central database is a big plus.

  It seems difficult at the very beginning but it quickly pays off. Give it a try

• ⁨Comment⁩ on ⁨Migrating from Nextcloud AIO to Owncloud Infinite Scale: Good Idea?⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:

  No idea at all, but I am highly interested in your experience. So it would be great if you could came here back to share it with us

• ⁨Comment⁩ on ⁨Maintaining a level of anonymity.⁩ ⁨⁨5⁩ ⁨months⁩ ago⁩:

  Even if you have a valid point, modern fingerprinting technics usually is done through your data and the connection dependencies of them (which accounts are activated from the sane computer and so on).

  Selfhosting remove some links between your data set like the files you store in drive, the people who appear in your photos, your contact list, to whom you email… Etc etc

  Suddenly all this data is vanishing from the big techs, so, in theory it would be possible to make that association process more difficult

• ⁨Comment⁩ on ⁨Maintaining a level of anonymity.⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Then follow that path, once you are comfortable with the approach you can start hosting more and more services,to the point that you can selfhost your own messenger services or ms teams services.

  Once you are in that situation, you can think in accounts rotation and/or burner identities to address the services you can not pull from the big techs

• ⁨Comment⁩ on ⁨⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  OK, thanks for the feedback. Perhaps I am doing something terrible wrong with it.

  I will recheck the system again.

  Thanks

• ⁨Comment⁩ on ⁨Maintaining a level of anonymity.⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  You need to start reducing your fingerprint on internet.

  The only reliable way to do so is selfhosting your stuff.

  There are a few communities here in lemmy, so check on them

• ⁨Comment⁩ on ⁨⁩ ⁨⁨6⁩ ⁨months⁩ ago⁩:

  Would you mind to elaborate a bit more about your experience witht he sophos?

  I got a reused xgs115 a few months ago and I found the experience not so pleasant. The device lags a lot with the web page interface, the learning curve is steep in my opinion and I have problems to setup some services in a reliable way (they tends to hangs up, but this is perhaps my own problem)

  Do you know by chance if they are able to have the Ds-lite tunnel for an ipv6 to ipv4 working?