--- Log opened lun nov 28 00:00:44 2022
02:50 < mason> Is there an interface setting that will prevent the timeline from jumping after it's loaded?
02:51 < mason> "Automatic updates only at the top of the post stream pages" seems not to impact this.
02:52 < mason> "Update browser every n seconds" set to -1 also doesn't impact this.
02:53 < mason> As it stands, I load a group, wait for it to jump down halfway, jump back up with the home key, and then start reading.
07:36 < fikabot> 💬 <Hank> Are you talking about when you do something like like something, comment, or reshare?
10:42 < fikabot> 💬 <bkil> Nolan: According to grep, the error about "Apologies" is triggered when the database is not available.
10:45 < fikabot> 💬 <bkil> It is triggered when the database could not connect (possibly due to missing host, username or password setting) while one of the following files already exist: config/local.config.php config/local.ini.php .htconfig.php
10:47 < fikabot> 💬 <bkil> Check whether the keys hostname, username, password, database and charset are correctly set under the "database" key in config/local.config.php
10:52 < fikabot> 💬 <bkil> You can find an overview about logging in https://github.com/friendica/friendica/blob/develop/doc/Settings.md#user-content-logs
10:56 < fikabot> 💬 <bkil> However, if you can't get to the Friendica GUI, then along with the PHP log mentioned there, you can also enable logging from config/local.config.php (or through the database config table if it had already been filled in by default. You can in most cases start from the template to find out your options https://github.com/friendica/friendica/blob/develop/static/settings.config.php#L95
10:57 < fikabot> 💬 <bkil> You basically need to set the `debugging` key under the `system` category to `true` to enable logging. You may also change logfile and loglevel according to your desires as well.
10:59 < fikabot> 💬 <bkil> I don't think that you can move an account to an already existing account. The documentation clearly instructs that you "Do NOT create a new account prior to importing your old settings - user import should be used instead of register". https://github.com/friendica/friendica/blob/develop/doc/Move-Account.md
12:49 < mason> Is there an interface setting that will prevent the timeline from jumping after it's loaded? "Automatic updates only at the top of the post stream pages" seems not to impact this. "Update browser every n seconds" set to -1 also doesn't impact this.
13:08 < fikabot> 💬 <Hank> The only time I notice this is when I interact with posts
13:09 < fikabot> 💬 <Hank> But it doesn’t like cause the entire page to rebuild and throw me back to the top usually
13:10 < fikabot> 💬 <Hank> Except maybe when adding new comments
13:11 < mason> Hm, throwing me back to the top would be interesting. In this case it puts me down somewhere around the middle.
13:12 < mason> My *guess* and I've not positively identified this is that it's jumping me to the most recent "latest activity" despite my being in "latest posts"
13:13 < mason> I suspect I could verify this by navigating through two tabs concurrently, one on "latest activity" and one on "latest posts" but ideally there'd just be a knob saying "don't change the user's scroll location"
13:17 < fikabot> 💬 <bkil> Without checking or knowing, I would guess that your browser has remembered the pixel offset within the page where your position is, but as the DOM is extended, it will scroll to the same offset. A better solution would be to remember the timestamp of your position or the post ID and scroll there after an update.
13:20 < mason> hrm
13:21 < mason> That sounds reasonable.
13:31 < fikabot> 💬 <bkil> But that is only easily fixable from JavaScript. Are you using the main web interface without JavaScript? Which theme exactly?
13:32 < fikabot> 💬 <bkil> Which browser? Well, it probably could be a valid workaround without JavaScript if the query or anchor encoded something like a "cache buster", but for busting scroll position.
13:33 < mason> bkil: Firefox, JavaScript enabled, Frio as a theme
13:34 < fikabot> 💬 <bkil> https://stackoverflow.com/questions/16239520/chrome-remembers-scroll-position/38270059#38270059
13:35 < fikabot> 💬 <bkil> https://developer.mozilla.org/en-US/docs/Web/API/History/scrollRestoration
13:35 < fikabot> 💬 <bkil> https://caniuse.com/mdn-api_history_scrollrestoration
13:35 < mason> interesting
13:36 < mason> That seems like a likely candidate. I'm curious where this would have to be set / who/what would have to set it.
13:46 < simcop2387> so i've added an rss feed as a contact, is there a way to make that show up as something more public in /community for everyone?
13:49 < fikabot> 💬 <bkil> I think that would result in more UX issues. Scrolling back to the top after submitting each comment seems a bit unprofessional. So a better strategy would be to remember the position by post ID and store it via push state. https://developer.mozilla.org/en-US/docs/Web/API/History/pushState Pop will probably be more involved if you aren't using infinite scrolling and if your posit <clipped message>
13:49 < fikabot> 💬 <bkil> ion paged out. Another hacky JS-free solution (other than a scroll-buster) would involve remembering the view state on the server side before submission and generating newer posts at the top within a summary-details widget (or something like that with CSS) that would result in the same pixel position of posts when it's collapsed.
14:04 < fikabot> 💬 <bkil> simcop2387: If you click on the contact listing and select the given RSS contact, under "Contact Settings", you will find "Mirror postings from this contact"
14:12 < simcop2387> Thanks, I'll look now
14:14 < simcop2387> I don't see anything like "Contact Settings" when I'm looking at the listing
14:16 < fikabot> 💬 <simcop2387> https://matrix.org/_matrix/media/v1/download/matrix.org/EcyIXxmjYVYcBNFjivjDJaDg
14:16 < fikabot> 💬 <simcop2387> This is what it looks like to me
14:20 < fikabot> 💬 <bkil> Is it your server?
14:20 < mason> simcop2387: Oh, are you going to do a sort of "universe" view?
14:20 < fikabot> 💬 <simcop2387> Yes, my server
14:20 < mason> Or account that can be followed?
14:20 < fikabot> 💬 <bkil> https://github.com/friendica/friendica/blob/develop/doc/Settings.md#user-content-allow-users-to-set-remote_self
14:21 < fikabot> 💬 <simcop2387> mason: hoping to do so
14:21 < mason> That'd be kind of nifty.
14:21 < fikabot> 💬 <simcop2387> Thanks, that looks like what I'm after.  So create a dummy user for them and then do that to mirror the feed as that user.
14:22 < fikabot> 💬 <bkil> I don't think you need to create a new user per feed. You should probably be able to follow as many feeds as you need from a single user.
14:23 < fikabot> 💬 <bkil> But if you are doing this so that your users can selectively follow feeds distributed centrally like that, you would surely need to keep the feeds separated.
14:23 < fikabot> 💬 <simcop2387> yea i'm thinking that people will want to follow them separately so a user per feed for it is what i think we'd want.
14:41 < fikabot> 💬 <Nolan> OK, thanks, it was in fact a database connection error. Working on getting Friendica running in a VS Code devcontainer. Any idea what might cause the installation form to try posting to http://localhost:8080/http://localhost:8080/install? Is there something I have to do in Apache to tell it not to prepend the base URL twice?
--- Log closed mar nov 29 00:00:46 2022