TestFlight for Voyager
  • "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearTE
    techie
    Now 100%

    Does the native app proxy through your server like the PWA, or does it connect directly with the instance? Thanks for all your work on this!

    1
  • Can anyone see this?
  • "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearTE
    techie
    Now 100%

    I seem to recall from reading a GitHub issue that a public cert and private key is generated for your user account upon creation. Once you start federating and interacting with other instances, the cert is distributed. When you delete the instance and start all over from scratch with the same username, now there’s a different public cert and the remote instances no longer trust your username.

    I’ll try to find the GitHub issue that discusses this issue.

    9
  • No luck getting my Lemmy instance up and running, is this a good place to get some help?
  • "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearTE
    techie
    Now 100%

    Came here to say the Ansible method is much, much easier than manual with Docker and from scratch.

    I was banging my head for hours fixing all kinds of errors. I finally gave up and went the Ansible method and was able to get to the Lemmy login page within 5 minutes.

    OP, if you decide to go the Ansible method, you’ll need to setup a separate server and install Ansible on it. From there clone the Git repo and modify the files the instructions tell you to. Make sure the two servers can talk to each other via SSH. Lastly, run the “ansible-playbook -i inventory/hosts lemmy.yml” command and your Lemmy instance should be online within a few minutes.

    Honestly, my advice is to setup two temp VPS’s with Ubuntu on them. Don’t lock them down too tight and play with the Ansible deployment. Once you get a feel for how everything goes, you can redeploy the VPS’s and set them up properly with proper security.

    2
  • How is it possible that roughly 50% of Americans can’t read above a 6th grade level and how are 21% just flat out illiterate?
  • "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearTE
    techie
    Now 100%

    I think the one thing you hit on is that your family valued education. They knew that in order for you to have a better life than the one they had, the one tool they could give you to be successful in life is education. They worked hard to give you this by making sure you had your basic needs met so that you could focus on learning.

    2
  • If I self host a Lemmy instance for just myself and maybe a few friends are there any risks?
  • "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearTE
    techie
    Now 97%

    The Electronic Frontier Foundation wrote a pretty good blog post on the legality of the Fediverse, around the time Mastodon was getting popular. It probably applies to Lemmy too. It’s worth a read to familiarize yourself of what kind of legal things you’ll be getting yourself into. You’re on the right track; you can control you and your friends’ content, but you can’t control remote content that gets pushed to your server and that’s the part to worry the most.

    https://www.eff.org/deeplinks/2022/12/user-generated-content-and-fediverse-legal-primer

    One thing that stood out is to register yourself as a DMCA agent. It costs $6 or something. Having an agent on record gives instance admins certain protection.

    102
  • It started off with an employee sending an email to a distribution list called "Bedlam DL3" asking to be taken off the list. With 13,000 recipients and everyone replying all with, "Me too!" and other messages, it was estimated that over **15 million** messages were sent through the system in an hour. This crashed the MTA service due to a recipient limit. Each time the MTA service recovered, it would attempt to resend the message again which lead to a crash loop. As a result of the incident, the Exchange team introduced message recipient limits and distribution list restrictions to Exchange, which is something we all use today! More on the story here: [https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643](https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643) cross-posted from: https://techy.news/post/2224

    161
    14

    It started off with an employee sending an email to a distribution list called "Bedlam DL3" asking to be taken off the list. With 13,000 recipients and everyone replying all with, "Me too!" and other messages, it was estimated that over **15 million** messages were sent through the system in an hour. This crashed the MTA service due to a recipient limit. Each time the MTA service recovered, it would attempt to resend the message again which lead to a crash loop. As a result of the incident, the Exchange team introduced message recipient limits and distribution list restrictions to Exchange, which is something we all use today! More on the story here: [https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643](https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643) cross-posted from: https://techy.news/post/2224

    14
    2

    It started off with an employee sending an email to a distribution list called "Bedlam DL3" asking to be taken off the list. With 13,000 recipients and everyone replying all with, "Me too!" and other messages, it was estimated that over **15 million** messages were sent through the system in an hour. This crashed the MTA service due to a recipient limit. Each time the MTA service recovered, it would attempt to resend the message again which lead to a crash loop. As a result of the incident, the Exchange team introduced message recipient limits and distribution list restrictions to Exchange, which is something we all use today! More on the story here: [https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643](https://techcommunity.microsoft.com/t5/exchange-team-blog/me-too/ba-p/610643)

    2
    0
    Microsoft wants to move Windows fully to the cloud
  • "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearTE
    techie
    Now 100%

    Microsoft has a track record of having excellent uptime! /s

    I find it somewhat funny that this article came out on the day Microsoft 365 had an outage for most of the day.

    4
  • From M365 Service Health Dashboard: EX610644 Title: Some users in North America may be unable to access their Exchange Online mailbox using Outlook on the web User impact: Users in North America may be unable to access their Exchange Online mailbox using Outlook on the web. More info: Affected users may encounter an unexpected 500 error when accessing Outlook on the web.

    1
    0
    apnews.com

    WASHINGTON (AP) — The Supreme Court on Tuesday ruled that North Carolina’s top court did not overstep its bounds in striking down a congressional districting plan as excessively partisan under state law. The justices by a 6-3 vote rejected the broadest view of a case that could have transformed elections for Congress and president. North Carolina Republicans had asked the court to leave state legislatures virtually unchecked by their state courts when dealing with federal elections.

    43
    4
    "Initials" by "Florian Körner", licensed under "CC0 1.0". / Remix of the original. - Created with dicebear.comInitialsFlorian Körnerhttps://github.com/dicebear/dicebearTE
    Now
    5 10

    techie

    techy.news