N26 is not a bank though. It would be interesting to see the difference with a real bank.
the former head owner is gone
Do you think we should be able to do the same with people who suffer with Alzheimer's disease or senility since they are technically "gone"? What about Down syndrome since their wishes are not on the same level as ours? Where do you draw the line?
Amazing that this scam hasn’t been banned yet by Google.
Your request has been blocked due to a network policy. Try logging in or creating an account here to get back to browsing.
I love it already.
You do attack them if you install uBlock Origin. It’s easy.
Why is the USA the only country to have those problems, AND complain about getting free stuff?
I use https://addons.mozilla.org/en-GB/firefox/addon/cookie-autodelete/ and only whitelist web sites that I have accounts on.
Everything is fake crap. They pretend they care or don’t share but they can’t prove it. I assume that they are lying.
https://en.wikipedia.org/wiki/Computer_architecture
Your question is confusing. What do you really want to know?
FLAC is supposed to be way smaller: https://hbfs.wordpress.com/2012/02/07/looking-at-flac-compression-ratios/
I use Opus at 192 kbps. It's overkill but it should be almost perfect and has the size of an MP4.
There are 5 or 6 ridiculous questions about AI at the beginning. They should have made it less obvious.
Handlers, module managers, any shitty thing that handle stuff or load stuff, but has a name more obscure than a philosophical book. God I hate this.
cross-posted from: https://sh.itjust.works/post/19440902
> I want to document my debugging sessions in a text file but I don't know if anyone did this before.
>
> I came up with this kind of "language" that is a mix between Markdown and C++, but I still wonder if something equivalent exists already.
>
> > // When you click on the button > # [click button] > - A::f() > // - ... other method calls, don't document if you don't need to > > # A::f() > // "..." for "parameters" where you don't need the details > - Stuff::g(...) > - Stuff::h(...) > > // <Class> is a fake template thing to show the possible types of an object > # <SubStuffA | SubStuffB> Stuff::g(...) > - Stuff::g() {} // empty but I use v/=> for virtual call > v/=> SubStuffA::g() > v/=> SubStuffB::g() > > # SubStuffA::g() > > # SubStuffB::g() > > # Stuff::h(...) >
>
> I document methods in the order of appearance in the code.
>
> If you have any good idea about a reliable way to document a list of function calls, I'm interested!
I want to document my debugging sessions in a text file but I don't know if anyone did this before.
I came up with this kind of "language" that is a mix between Markdown and C++, but I still wonder if something equivalent exists already.
``` // When you click on the button
[click button]
- A::f() // - ... other method calls, don't document if you don't need to
A::f()
// "..." for "parameters" where you don't need the details
- Stuff::g(...)
- Stuff::h(...)
// <Class> is a fake template thing to show the possible types of an object
<SubStuffA | SubStuffB> Stuff::g(...)
- Stuff::g() {} // empty but I use v/=> for virtual call v/=> SubStuffA::g() v/=> SubStuffB::g()
SubStuffA::g()
SubStuffB::g()
Stuff::h(...)
```
I document methods in the order of appearance in the code.
If you have any good idea about a reliable way to document a list of function calls, I'm interested!