Pretty simple django + pandas in the background. Anyone interested in source ?
Yeah, why not post the source? Any reason why it only provides links to the posts, rather than an embedding of the post on the page?
Oh yea I did that initially. Two reasons
You should try to find a solution, probably cache the entire page. It doesn’t seem like it changes too often and everyone sees the same content anyway. Also, just keep the content of the post, no need for any CSS.
That would be no problem, I can also get the user Icons of the people who posted it. I was thinking it may upset some server/content owners. Feels like a repost to directly copy no ?
Yeah, it’s iffy to directly copy. People might not like that. It’s a good call to not do that.
This is a fascinating idea. the page itself could really use some more information - how many sites/toots is it considering? (“all posts” is a bold claim, especially for a federated system). A paragraph on the page itself explaining what its doing would be helpful, especially for visitors who are not coming from lobste.rs. A link to a description of the “HN algorithm” would also be nice. And finally, the source code would be a good reference, too. thanks!
Nice! Your title seems to have been truncated?
Am interested in source - would be cool if you adapted some open ranking algo like reddit’s. To my biased eye, the ranking has some pretty old posts.
yea, old posts can get bumped by someone replying to it or “boosting” it. But actually I like the result because its more for exploration than another website to get an addiction too.
Oy, careful with the Switter posts, those could be NSFW.
yea, but NSFW images should require a click before they show no?
Yeah, but I’ve noticed that Switter isn’t always careful enough with those. I personally blocked Switter because I would often see ads from it.
I think there is a DNS issue:
$ nslookup lazymastodon.com
*** Can't find lazymastodon.com: No answer
I have this issue with two different ISPs so…
Hackernews killed it I had to make a quick backup on s3
if you clear cache DNS should point to that now
This is interesting. I’ve been running my own instance a few weeks though, and thought I might find some more people to follow.
Clicking through the links, I’m just starting to think that Mastodon isn’t for me. It’s not exactly a shock, it positions itself as a twitter alternative, and I never got into twitter either. I like Mastodon, in that I think it fulfills some popular use. It’s just not for me.
PS Would non-Mastodon ActivityPub posts show up here, assuming they were popular enough? Peertube, for instance?
switter.at seems to just be dating/mildly sexual ads?
Switter happened because of SESTA/FOSTA. It’s like Twitter, except for SW.
This is really nice, to get some more overview over the fediverse and to find new peoole to follow.
Thank’s a lot!
glad you like it. It feels to me like the good old internet days where you come across quirky communities on the regular.
You know at first I thought “I wish it would show the post’s text”, but when you click through, you discover all the other content that is there. Very cool. I’m actually surprised at the amount of users all over!
Does this respect #nobot? (It’s essentially the same as an ‘ambassador bot’, of which there are several, & the accepted way to inform ambassador bots that you don’t want your profile indexed is putting ‘#nobot’ in your bio. A lot of people will probably get pissed off if this policy isn’t respected.)
Ok I added this feature. I check every post for string #nobot before including it. Thanks for the advice.
#nobot is usually a user-level constraint – if it’s in a user’s bio, then they don’t consent to have their public posts scraped by an automated process. (I’m not sure if any process that supports this also searches for it in the post body. It’s sort of an ad-hoc thing, made in part in response to my early malfunctioning followbot project, & I had stopped working on that by the time it was accepted.)
If you’re using mastodon.py, you just need to grab the user ID from the post object, drop it into a ‘get user info’ request (the same way you’d get an avatar), and search the bio/profile.