• 0 Posts
  • 27 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • The “downvote to disagree” thing isn’t just an attitude problem, it’s a structural issue. No amount of asking people nicely to obey site etiquette will change the fact that the downvote button is a disagree button. If you don’t want a hive mind, you necessarily need to be able to allow for things you don’t like to be amplified.

    Actually, with enough interactions from different people (ie: enough data points) Lemmy should be able to determine if a comment brings value to the conversation (either positive or negative) or if it’s noise that should be ignored (and prioritized lower).

    If you have 4 comments:

    1. Has 100 upvotes (in total)
    2. Another has 100 downvote (in total)
    3. Another has 50 upvotes and 50 downvote (100 in total with a 0 sum)
    4. The last was a new comment with 0 votes.

    It’s obvious that 1 and 3 are providing more to the conversation than 2. 4 is a bit of an outlier, but probably provides more value than 2.

    Regarding 3: The challenge would be that there’s a low chance that there will be such a wide margin of upvotes/downvotes. Due to the hive mind, the voting will probably look like 30 upvotes and 130 downvotes. So, there would need to be a weight accordingly, so those fewer upvotes had a greater impact (in terms of sorting and scoring comments)

    Reddit has a “sort by controversial” algorithm that seems to be missing from Lemmy (or maybe it’s hidden in the “what’s hot" - I haven’t looked at the code).

    It would be awesome (and resource intensive) if Lemmy could provide the federated instances with custom sorting algorithms. It would allow federated instances to be unique, provide some playful competition, and given the open source nature of Lemmy - I’m sure these algorithms would be open sourced, which would improve the entire Lemmy ecosystem as a whole.


  • Innevitably whatever public transportation you use the route will end up in the ghetteo.

    This is a mindset that many people in the U.S. will need to get over before the “quality” of public transport improves: that busses, trains, subways are for “the poor”.

    I’ve been on the subways in New York and busses and trains elsewhere in the States. They’re gross. Especially, compared to most of Europe (Italy, Denmark, Germany, etc). In Asia, they’re also a clean. The mindset in Asia and Europe is “this is what people (not just the poor) take to get from point A to point B”. There aren’t school busses, the kids just take the same city bus/train/subway that all the other people take to get to work.

    I’ve spent 45 minutes in the States on my daily commute staring at (and riding on) the bumper of the car in front of me. I’ve also spent 45 minutes, in Europe, peacefully riding the subway to work. I’m able to surf the web, watch a video, relax. I definitely enjoy/recommend the later experience.



  • One of your questions I didn’t see answered:

    And after doing my research I found out americans file taxes every year. I haven’t done it the last 18 years of working. Should I just not file?

    You have two choices:

    1. Full Disclosure : you tell the IRS, you haven’t filled and ask them to help you rectify the situation. This could mean penalties and fines for filing late or based on your situation, they might let is slide (as it was an honest oversight). Once you’ve gone through this, then your back in the IRS’ good graces (assuming you still file your taxes and fbar annually)

    2. A “stealth” disclosure : (there’s a better name but I forgot was it’s called) basically, you just start to file your 2023 taxes and pretend that nothing has happened during the last 18 years… if you do this for the next 5 years (or 7 years?) and the IRS does not say anything, then you’re back in the IRS good graces (they can only penalize you for x number of years) . But if the IRS decides to contact you, then they could throw the book at you (more than if you went with option 1).

    Ultimately, it’s a gamble with a risk. However, if you’ve recently learned of your citizenship and got a passport. I think it’s quite plausible to get some lienency, both for the full disclosure and the stealth disclosure.


  • Well… there is also Eritrea, a small country in West Africa.

    The U. S. Taxes is based on the country you’re living in. If there are double taxation treaties between the two countries (ie: Europe and the U. S.), then the IRS would tax you on the amount you’ve earned over a certain limit (it was 100k usd, but I think was increased). Meaning, if you earned 110k usd, you’d be taxes on the 10k. If you earn less then 100k, you’d pay no U. S. Taxes.

    If there isn’t a treaty, which is often the case in countries that tax their citizens less than the U. S. , then you’d basically be charged taxes in the U. S. (based on your worldwide income) minus whatever you paid the country you’re living in.


  • OP read this, they’re absolutely right - lawyer up!

    Cause in the U. S. if you want to renounce your U. S. citizenship, you must settle your debts - which includes filing your U. S. Taxes.

    … and yes, as a U. S. Citizen you need to file U. S. Taxes *even if you’ve never set foot in the U. S. *.

    Note: there are double taxation laws between the U. S. and Germany, which prevent you from needing to pay taxes in U. S. (up to 100k / year or so), but you still must file them.

    Also, as a U. S. Citizen, you’ll need to file annually a FBAR with the IRS. This is basically a disclosure to the IRS that you have non-u.s. bank accounts (that exceed, in total, 20k usd / year).

    The point being is that, in theory, there could be fines for not doing this, which (in theory) you would have to pay before being allowed to renounce your citizenship.

    In practice, the IRS is pretty approachable - so you probably won’t have an issue, but you’ll definitely want decide if you want to keep the U. S. Citizenship (and the work associated with it: annual taxes and fbar) or renounce it.

    The (only) upshot of filing U. S. taxes abroad if you have kids is that you qualify for a Child Tax Credit. Which amounts to 1000 usd / kid / year (I don’t know if the kids need to have U. S. Citizenship or not)








  • I’m curious, how would you do this in such a way that it wouldn’t come at the expense of effecting your high availability?

    If the server were on-prem or in the cloud… and the system crashed/rebooted, how would you decrypt (or add the passphrase) to the encrypted drive?.. cause the likehood of the kernel crashing or a reboot after and update is higher than an FBI raid… and it would get tiresome to have the site being down, while we wait for Bob to wake up, log in, and type the passphrase to mount the encrypted hdd.

    You could use something like HashiCorp Vault, but it isn’t perfect either. If the server were rebooted, it could talk to Vault and request the passphrase (automatically) , but this also means that the FBI could also “plug in” the server (at their leisure) and have it re-request the passphrase. … and if Vault were restarted there’s quite a process to unseal (unlock) a vault - so, it would be as cumbersome as needing to type in the passphrase on reboot.

    My point / question is: yes, encryption (conceptually) is easy, but if you look at “the whole life cycle / workflow” - it’s much more complicated and you (as an administrator) might ask yourself “does this complexity improve anything or actually protect my users?”




  • But the nice thing about email is it’s decentralized, and everyone already has it.

    That is true, but in the case of email as an issue tracker: only the people who have received it will know of its existence (unless it’s mirrored on public facing websites - like Debian does with their issue tracking).

    The thing we’d lose is the “ease of access”. Tbh, I’d see Usenet being a better distribution medium than email for OSS apps… but I really appreciate the intention behind solutions like git-issues: move the issue tracking into the same tools used to track code changes. It, in my opinion, is more in line with K. I. S. S.


  • You make a valid point regarding losing important contextual information like PR and open bugs.

    However, I don’t think email offers the same level of visibility as we currently have with github workflows.

    There is an creative Git based issue tracker, I used called git-issue. Basically, the entire bug/issue/pr process is captured as yaml (I think) files, which are kept in a dedicated branch.

    When I used it (as I wanted a self-hosted bug tracker), I found it functional but a bit cumbersome. However, I could see someone creating a very nice github like web interface for it.