Welcome to our AI-generated Daily Summary topic! (5:00 AM Edition)
This is the topic where a daily summary of meta’s activity is collated by our good friend Bert, and posted here so everyone can get a rundown of some of the top discussions over the past 24 hours.
To account for our global audience, we have three editions (this one, Daily Summary (9pm UTC), and Daily Summary (1pm UTC)), which fire at different times of the day so you can get one at a time most convenient to you. All of them cover the last 24 hours (respectively), so the main difference is when they land.
If you’d like to get a ping whenever a new one is posted just set this topic to Watching (and if you change your mind, change it back ).
Feedback is certainly welcome. We’ll be tweaking and refining the idea as we go, so all input is encouraged. We do have a separate topic for that so as to keep this one just for summaries. You can find that here - Daily Summary Feedback
Enjoy!
Small caveat… AI (even GPT-4) does hallucinate, it is unavoidable. Don’t treat everything it says as truth, as there will likely be some lies mixed in. We’ll try to manually correct any if we spot them, but still… keep an eye out.
0x22f1a6543a0requested the ability to sign up for Discourse using just a phone number for verification, as email is not widely used in China. JammyDodgersuggested using a non-official plugin to disable email verification along with a required user custom field. supermathieproposed using a common SSO or federation login provider to handle phone-based signup.
tobiaseigensuggested that silenced users flagged by Akismet should not be able to like posts. JammyDodgeragreed this should apply to Reactions as well. Lokinoted some organizations legally can’t delete users without an option to protest.
patrickeminasked if deleting the “topic will close” notification also removes the auto-close functionality. JammyDodgerconfirmed deleting the small action post also deletes the topic timer.
velichorinquired about hosting Discourse on a WordPress site. pfaffmanlinked to guides on publishing WordPress posts to Discourse and setting up Discourse alongside existing Apache sites.
Earnie_Bairdrequested help updating user profile info via the Discourse API. After troubleshooting with Arkshine and JammyDodger, they discovered the correct API endpoints and headers needed to update name and username.
ogulcan1787asked how to assign a separate link to the Discourse logo. Arkshineprovided the necessary code, but it caused a JavaScript error. Moinshared an alternative approach that worked.
supermathiereported that after using the topic navigator on mobile, the header sticks around visible at the bottom of the screen. Lillyconfirmed the issue on iPhone with Chrome and Safari.
Samir_Sabriasked for guidance on creating a direct auto-login link from a Ruby on Rails app to Discourse, as part of SSO integration. simonsuggested using a DiscourseConnect login link.
riverinquired about connecting Memberstack with DiscourseConnect. simonreplied it’s likely not possible without server-side code on the Memberstack site, but Memberstack could potentially implement it like Memberful has done.
Master encountered a YAML syntax error while trying to install plugins on a self-hosted Discourse site. Firepup650 and Arkshine suggested checking indentation and using a YAML checker tool.
Gab, a non-profit in Australia, is looking for assistance setting up a new Discourse forum for their 800+ members. HAWK provided guidance on the setup process.
kuazaquestioned why Discourse presents JS and CSS files separately instead of combining them. They found a previous discussion on the topic of JavaScript aggregation.
Moinreported that the “no results” text in the user directory filter is the same as for a brand new community, which doesn’t make sense. They suggest using “No results were found.” instead.
In a discussion on mentioning users, Tris20 asked about ensuring anonymity for users who leave a company, to comply with GDPR. HAWK suggested it may be legitimate to put the onus on the person requesting anonymization to find posts needing editing.
nathankreported that including the link and description when adding events to .ics calendar files has now been implemented, in addition to Google Calendar.
Heliosurgewelcomed a new user looking for help setting up their Discourse forum, suggesting they map out their category structure and consider mail server options if self-hosting.
TonyGreported that the Hungarian password reset URL includes an errant space character. pmusarajreplied that he updated the translation string which should fix it in a few days.
piffyquestioned the intense red “Delete” wording for removing bookmarks, suggesting it implies more permanence than warranted. twofoursixeightnoted the mobile layout at least indicates it’s a bookmark-specific menu.
MarcPnoticed post link previews aren’t working properly in Telegram. pmusarajtested it worked in another Discourse instance and Open Graph tester. Further investigation revealed Telegram is using the canonical URL which omits the post number.
Maartje had trouble finding their About page in the navigation menu. Moinexplained it’s usually in the first menu section and can be re-added by customizing that section.
The search banner component had a bug where the search button text was incorrectly displayed. awesomerobotreproduced it when the site and user locales differed, and has a fix ready.
A 2-month old bug where post event dates weren’t always displayed on topic titles will be fixed once zogstrip’s PR is merged, inspired by mbauman.
TheDarkWizardfollowed up on the status of user-created categories. saquetimreplied the plugin is still under active development to solve category scaling issues but not yet ready for release.
jidannisuggested adding a mouseover tooltip to the site notice close button explaining where to find previously dismissed notices. Moinnoted the hiring banner referenced is a separate theme component that won’t affect other notices.
jonbarrow is working on SSO integration where emails aren’t unique identifiers. simonsuggested enabling verbose logging to debug why the avatar upload is failing.
Explained that evidence is required that bundling CSS/JS files would provide significant speed benefits, as the bottleneck is often in JavaScript execution not asset loading
Noted a potential bug with the Bedrock Claude integration after seeing an issue in multiple daily summary reports
ted is investigating why CNN oneboxing is failing due to the response size exceeding the 2MB limit. sam suggested the needed info should be in the first 2MB anyway.
In the Discourse Post Voting Plugin topic, dreieck relayed UI issues discussed on OpenStreetMap forum where the plugin is used, such as allowing users to start replies that are then blocked upon submission. Read more
Moin suggested adding the admins and moderators groups as mandatory to more settings like hidden post visible groups and chat allowed groups, similar to a recent commit.
awesomerobotrolled out an experimental simplified topic map on Meta, dramatically simplifying the layout while keeping useful information available. The changes include removing some info, summarizing a single way, and putting some data behind clicks.
tumbleweedreported that after updating Discourse, iOS Safari could no longer successfully open their forum, getting stuck on a “loading” page. david noted it starts working when dev tools are opened and they are investigating.
Ryan_Hyer’s Discourse site broke after moving servers. The issue was narrowed down to Cloudflare caching and minification interfering. Disabling Cloudflare’s “auto minify” feature and purging the cache resolved it.
BryanVrequested a plugin outlet between the post editor and preview. Alteras shared that putting a div in the after-d-editor outlet and some CSS positioning worked as an alternative solution.
#admins
Architect had trouble finding where to generate an API key with the new admin settings layout. Moin pointed to an archive.org link with the old instructions. The new location is in the admin settings dropdown under “API keys”.
supermathie investigated the missing images issue on Meta and found that oneboxing in a PM seems to cause the PM to “take over” the image uploads, making them inaccessible in the public topic. Secure uploads exacerbate this.
salbertelli noticed tag counts were missing on their /tags page. Arkshine debugged and found the pmCount was undefined in the API response, resulting in NaN for totalCount.
forummasterasked self-hosters about their experience to decide between self-hosting on a VPS or using managed hosting. Key considerations are difficulty level, migration ease, and common problems encountered.
fokx wondered if the Discourse Chatbot plugin could use the embeddings generated by the discourse-ai plugin to save costs. merefield explained the reasons for keeping them separate currently.
eisammyshared their positive experience self-hosting Discourse for a month, calling it a good lesson they will take with them in their professional life.
sp-jordan-violet had issues with the sidebar not appearing on a new DigitalOcean install. Moin helped resolve it was due to the navigation menu setting. JammyDodger also explained the difference between the main and admin sidebar settings.
awesomerobotintroduced an experiment simplifying the topic map. Changes include showing top 5 posters, hiding popular links behind a click, and showing most liked replies when clicking the like count.
Master had issues with the Discourse Chatbot plugin responding in English instead of Spanish. merefield and MarcP advised modifying the system prompts to specify the desired language.
RGJ encountered a 500 error when using the gpt-4-turbo model in the Discourse AI Topic Summary plugin. merefield suggested it may be a permissions issue if gpt-3.5-turbo works.
samshared thoughts on the challenges with the mobile design, noting issues like inconsistent button sizes, precious real estate usage, and the need for cohesive topic control normalization.
merefield further clarified that Discourse uses a one-dimensional stream of posts rather than threading. supermathienoted the design ideal is for meandering topics to be branched into new ones by writers.
In a discussion on managing issues with Discourse, sp-jordan-violet shared their unorganized thoughts and asked how others handle issues across GitHub, open-source, product feedback, community, internal, and docs in their communities.
merefieldnoted the Discourse Bars theme component is currently incompatible with the “Powered by Discourse” setting. Arkshinesuggested a small CSS change to resolve it.
pmusarajclarified the status of the Discourse Discover launch and fixed a reported issue with an incorrect site screenshot.
supermathienoted the Discourse design ideal for branching meandering topics and agreed with merefield on the importance of content curation by posters and moderators.
tedpraised the Discourse Discover launch as “so cool” and suggested adding thousands separators to the stats.
tgxworldsaid he’ll try to land the requested reordering feature for the objects type theme setting this week and will update the first post about the identifier property.
HAWKliked the idea of starring/favoriting admin pages to have them show up as buttons for quicker access.
kris.kotlarekfixed the bug causing sidebar section headers to be bold in the admin area.
Thanks for reading, and I’ll see you again tomorrow!
Small caveat… AI (even GPT-4) does hallucinate, it is unavoidable. Don’t treat everything it says as truth, as there will likely be some lies mixed in. We’ll try to manually correct any if we spot them, but still… keep an eye out.
