TootSweet

joined 1 year ago
[–] TootSweet@latte.isnot.coffee 71 points 1 year ago* (last edited 1 year ago) (8 children)

Step 1: Print a photo of your dad.

Step 2: Hold it up to the camera.

Step 3: Play Resident Evil 7.

[–] TootSweet@latte.isnot.coffee 23 points 1 year ago (1 children)

Trusted computing is back in a new form. :\

[–] TootSweet@latte.isnot.coffee 1 points 1 year ago (1 children)

Ah. Well, I still see the web interface pulling in new posts as I sit on the home page. But then, I also mentioned that my Lemmy instance (or, the instance I've joined, that is) is a couple of versions behind. (I'm not sure if they're behind on both Lemmy and the UI or on just one.) If they've changed that behavior in newer versions, that could be why I'm still seeing the web interface pull in new posts while you don't.

And if that behavior is removed in the newer versions, then I can probably expect all the issues I've mentioned in this thread to be resolved as soon as latte.isnot.coffee updates to more recent versions of either Lemmy or Lemmy-UI or both.

[–] TootSweet@latte.isnot.coffee 1 points 1 year ago (3 children)

It doesn't refresh the page to get new posts, but it does pull in new posts as they're posted.

 

I didn't know that was something a website could do. But on the main page (that is, '/'), I can't seem to refresh. The refresh button in Firefox doesn't work. Ctrl+r, ctrl+shift+r, and f5 all do not work. Selecting the url and hitting enter doesn't work. I haven't tried in any other browsers. Is this supposed to be a feature?

I'm guessing some folks are going to wonder why I'd ever want or need to refresh. Sometimes, one server or community seems to get "stuck". I'll load my main page (I default to "subscribed/new"), scroll for a bit, and then suddenly the one community gets "unstuck" and starts flooding my feed with (all?) posts from that one community. When it does that, it makes the feed basically unusable. I can't expand out images during that time (and even the thumbnails usually go away on posts for some reason.) The posts move down the page fast enough that I can't read titles or click comment links. It's... a problem.

If I could refresh, I'd have an easy workaround. But right now, the best workaround I've found is to copy the url, open a new tab, paste the url into the new tab, and close the original malfunctioning tab. (Ctrl+l, ctrl+c, ctrl+n, ctrl+v, enter, ctrl+pageup, ctrl+w.)

And, yes, if the issue I describe above would be resolved, that would go a long way toward making it less necessary to allow refreshing. But it's the principle of the thing, you know? Is a web app breaking basic browser functionality considered acceptable? Is being unable to refresh the main page intended?

Now, the instance I'm on is still on an older version. (Specifically 0.17.4.) If any of this is addressed in later versions, that would be awesome news.

Edit: In retrospect, it seems I should have done more experimentation before posting this. Now that I'm trying things, refreshing is working. It takes a second or three to start refreshing, though. I guess my theory at this point is that when I'm experiencing the issue mentioned above, that few seconds turns into a much longer amount of time. (Minutes, I think.) And I just never waited long enough to see that refresh eventually does work. I guess that kindof invalidates much of what I said here, but in case others have insight, I'll leave this post up.

[–] TootSweet@latte.isnot.coffee 1 points 1 year ago* (last edited 1 year ago)

Yeah. I'm definitely for some pretty seamless integration. Probably in the optimal case:

  • The wikis would be hosted on the same domain as the Lemmy servers.
  • Any account you had on the associated Lemmy server would automatically exist to the wiki as well.
  • If you were logged into Lemmy, you'd also be logged into the wiki.
  • Only mods would be able to enable wikis but the process of doing so would be trivially easy.
  • I'd personally say that it makes the most sense to just have the mods link the associated wiki from the sidebar rather than creating new special interface features to add a link outside the sidebar or whatever. (Unless some kind of plugin infrastructure that would allow that already exists.)

But all that can be done without putting any wiki-specific code into the Lemmy or Lemmy-UI source repositories, which I think is preferable for the same reason you wouldn't add flight simulator code to a spreadsheet application. (Ok, maybe a bad example, but you get my point.)

Edit: And I'll admit there are both upsides and downsides to my approach here. One downside would be that some Lemmy instances would offer attached wikis and others wouldn't. It's possible it also just wouldn't catch on at all and nobody would enable attached wikis as a feature if it was a whole separate step to setting up "Lemmy".

[–] TootSweet@latte.isnot.coffee 2 points 1 year ago (1 children)

Mostly I mean the wikis for really informational subreddits like /r/bodyweightfitness or /r/personalfinance. Those would usually be the best place to get information on whatever topic that wasn't mostly sponsored propaganda. And it had uses that the threads didn't fill because the wikis would take a comprehensive view of the subject matter whereas threads would be about one or another detail.

Who knows. Maybe I was the only one who felt like they got benefit from the wikis. Ha!

[–] TootSweet@latte.isnot.coffee 7 points 1 year ago (6 children)

I don't want to be constantly comparing Lemmy to Reddit, but on Reddit, the wikis were invaluable. As helpful as the threads were, the wikis frequently had amazingly useful info.

That said, I'm not sure I think adding wikis to Lemmy is the right way to go. "One thing well" and all that.

Maybe instead, some ancilliary wiki platform that can be run alongside Lemmy that lets a community mod easily set up a wiki that can be linked to in the sidebar?

Or we could go really simple and just link specific posts in the sidebar with useful information of the kind you'd otherwise put into a wiki.

[–] TootSweet@latte.isnot.coffee 1 points 1 year ago (1 children)

I saw another post today about ArchiveTeam Warrior and on a lark started up a Docker container.

But it occurred to me that maybe today isn't the best day to be archiving things. Right?

With so many subreddits shut down, isn't ArchiveTeam going to get a whole lot of "this sub is private" messages rather than actual content?

Hopefully the mothership is smart enough to gracefully account for that. Maybe centrally, they keep track of those pages and "reassign" those pages back out to be fetched again after a good number of hours (days?) have passed.