A wall hack is any technique allowing the player to see opponents through walls. Googling for screenshots or videos should give you a good idea of how it looks.
How is that setting supposed to carry over if I don't even have a Google account on my phone?
And even if I disregard that for a moment, what's up with the author being a mouthpiece for Google?
> Google's latest concession makes the sideloading controversy a big nothingburger
> Opting out is going to be even less of a problem than we thought
> This afternoon, Google’s Matthew Forsythe shares some answers to questions he’s gotten about the minutiae of how this process all works — and he’s got some very, *very* good news for us.
(emphasis theirs)
> Doing that once with every new phone already sounded perfectly manageable. But now Google clarifies that even that won’t be necessary, with the opt-out able to be transferred as we upgrade phones. That is maybe just the best news we could have gotten here, and hopefully it’s enough to calm everyone down about the sideloading-sky falling.
I think such "ludicrous sets of patches" are very common in many jurisdictions. (At least in Germany they are.) I agree, though, git patches would be a lot nicer.
Looking at the commit dates (which seem to be derived from the original publication dates) the history seems quite sparse/incomplete(?) I mean, there have only been 26 commits since 2000.
It's related to commits actually having a parent-child structure (forming a graph) and timestamps (commit/author) being metadata. So commits 1->2->3->4 could be modified to have timestamps 1->3->2->4. I know GitHub prefers sorting with author over commit date, but don't know how topology is handled.
> It's related to commits actually having a parent-child structure (forming a graph) and timestamps (commit/author) being metadata.
Yeah, I think everyone is aware. It's just that the last couple dozen commits, to me, looked like commits had been created in chronological order, so that topological order == chronological order.
> I know GitHub prefers sorting with author over commit date, but don't know how topology is handled.
I have 30 days of food in my house and I have maintained that since probably 2021. It doesn't mean I will run out in 30 days, since I can still buy food although at higher prices lately. I personally never let it dip below 20 probably.
Oh I'm sorry, that was actually my mistake, I should have been much more specific, and I will update the comment if I still can. My intention was to emphasize that Taiwan may have to start limiting electricity to its industrial sector based on its current runway. Per the article you listed:
> Yeh Tsung-kuang, a professor in the Department of Engineering and System Science at National Tsing Hua University, said Taiwan's maximum LNG inventory is only 11 days but that does not mean the island will run out of fuel or face outages within that time period
> Yeh Tsung-kuang, a professor in the Department of Engineering and System Science at National Tsing Hua University, said Taiwan's maximum LNG inventory is only 11 days but that does not mean the island will run out of fuel or face outages within that time period
So he's saying they've got an 11 day supply and that they won't face any shortages during that 11 days... but what about after 11 days? I guess I'm not sure how that's different, how it's a hoax?
11 days of supply in the system. If they can afford it they can add to that with new shipments. It is not like Taiwan is blockaded. Just that global supply from single region is limited.
This might be lot bigger issue if China managed blockaded Taiwan during an invasion. Or destroy port facilities sufficiently.
Not blockaded, sure, but how long would it take for these new shipments to arrive? If these are shipments they hope can come through the SoH even if they got through tomorrow it would take ~10 days to arrive in Taiwan. They can also get LNG from Australia, but a typhoon has shut down some of Australia's LNG terminals today.
> I'm fairly sure the German tax authority will claim that you have a local German branch office since you live and work there. That might be OK tax wise?
If you work from home, your office at home usually does not qualify as a company office unless you make it one. In particular, that alone would not force you to pay Gewerbesteuer to the city, which is the tax specifically addressing local presence.
However, you're touching upon a very important point: If you live in Germany and your Estonian company pays you a salary (as opposed to dividends), you will be a proper employee and your company will also have to pay social security for you, and this might complicate matters significantly. In fact, this will likely (in the German tax authorities' eyes) establish that your Estonian company partially operates in Germany (which is a much broader thing than having an actual physical branch office). This then brings you back to square 1 – your company having to file taxes in Germany, too. Someone below linked https://eidel.io/posts/estonias-e-residency-is-awesome-and-s... which seems to confirm this.
> German tax authorities will see that as an illegal dividend payment from your company.
Could you elaborate? How is this illegal if you declare taxes?
Not illegal, but the incorrect amount of taxes will be paid. Also, the financial statements will not be entirely correct. So, not illegal in the sense of "not allowed", but in the sense of "legal requirements and obligations not fulfilled".
> Could you elaborate? How is this illegal if you declare taxes?
As someone else mentioned, the taxes are different.
Namely: Salary is taxed lower than dividends. So the German tax authorities checks very carefully that you don't pay salary instead of dividends. If they determine that you paid out dividends as a salary, then you'll be charged with tax fraud.
Now you might say, "I don't care about paying a bit extra in taxes, so I'll pay it as dividends as they wish"
The problem is that you can only pay dividends the year after you earn the money.
If you can set a fixed salary which you can keep paying throughout, and then wait for the dividend payments next year, that's fine.
But what if you want to pay yourself wildly different amounts of money each month based on how much you managed to charge your customers? You can't just keep adjusting your salary up and down every month with a corporation.
So here's where something like a sole proprietorship may be simpler from that aspect?
Another thing you want to look at is "how easy will it be to dissolve the operations?" With a GmbH/UG it takes several years and potentially many thousands of euros in accounting fees. Not sure about the foreign corps. I think German sole proprietorships are simpler in either case?
Also, Germany has a "Moving away tax" where you get taxed on the fictious value of your company if you move away from Germany. This fictious value can be quite a lot more than what you'd actually get if selling the company.
Yet another thing: Depending on your setup, you may be covered by different rules regarding health insurance and pensions. If you don't make a lot of money in the beginning, it may be best to stay in the government insurance. But if you think you'll make a lot of money, it can be better to be able to do private insurance instead? There are rules on how you can move back and forth between government/private, so this is another area to consider carefully.
This is my understanding as a layman, please check this with a competent local tax expert before acting on any advice here.
That very much depends on your tax bracket but at high income levels salaries are usually taxed quite a bit higher (42% vs. ~27%). 42% being the highest tax bracket of course; the first ~69k€ of your salary are taxed at a lower rate.
> If they determine that you paid out dividends as a salary, then you'll be charged with tax fraud.
This might be the case if the company were in Germany, and then it might not even be the taxman that'd complain but social security since you don't pay social security fees on capital gains. However, I doubt German authorities can do much about an Estonian entity paying dividends.
> You can't just keep adjusting your salary up and down every month with a corporation.
Yes, you can. Many companies do that – it's called fixed vs. variable salary (bonuses).
> The problem is that you can only pay dividends the year after you earn the money.
You're right in general (and I assume also in the case of an Estonian entity). Though at least in Germany – surprisingly – this is not correct, look up "Gewinnvorabausschüttung".
Either way, this is not a huge obstacle if you're pursuing this long-term: You only have to make it through the first year without any income. Afterwards you can live off of last year's dividends.
I've been a big fan of Ente and their work and am a paying customer but, man, this comment in a long-standing GitHub feature request is ringing truer every day:
> Ente is becoming like Proton: too many products and a lack of focus, leading to lower quality and not delivering what customers want
Hi Vishnu, thanks for engaging here – it is highly appreciated! Let me respond to a couple of your statements from the interview:
> I think it's important to offer a complete package
I agree. But doesn't that start with making one product (Ente Photos) good enough for people to actually be able to migrate? If Ente Photo really is your "home ground", as you say, shouldn't you prioritize accordingly? Specifically, in your response[0] to the GitHub issue I linked you say
> to pull it off with the finesse we would like, it will take us more than a quarter. […] I will mark this feature as unplanned until we have more engineering bandwidth.
But it seems you really do have the engineering bandwidth! You've just been prioritizing other products besides Ente Photos. I do understand that folder nesting in particular is a non-trivial change and if you look at the discussion on GitHub, I've actually been defending you rather heavily. But it's becoming increasingly difficult to do so – quite frankly, I am starting to doubt your product management is entirely on the right track if in 3 years you can't dedicate 3 months to the feature request with the highest number of votes by far. More generally, I am losing trust that any of your products will see enough polishing any time soon. (So I will definitely not put time into migrating anything else if I can't even migrate my photos yet.) And it seems I'm not the only one thinking that – your reputation among enthusiasts is starting to take a hit.
> There is no way Ente is going to let anyone else build a better photo app.
For a bootstrapped, engineering-driven company like Ente, product offers the best leverage for growth. We are not P0-ing nested folders right now because we believe there are areas within the photos app investing into which will provide higher revenue returns, that we can re-invest into increasing our engineering bandwidth.
Now I understand the disappointment around us not prioritizing a feature that is blocking you from even using the product. It is a loss for all parties, but it is important for us to plan long-term. And while we're not prioritizing this specific feature, I don't think it is fair to say that we do not invest time into polish. We do care about our craft[0][1][2].
Thanks again for the YouTube link – I hadn't had time to watch the entire video yet, so I wasn't aware your product lead addressed nested folders specifically.
So how would nested tags interact with albums? Will I also be able to share (or contribute to) tags like I can share (or contribute to) albums? Actually, aren't albums already "tag-like" in the sense that photos can be assigned to multiple albums at the same time?
> And while we're not prioritizing this specific feature, I don't think it is fair to say that we do not invest time into polish. We do care about our craft[0][1][2].
You will be able to create "smart albums" with nested tags, and share (and contribute) to them.
Albums are tag-like in the sense you described it, but might be an overkill[0] for the outcome we wish to achieve - organization, sharing, and ability to respect original folder structure when a user exports their data.
So if I understand you correctly, users will be able to share tags from a given album but you don't want to make tags separate collections (inside the existing album collection). But what is the alternative here if you want to secure access to the tags cryptographically (which I hope you do)?
A few thoughts:
1. Let's say files inside tags use the collection key of the parent album. Access to a tag (e.g. if I shared it with someone) therefore requires access to the collection key, thereby potentially exposing the entire album. (E.g. if a government agency got hold of a public link I've shared to a single tag inside a bigger album.) Bad.
2. Alternatively, let's say all file keys of files belonging to a tag will also be encrypted with an additional tag key (separately from the encryption with the collection key). This is certainly doable and I assume you already do a similar thing for photos belonging to multiple albums/collections. However, with nested tags this might get annoying fast if a file key needs to be encrypted not only with the tag key of the tag "foo/bar/baz" but also with the tag keys of "foo/bar" and "foo". If you wanted to avoid this, you'd encrypt the tag key of "foo/bar/baz" with the tag key of "foo/bar" and the latter with the tag key of "foo". But then isn't this more or less exactly what you would do if you implemented nested collections?
On top of this, you will need to store an encrypted map of tag -> tagged files somewhere both for performance reasons, for privacy reasons (if you stored the tags inside the files, you'd risk exposing them to people the tags weren't shared with), and to manage write access (contributions) to a tag.
All this, I assume, is also what you do for collections. So then, all in all, how different from collections would tags really be?
--
Irrespective of the encryption questions, wouldn't the addition of tags complicate your domain model quite a bit? You'd likely also need new API endpoints, and separate UIs for viewing photos belonging to a tag (as opposed to an album), sharing a tag, editing/renaming tags, …
The way I've thought about this, we will not have "files inside tags", but we will have tags (foo, bar, baz) attached to a file as additional encrypted metadata.
We have existing client-side infrastructure[0] that can create auto-updating albums based on metadata, and this can be extended to enable sharing workflows.
Manual refresh(). This is something Crank does, and other frameworks like the new Remix one is picking it up as well. Being explicit has its advantages.
Looks like it is, though? https://news.ycombinator.com/item?id=47558097
reply