techie

joined 1 year ago
MODERATOR OF
[–] [email protected] 2 points 1 year ago

Sweet, thank you!

[–] [email protected] 1 points 1 year ago (2 children)

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!

[–] [email protected] 8 points 1 year ago

I’m starting to think Microsoft’s marketing department gets incredibly bored lol. Like the time they renamed Lync to Skype for Business.

[–] [email protected] 9 points 1 year ago

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.

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 3 points 1 year ago

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.

[–] [email protected] 1 points 1 year ago

I see you from techy.news!

[–] [email protected] 124 points 1 year ago (6 children)

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.

 

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

cross-posted from: https://techy.news/post/2224

 

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

cross-posted from: https://techy.news/post/2224

 

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

 

I recently heard of two stories from friends who were hired as remote or hybrid employees, but later forced to come into the office full-time.

The first friend lives about 50 miles outside of the office and was hired as a remote employee. When the company announced RTO for employees living within a certain radius, he was included because his home fell within the zip code range. He now has to commute over an hour each way to come into the office.

The second friend was recently hired with the expectation of a hybrid schedule to come into the office twice a week. This was discussed and agreed upon by his direct manager and director. During his first week, HR decided to change this and forced all employees to RTO full-time.

IMO, in order to stay truly remote, look for companies that:

  • the entire workforce works remote,
  • have majority of senior leadership working remote and value working remote, or
  • have at least 50% of the workforce working remote without easy access to an office
 

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.

[–] [email protected] 1 points 1 year ago (1 children)

I like Harry’s bar soap, specifically the Stone scent. It’s very subtle and not overpowering.