• 0 Posts
  • 28 Comments
Joined 1 year ago
cake
Cake day: September 10th, 2023

help-circle






  • Step 3: unfuck the SIP settings, then email both HR and their supervisor to throw them under the bus. Also covers your ass for step 4.

    Step 4: Route the manager’s calls to a disconnected number. When they come knocking about their phone not working, tell them, “No, you should be able to dial out, unless someone changed the SIP trunk settings and didn’t tell me.”


  • Assuming you already have the IP phones, you need two things. A PBX server (for the VoIP stuff), and a SIP trunk with a block of external phone numbers.

    Start with the PBX server software, there’s several free/open-source implementations. Once you’re comfortable with it and have internal calling good to go, then you can spend on the SIP trunk and number blocks.


  • There’s also a limited federation mode that server admins can use. Users and posts are still searchable, but they do not show on the public federated feed.
    Useful for this exact case where a server may have beneficial accounts, but the rest should be hidden for moderation reasons.

    Still would prefer it being on a proper mastodon server, but I can live with this. Whatever server ends up hosting a President’s account now has to deal with record preservation laws for their posts. Let’s leave that bureaucratic stuff to threads.




  • Step right up and place your bets now, folks! What will be the tipping point for massive defederation? Will it be:

    • Snobby, vocal elitism from instance admins,

    • Retaliatory sanctions for anticompetitive actions, or

    • insufficient moderation of harmful or adult content?

    I’m putting $20 on the third one, rampant porn bots will be the tipping point.




  • Fedora Linux also comes with SELinux enabled by default. Did you check that the new home folder and all its contents have the proper SELinux tags?
    Run an ls -lZ and check that the directory has the user_home_t tag,
    The user’s home directory is also stored in the /etc/passwd file. Did you update the entry there?

    No, do not “disable SELinux”. That advice hasn’t been valid for a good 20 years. You can set it to permissive though, to see if it’s the source of the problem.