dwightgunning

Perhaps a happy accident.

That's not a tax, that's the expense ratio, which is basically describing fees captured by the fund manager. Funds accessible to Dutch investors involve similar ERs. It's not an alternative.

Proud to have helped work on this. Happy to field any questions.

Is there a robust Syncthing app for iOS? Last time I checked there was only an affiliate project and their story wasn't convincing.

I had a hunch this was the bridge featured in The Wire s2e1, "Ebb Tide". Classic McNulty; a great season opener.

https://en.wikipedia.org/wiki/Ebb_Tide_(The_Wire)

DALI (IMO: 9697428) is a Container Ship and is sailing under the flag of Singapore. Her length overall (LOA) is 299.92 meters and her width is 48.2 meters [1].

Based on the track, it appears the ship changed course slightly and slowed as it approached the bridge [2].

[1] https://www.marinetraffic.com/en/ais/details/ships/shipid:28...

[2] https://www.marinetraffic.com/en/ais/home/shipid:2810451/zoo...

The Sound Map of Amsterdam shows the (calculated) noise load for the most important traffic sources in the city.

Gemeente Amsterdam publish a handy noise map (along with some other great public data). Check it out: https://maps.amsterdam.nl/geluid/

They don’t have access to the ssh private key. They have access to the encrypted password file (and presumably not the password used to encrypt it).

The attack works when the user doesn’t realize they’re sending their SHH private key through the password form of malicious-site.com.

Something like accidentally putting your Google password into the Dropbox login form. Dropbox have now seen your Google password.

Seems logical to move smaller sums more frequently.

So many ads I can’t even get to the obituary.

For a long while I've trusted and used various KeePass ports/forks on my phone and laptops and stored the password file in cloud storage.

With the recent LastPass exposure, the supply-chain attack on PyTorch, needing to be vigilent and avoid granting apps access to my cloud drive, I've actually just been reviewing my setup and workflow.

Here's what I'm planning to change...

Phone: Switching from MiniKeePass to KeePassium. I've found it's not too difficult to build KeePassium from source and install without needing an Apple Developer subscription. This means I can properly audit the code and control/verify all updates.

Laptops: Start building KeePassXC from source. In the short term, I'll be more diligent in obtaining updated versions from trusted sources and using PGP to verify the package.

File sync: Start storing the password file on a self-hosted file server. Having recently setup Tailscale on all my devices, it's now convenient to manage Samba and remove cloud storage from the system. In case the SMB share is inaccessible, I'll fallback to the backups kept by KeePassium and use cron+rsync to maintain an secondary copy on my laptop.

Backups: I'm planning to periodically backup to a hardware keypad encrypted USB drive. In comparison to a regular USB / external drive, the hardware encryption makes it harder for somebody to quickly make a copy of the password file and take it away to be brute-forced.

Would welcome any pointers on things I may not be considering or suggestions for improvement!

As explained in another thread, nothing went wrong with the tooling and namespacing. The PyTorch devs misused a feature intended for a different use-case.

I took a look and the vulnerability that was exploited is warned about and described in the documentation.

> Warning > Using this option to search for packages which are not in the main repository (such as private packages) is unsafe, per a security vulnerability called dependency confusion: an attacker can claim the package on the public repository in a way that will ensure it gets chosen over the private package.

https://pip.pypa.io/en/stable/cli/pip_install/#examples

> This coffee is still good. It was roasted in June and July 2022 with a one year best buy date.

Still good but hardly fresh for a specialty.

Anyway. There’s a 6x number in here that somebody (or somebodies) completely missed…

Seems like what they thought was a fair-to-good deal was actually a such a terrible deal that, given their incorrect definition of a unit, the numbers in their model lined up.

That might be something the consultant could have spotted, since they’d seen the numbers around previous deals. I’m not sure it’s their duty/obligation to.

That’s a great example and suggestion. Thank you!

Can you elaborate with some examples of workflows that it is incapable of?

So far I’ve not found any limitations or issues using Ubuntu runners on my OSX dev machine. A couple examples from my workflows: - building docker images - provisioning VMs with the Digital Ocean cli / http api - hardening VMs with ansible - creating/managing k3s clusters with k3sup - deploying apps with helm

I like your suggested approach of using tmate to access the worker mid-way through a run. This should make it faster to develop/debug the steps that make up the workflow. Though this doesn’t address the cycle time of push-to-GitHub/queue-workflow/watch-for-result.

I’m actually going to try combining the two techniques - use tmate to develop inside a local act runner.

+1. So glad I found this group.

But it’s just a data point… gotta do your research.

This is right. Black emerging from beta was discussed on the Django mailing list in the last week or so, and triggered the work.

I’d only installed it ~24hrs ago onto a new MBP. So my fix was `brew uninstall` and then reinstall. That worked.

This is still in place for PPOR. Does not apply for investment properties AFAIK.

Even if it were feasible... it seems like it would just defer the problem to a later time or place the burden on other intergalactic citizens.

Thanks both for taking the time to acknowledge and explain the subtlety. Helps somebody like me who’s casually following along to better understand both scenarios.

> While $599 may seem like a steep price to pay for a Zoom-calling device when you can already Zoom from a phone or computer, the idea seems to be that it’s an easy way for newly remote employees to jump right into Zoom without having to deal with installing the software or setting up any complex equipment.

Hang on a minute... their partner manufactured hardware product is easier to setup than their own software?

How hard is it to install on the major OSes?

Seems like a strange angle.

I submitted a DS-160 application for a B1/B2 this past Friday and which asks for all social media handles in use over the past 5 years. The implication is that this a request for accounts you've used, not those that are still "active".

Thanks for a great anecdote. While I feel I'm pretty good at recognising that "done is better than perfect", I'm not as good at realising when "near enough is good enough". For some reason approximations usually don't sit well with me... something I can work on for sure.

My first reaction was ... “so Microsoft”. I’m with you on the positive path Microsoft have been on with OSS but also recall the not-so-recent history. It’ll be interesting to see how this plays out.

Mini owner here, often think about this too. There’s an MGB that gets around my area which has been converted to electric.

It’ll be interesting to see if converting classics will become more common. Here’s hoping.

I once shook hands with a new acquaintance who, unbeknownst to me, had just been snacking on a few peanuts at a bar: https://photos.app.goo.gl/7tvD65JmV45M4Mpw5