Best posts made by PhlipElder

@gjacobse said in MS Edge and pop-ups:

I don't use Edge... and for many good reasons. Even with it being build off of Chromium / Chrome.

I've used it mainly as a MS / Azure / O365 Admin since I had to have user and Admin level sessions going over using incognito mode in Chrome.

User is having a site issue that it doesn't work in Chrome but works in Edge - but they are getting Pop-ups in Edge even with the Pop-Up blocker enabled under settings.

I've cycled through a few things but haven't gotten to the cache / reset as they are sloow to respond.

What else could I have them try - because else it's Edge and I haven't much of a care....

Time for a full reset of the browser. They clicked on a search result or something else that pulled in an extension that is probably hidden.

Elevated PowerShell:

CD C:\Users\%username\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml” -Verbose}

@gjacobse Sorry I wasn't clear. At some point the user was looking for something and clicked on a link in the results that then inserted something into Edge that causes the pop-ups.

We've seen it often enough that we've added search training to our Train the Human regimen.

@scottalanmiller said in Staying in Ethics and Legal with ChatGPT usage?:

@PhlipElder said in Staying in Ethics and Legal with ChatGPT usage?:

In those examples the original content comes from the mind of the one hitting the keys.

To some degree, but not entirely. And the same is true of ChatGPT. You still need a competent operator to make it produce useful output. The average person can't operate it to get a good PhD thesis, for example. So it still comes from the mind of the operator of the tool.

I've come to realize that will never again trust anything from anyone without proof that they know what they have presented.

That's going to be the differentiator in my mind.

There's always the person that comes from the "School of Good Enough" and it's those folks that will try and coast through using any "tool" they can without investing the time and effort needed to actually know something.

This conversation puts an entire segment of conferences, conventions, and so much more into question. I'll never be able to look at a person as being knowledgeable without having a conversation with them to determine whether they are a ChatGPT Clone or the real deal.

That's a really sad place to be in Scott.

As I mentioned above, ownership means, "I did that". It came from me not some machine. There is an inherent sense of accomplishment there.

There is no accomplishment having a machine do it for us. None.

And this is the point that doesn't seem to be registering here. Lots of deflections and explanations.

KISS

I do it = mine.
I write it out = mine.
I use a hammer, nails, a string, a tape measure, and a hose to build a house and I did it.

To have someone that has gone through life having it done for them by the ChatGPTs of this world is beyond sad with that person missing one of the most important aspects of being human: I created that.

@scottalanmiller said in Installing Mastodon 4.1.2 on Debian 11:

Mostly this is taken from Mastodon's documentation but some of it is wrong. I tried their Docker configs, but couldn't find any that worked and it isn't clear if they have an official Docker image or just third party ones. They don't actually list Docker on their official site. So this is a traditional install.

As root...

apt update && apt install -y curl wget gnupg apt-transport-https lsb-release ca-certificates
curl -sL https://deb.nodesource.com/setup_16.x | bash -
curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | tee /usr/share/keyrings/yarnkey.gpg >/dev/null
echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | tee /etc/apt/sources.list.d/yarn.list
wget -O /usr/share/keyrings/postgresql.asc https://www.postgresql.org/media/keys/ACCC4CF8.asc
echo "deb [signed-by=/usr/share/keyrings/postgresql.asc] http://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/postgresql.list
apt update && apt install -y imagemagick ffmpeg libpq-dev libxml2-dev libxslt1-dev file git-core \
  g++ libprotobuf-dev protobuf-compiler pkg-config nodejs gcc autoconf \
  bison build-essential libssl-dev libyaml-dev libreadline6-dev \
  zlib1g-dev libncurses5-dev libffi-dev libgdbm-dev \
  nginx redis-server redis-tools postgresql postgresql-contrib \
  certbot python3-certbot-nginx libidn11-dev libicu-dev libjemalloc-dev nodejs
corepack enable && yarn set version classic
adduser --disabled-login --gecos "" mastodon
sudo -u postgres psql -c 'CREATE USER mastodon CREATEDB;'
ufw allow http && ufw allow https

As Mastodon

su - mastodon
git clone https://github.com/rbenv/rbenv.git ~/.rbenv && cd ~/.rbenv && src/configure && make -C src
echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bashrc && echo 'eval "$(rbenv init -)"' >> ~/.bashrc
exec bash
git clone https://github.com/rbenv/ruby-build.git ~/.rbenv/plugins/ruby-build
RUBY_CONFIGURE_OPTS=--with-jemalloc rbenv install 3.0.6
rbenv global 3.0.6
gem install bundler --no-document
cd ~
git clone https://github.com/mastodon/mastodon.git live && cd live
git checkout $(git tag -l | grep -v 'rc[0-9]*$' | sort -V | tail -n 1)
bundle config deployment 'true'
bundle config without 'development test'
bundle install -j$(getconf _NPROCESSORS_ONLN)
yarn install --pure-lockfile
RAILS_ENV=production bundle exec rake mastodon:setup
npx update-browserslist-db@latest
exit

As root again...

cp /home/mastodon/live/dist/nginx.conf /etc/nginx/sites-available/mastodon
certbot --nginx -d  yourdomain.com
ln -s /etc/nginx/sites-available/mastodon /etc/nginx/sites-enabled/mastodon
vi /etc/nginx/sites-available/mastodon
rm /etc/nginx/sites-enabled/default
systemctl restart nginx
cp /home/mastodon/live/dist/mastodon-*.service /etc/systemd/system/
systemctl daemon-reload
systemctl enable --now mastodon-web mastodon-sidekiq mastodon-streaming

We install on Ubuntu and yeah, their documentation really sucks. There's lots of little tweaks that need to be done outside of what they have.

I've not had the time to compile them into a How To as of yet as each successive install has needed to be tweaked so keeping a public facing How To is out of the question.

@scottalanmiller said in Installing Mastodon 4.1.2 on Debian 11:

@PhlipElder said in Installing Mastodon 4.1.2 on Debian 11:

I've not had the time to compile them into a How To as of yet as each successive install has needed to be tweaked so keeping a public facing How To is out of the question.

I think that the Mastodon team has had the same issue and just gave up, lol.

Yeah, their notes are based on Ubuntu 19.x LTS with some copy & paste to try and cover Ubuntu 20.x LTS. It took about half a dozen run throughs before we were confident we had a stable configuration. We host all of the instances in-house.

@scottalanmiller said in Installing Mastodon 4.1.2 on Debian 11:

@PhlipElder said in Installing Mastodon 4.1.2 on Debian 11:

We install on Ubuntu and yeah, their documentation really sucks. There's lots of little tweaks that need to be done outside of what they have.

Current or LTS? I tried on current and there are some super recent breaking changes in the last few weeks that basically don't work on Ubuntu 23.04. I didn't try LTS because once doing that, I looked and Debian 11 felt like the better choice and it worked with a LOT fewer tweaks. At least Debian 11 is current, at the moment (but not for long, lol.)

That Mastodon requires Ruby 3.0.6, what the heck. I couldn't get it to run on 3.0.4 with the latest Mastodon 4.1.2 and Ubuntu couldn't compile 3.0.6 successfully and it isn't available for it any other way and Mastodon isn't yet compatible with Ruby 3.1 or 3.2, which is even more ridiculous.

ugh.

We're on 20.04.x LTS and recently on 22.04.x LTS. Getting deployed on 22.04.x LTS required a bit of intervention via GitHub help request. But, we ended up figuring it out along with another poster on that GitHub thread.

Mastodon is very particular about component versions. So, while we take the out of the box Ubuntu LTS version there's been times where we've tweaked the repository for a specific component version.