• 5 Posts
  • 25 Comments
Joined 2 years ago
cake
Cake day: July 26th, 2024

help-circle


  • Neat but I’m getting errors just loading the page.

    A better browsing experience is definitely a nice idea though. I wonder if we couldn’t just improve the UI/UX of the actual peertube web interface though so that all instances benefitted from this work? (For example, allow setting up aggregate indexers on the instance settings (links to json repos) so that channels that exist on other unknown instances can be found quicker.)


  • The amount of furry / anime content on the front page might be putting off some new users

    I don’t see this on mine. Isn’t NSFW enabled by default?

    This is why I don’t generally believe in all being a good “starting” view for new users. Local would probably make more sense until the user has subscriptions, and then defaulting to subscriptions once the user has joined communities. This would mean an always active feed to start, prioritizing the “local” community for users to participate in the instance they belong to, while also not bombarding them with content from the firehose.

    My 2 cents, probably easier to say what to do than to do it though, being a programmer myself. 😎


  • Needing more users is fine. Sure, we could always use more friends (or enemies, I guess)

    But, ultimately, just having people come here first and then whatever hellhole corpo-media second is at least a step in the right direction. I feel like user activity increasing is a good sign that there’s a lot of people out there investing time in the fediverse instead of the corporate hell-loop social media.


  • While LOLA is great, I’d really love an established handshake mechanism for having two accounts on two bespoke services represent the same user.

    For example, I want to have a pixel fed and mastodon presence that can be authored between the two. However, you currently can’t make two accounts that are effectively linked to each other. I feel like this linking is important for further decentralizing the fediverse (by effectively decentralizing the user itself)



  • Active is basically like old forum logic, where new comments will bump it up back to the top. Scaled is my go to view first as it does a pretty good job balancing out communities of widely different sizes, so smaller communities that you’re subbed to have a chance of having their post be seen if it’s new and larger in upvoter count.


  • Hot take: the biggest issue is actually ever entering a community and seeing zero comments. Most reddit addiction stems from wanting to read comments, so I think people should add a comment to something if they’re upvoting and they see that the thread has zero comments.

    Nothing eliminates enthusiasm like seeing 0 comments on every post in a community, especially if that community is driven by bots.




  • Depends on how you do it and what you need from it. I’ve actually moved on from my Pihole instance, for reasons I’ll get into later.

    The broad appeal of using Pihole for DNS in a homelab is the ability to route services from domain names on the local host. This can be really useful, especially for “hacking” service availability onto other unintended devices. Additionally, it can be nice for less tech-savvy users who might not be comfortable editing /etc/hosts or just want to check out a service on their phone web browser.

    I would generally recommend using an isolated device for Pihole needs; If you’re doing work on your home server, you’ll probably want all users on your service to keep their internet connection working to not be a burden to others living in your household (if you have others). A raspberry pi is a really good target for a pihole, and even a cheap old/used one from the interwebs can serve you well (I was using one recently on a pi3b and it was no issue.) Keep in mind that you can’t really do fallback dns configuration unless you’re ok with losing the key feature of pihole (blocking ads and redirecting domains). Notably, I’m actually not a proponent of running all services on individual compute units generally, I just think DNS is special and you don’t really want to tie it into docker services to keep a separation between the services and the server, so to speak.

    This brings me to the second feature: adblocking. This one is really a mixed bag. Ultimately, I turned this feature off only because it doesn’t work for the websites that have arguably the most ad content (youtube, twitch) and really only serves to hurt the smaller players. Sometimes it’s great for blocking things like SmartTV advertisements or data encroachments, but it’s very hard to block ads from a web domain in a way that doesn’t outright block the service itself (so blocking youtube ads without blocking youtube is, seemingly, a fools errand.) I’m willing to hear other people’s opinion on this, I just couldn’t get this working to a satisfactory degree.

    I’ve abandoned Pihole as a local dns resolver. This is because Tailscale suits my needs and also allows me out-of-house connectivity to things like my music or personal data so my phone never goes out of communication with my home network. When you use tailscale at home, it’s generally really good about routing that through your local network instead of the relay, so there shouldn’t be that many downsides. Note, I say generally, because there have been times where it goes through a relay unexpectedly which I haven’t solved yet (this is likely a local router configuration issue, anyway…)

    I notice that you’re already familiar with Pihole, but just thought that it would be best to “explain” my thoughts on it in the form of a recommendation/editorial form.