You have clearly never driven on 93 through Boston where the person you replied to said they are from (aka the Big Dig). It is basically an entire highway that is underneath the city. There are many on and off ramps, lanes suddenly become exit only, complex multi-lane exits that branch...it's intimidating. As somebody that has lived in the Boston area for 15 years now, I still mess things up.
Official response from Greg Bernhardt
It's years since I last used PhysicsForums, but found it immensely useful in the old days while going through my undergrad physics degree (it was less useful for PhD courses). I am not morally opposed to providing AI attempts at an answer in threads where nobody else chimes in. However, using real accounts that belong to other users is wildly over the line. I was surprised to see this wasn't really called out in the official response thread by the existing users as that is the part of all this that is the most egregious to me.
IIRC, piefed's private votes are disabled for "trusted" instances. You can see which instances are trusted here.
I have a PhD in and am a practicing physicist in the field of rheology. I think this is an interesting way to explain viscoelastic materials to people. My go-to example is usually Silly Putty, but cats are something that just about everybody has some experience with.
I guess it depends what you want to do with it. I do lots of product photography, so I know exactly what lens I need for my studio and the type of product I am shooting. So, I spent about as much on a lens as I did a body. Getting a better sensor with more accurate colors saves me time in the post-processing step.
When I was starting out, I just used a kit zoom lens, but realized that most of my shots were around the same focal length. So that is when I invested in a faster, nicer prime lens at that focal length.
Taking a look at those two paradigms, I think I prefer the collapsed comment sections. Different communities/instances can have very different moderation policies or standards of discourse, so allowing users to segregate the comment sections like that would be helpful. Having all the comments from the different crossposts is definitely nice, and a step up from the way lemmy handles crossposts.
A special case might be if there are crossposts within the same community. In one of the communities I mod, there are recurring posts where the same lead image is used, so they are automatically detected as crossposts in lemmy even though weeks have elapsed since the last time it was posted. Not sure if something like this should be handled differently or not.
I have scheduled posts for lemmy in the past using lemmy-schedule, so I won't say no to this feature, but I don't think it needs to be a high priority. It is most useful for community moderators that do things like schedule weekly posts (what I have used it for) or create threads for specific events (sporting event, community movie night, etc.). This is something that wouldn't be too hard to live as a third-party tool interacting via an api (if a piefed api exists...I haven't checked).
Combining comments into one comment section from crossposts could be an issue in some circumstances. An example from the communities I am most familiar with (ani.social communities primarily):
There was recently a show airing this past fall season called Dan Da Dan. Users created a community to host episode discussion threads, !dandadan@ani.social. However, to try to separate spoilery discussion among those that have read the source material, a source reader community was made, !dandadumber@ani.social. When an episode aired each week, a discussion thread was made in each community and they both linked to the same poster image of the show. So, they would show up as crossposts. However, if the comments were combined, then the spoiler-filled discussion would be mixed in with the spoiler-free comments.
Writing this out, I guess you might be able to segregate the different comment sections in some way to help avoid this. Comments from the crossposted communities might start collapsed in their own section, similar to the current reply page. So, imagine dividers like this that say things like "Comments from !technology@lemmy.world", "Comments from !technology@lemmy.zip", etc.
Yes! I use this to help with modding. I can't necessarily view every comment thread of every post very easily, so flipping over to the comment view makes keeping tabs on them easier.
Also, this is neither here nor there, but I have been trying out piefed lately and it's pretty cool. Thanks to the devs over there, the anime community should be a lot more compatible with piefed going forward thanks to squashing a couple bugs I found from our use cases. Specifically, piefed users should now enjoy:
- Images on episode discussion threads don't disappear when I edit in a screenshot submitted by a user (relevant issue)
- Clips submitted to the community will no longer break the UI in Tile or Wide Tile view (relevant issue)
Welcome to lemmy! I just wanted to shout out Piefed, a fediverse software similar to lemmy (that I am posting from) that is actually written using flask!
I am very new at using flask, but have found that the flask community on reddit has been one that I have had to dip into from time to time as I have been noodling away at a project. So, it's nice to see one on here as well.